Convert SRT to CSV or TSV

Turn a SubRip .srt file into a spreadsheet table — comma-separated CSV or tab-separated TSV, one row per cue, with index, start, end and text columns. Drop it below and it converts instantly in your browser.

Drop your .srt file here
or click to choose a file · or paste the text below

Timestamps are written HH:MM:SS.mmm (a dot before the milliseconds, so they never clash with the comma delimiter), and a cue with more than one line is collapsed into a single cell with each break written as a literal \n. Nothing is uploaded — the file is built in your browser.

Subtitles as a spreadsheet

Translators and editors often prefer to work in columns: one row per subtitle, the original text in one cell and the translation in the next. CSV (comma-separated values) is the format every spreadsheet app opens, so exporting your .srt to CSV lets you edit, translate, spell-check or reorder cues in a familiar grid instead of a subtitle editor.

Each row carries the cue's index, its start and end times, and the text. Timings are written as HH:MM:SS.mmm so they read cleanly and never collide with the comma that separates columns. A cue that spans two lines is kept on one row, its line break written as a literal \n, so the table stays exactly one row per subtitle.

When you're done, the CSV to SRT tool turns the edited sheet straight back into a subtitle file — the timings ride along untouched, so a translation pass never knocks your subtitles out of sync.

Prefer tabs? Switch the output to TSV and the same table is written tab-separated instead. Because no field ever contains a tab, nothing needs quoting — commas in the caption text just sit there as text — and a TSV pastes cleanly into an existing sheet, since spreadsheet apps put tab-separated rows on the clipboard.

FAQ

What do the columns mean?

There are four: index (the cue number), start and end (the on-screen times as HH:MM:SS.mmm), and text (the caption itself). One row is one subtitle cue.

How are two-line subtitles handled?

A cue with more than one line is collapsed into a single cell, with each line break written as a literal \n (a backslash then an n). That keeps the table one row per cue. When you convert back with the CSV to SRT tool, each \n becomes a real line break again.

Why are the timestamps written with a dot, not a comma?

SubRip normally writes milliseconds after a comma (00:00:01,000). In a CSV that comma would look like a new column, so the export uses a dot (00:00:01.000) instead. The importer accepts either, so nothing is lost on the way back.

When should I pick TSV instead of CSV?

Pick TSV when your captions are full of commas or when you plan to paste rows into an existing sheet rather than open a file — tab-separated cells never need quoting and match what spreadsheets use on the clipboard. Pick CSV when a tool asks for a .csv file specifically. The columns are identical either way, and CSV/TSV to SRT reads both back.

Is my file uploaded anywhere?

No. The conversion runs in JavaScript inside your browser. Your file never leaves your device, no server is involved, and the page works offline.

Can I batch convert multiple files at once?

Yes. Drop several .srt files together and they'll each be converted and returned in a single ZIP, all in your browser. It's the same conversion as single files, just in bulk.

You might also need