How to Edit Subtitles in Excel or CSV and Convert Back

Subtitle editors are built for timing work. Translation, proofreading, and consistency fixes are easier in a spreadsheet: you can filter, sort, search and replace, or hand a file to a translator who has never seen an SRT file. The catch is getting the captions back out without breaking them. Here's the workflow, and the details that keep it safe.

Step 1: export the subtitles to a sheet

The SRT ⇄ Excel Converter and SRT ⇄ CSV Converter turn each cue into one row with four columns:

A caption on two lines stays two lines inside its cell. In CSV that cell is quoted; in Excel it shows as wrapped text. Formatting tags such as <i> stay in the text, so a translator can see which lines are italic (off-screen voices, songs) and keep the tags around the translated words.

Step 2: edit, or add a language

For proofreading, edit the Text column directly. For a translation, keep the original next to the new text:

1. Rename the Text column to something like English.
2. Add a new column called Text and write the translation there, row by row.
3. Leave Start and End alone.

When converting back, the tool reads only the columns named Start, End and Text. The names are matched case-insensitively, and it also accepts Start Time/StartTime, End Time/EndTime, and Subtitle or Caption in place of Text. Anything else, like the English column or reviewer notes, is ignored. To make a file for a third language, rename columns so that language's column is the one called Text, and convert again.

Step 3: convert back to SRT

Upload the sheet (or paste the CSV) in the reverse direction and download the .srt. Cues are sorted by Start and renumbered 1, 2, 3…, so rows added at the bottom of the sheet, or a sheet sorted by speaker, still give a file in time order. The Index column itself isn't used.

Keeping timestamps intact

Timing is the part that breaks, and what breaks it is a spreadsheet program "helpfully" reinterpreting a timestamp as a time of day.

• Prefer the .xlsx route when people will edit in Excel. In the Excel file, Start and End are stored as text cells, and Excel leaves them alone. A CSV is re-parsed every time it's opened, so its timestamps can be reinterpreted.
• The comma-decimal problem. In languages and regions that use a comma as the decimal separator (much of Europe, for example), Excel can read 00:00:01,234 in a CSV as a time value and display it as 00:00:01, dropping the milliseconds. If you work in such a locale, use the .xlsx file.
• What the converter accepts. Both 00:00:01,234 and 00:00:01.234 are read correctly, and so is 00:00:01 with no milliseconds (as 1.000 seconds). If a timestamp cell was turned into an Excel time, the converter reads the time value, milliseconds included.

Before converting back, filter the Start and End columns for blanks. A missing or mistyped time stops the conversion with an error that names the spreadsheet row, for example Row 14: the End time "" isn't a timestamp. That's better than a silently broken file, but quicker to catch with a filter first.

Quick quality checks while you're in the sheet

A spreadsheet makes a few subtitle checks easy that are tedious in a subtitle editor:

• Line length. Add a helper column with =LEN(D2) (or check each line if a cell has two). Many style guides cap subtitle lines at around 42 characters for Latin-script languages. Translations often run longer than the source text, so sort by this column to find the lines that need trimming.
• Consistency. Filter the Text column for a character name or product term to check it's translated the same way everywhere.
• Leftover source text. Sort by the Text column. Untranslated rows often cluster together or show up identical to the original column.

Reading-speed checks (characters per second) need the durations as numbers. Since the timestamps are deliberately kept as text, that's easier in a subtitle editor after you convert back.

CSV or Excel?

• Excel (.xlsx) when a person will edit the file in Excel, when you're in a comma-decimal locale, or when you want line breaks shown neatly inside cells.
• CSV when the file goes to a script, a translation-management system, or Google Sheets, all of which read quoted multi-line cells correctly.

Both converters run entirely in your browser, which matters for unreleased video, and they accept files up to 200MB. If you only need a readable transcript rather than a spreadsheet, the subtitle formats guide covers the text export and converting between SRT, VTT and ASS.