SRT to CSV Converter

Convert SRT subtitles to CSV instantly in your browser.

Accepts
SRT
OutputCSV

Drop your subtitle file here

or click to browse (multiple files supported)

Supported: SRT

Your converted subtitles will appear here.

About Converting SRT to CSV

Converting an SRT (.srt) file to CSV turns each numbered subtitle block into a spreadsheet row: ready to open in Excel or Google Sheets for review, bulk editing, or handing off to a translator who works in spreadsheets rather than a subtitle editor.

What is SRT Format?

SubRip (SRT) is the most widely supported subtitle format. It contains only basic text and timing information without styling or positioning data, making it universally compatible with video players and platforms.

What is CSV Subtitle Export?

CSV (.csv) is a spreadsheet-ready export: not a subtitle format any media player reads, but the format for reviewing, editing, or bulk-processing subtitle text in Excel, Google Sheets, or any spreadsheet tool. Each cue becomes one row with its index, start/end timecodes, millisecond timing, and text in separate columns, so a translator, editor, or QA reviewer can work through an entire subtitle file as a table instead of a line-based text format.

About SRT to CSV Conversion

  • One row per cue: each SRT block (index, timestamp line, text) becomes a CSV row with index, start/end, startMs/endMs, and text columns.
  • Timecodes are quoted: the SRT timecode format (00:00:01,000) itself contains a comma, so the start/end columns are quoted per the CSV standard, otherwise spreadsheet software would misread the comma as a column break.
  • Multi-line cues and styling tags flattened: a cue that spans two lines in SRT becomes one space-joined cell, and optional <i>/<b> tags are stripped, a spreadsheet cell is plain text with no line-break or styling convention.

All timing is preserved precisely during conversion.

What You Lose vs What You Gain

What You Lose in Conversion

What You Gain in Conversion

  • Opens directly in Excel, Google Sheets, or any spreadsheet tool, no import wizard needed
  • One row per cue makes bulk find-and-replace, sorting, or filtering trivial in a spreadsheet
  • A familiar table format for translators and reviewers who work in spreadsheets, not subtitle editors

When to Convert SRT to CSV

Spreadsheet Review

Review or proofread an entire subtitle file as rows and columns instead of scrolling through timecoded text.

Bulk Text Editing

Use a spreadsheet's find-and-replace, sort, and filter tools to bulk-edit cue text across a whole file.

Translation & QA Workflows

Hand off cue text to a translator or QA reviewer in a format they already work in, without teaching them a subtitle editor.

Frequently Asked Questions

Can I edit the CSV and convert it back into an SRT file?

Not with this tool: CSV export is one-directional. It's meant for reviewing or bulk-editing cue text in a spreadsheet, not as a round-trippable subtitle format. Keep your original SRT file if you need it back.

Why are the timecode columns wrapped in quotes?

SRT's timecode format (00:00:01,000) uses a comma before the milliseconds. Since CSV uses commas as column separators, any field containing one must be quoted per the CSV standard (RFC 4180), otherwise spreadsheet software would split that single timecode into two columns.

What happens to a subtitle line that spans two lines in the SRT file?

Multi-line cue text is joined into a single line with a space, since a spreadsheet cell doesn't have a native line-break convention the way subtitle formats do. The full text is preserved, only the line break is flattened.

Tips for Converting SRT to CSV

CSV export is one-way: there is no CSV-to-SRT converter, since CSV here is a review/editing format for spreadsheets, not a subtitle format any player reads back.

Use the numeric startMs/endMs columns for spreadsheet formulas (duration = endMs − startMs) instead of parsing the timecode text columns.

If you need the original SRT back after editing the CSV, keep your source .srt file: this export is additive, not a replacement workflow, and there is no re-import path.