Skip to content

SubRip SRT to Plain text converter

SRT to TXT strips timing and cue numbers, leaving only caption text separated by blank lines.

  • Converted with Subtitle engine · nothing stored
  • Free: 5 conversions a day · 5 MB each
  • Higher limits →

From real runs

What you get — and what changes

  • Cue text Kept

    All three torture SRT cue texts appeared in the TXT output in their original order.

  • Timestamps Lost

    Start and end times were removed completely because TXT output is a transcript, not a subtitle file.

  • Cue numbers Lost

    Numeric SRT indexes did not appear in the transcript output.

  • Multiline cues Kept

    The first torture cue kept its internal line break between the first and second caption lines.

  • Styling tags Kept

    The literal <i> tag and the {\an8} placement override stayed in text instead of being stripped.

  • Encoding Changed

    The UTF-8 BOM was removed, while café and curly punctuation remained readable.

Sample conversions

Torture SRT transcript

Input
BOM and CRLF SRT with comma milliseconds, <i> styling, a {\an8} top-position tag, overlapping cues, a quote, and café.
Output
118 byte TXT containing three text blocks, including the literal styling tags, with no cue numbers or timestamp lines.

Sample SRT transcript

Input
176 byte fixture SRT with three numbered cues from 00:00:01,000 through 00:00:09,000.
Output
80 byte TXT with Previously, on the show, We never found the second key, and Then we look again separated by blank lines.

A real SubRip SRT → Plain text run

We converted our SubRip SRT sample (176 B) with Subtitle engine on 2026-09-11. It took 1 ms and produced a 80 B Plain text file, 55% smaller than the input. The engine raised no warnings.

Input · sample.srt · 176 B

3 cues

Cues
3
Lines
9

Output · sample.txt · 80 B

3 non-empty lines, 14 words

Lines
3
Words
14

First lines of the output

txt
Previously, on the show…

We never found the second key.

Then we look again.

Do it yourself

FFmpeg plus shell text filter

bash
ffmpeg -i in.srt -f srt - | sed -E '/^[0-9]+$/d; /-->/d' > out.txt

This quick filter does not remove inline styling tags, matching the service behavior more closely than a cleaned transcript.

SubRip SRT to Plain text by API or MCP

The HTTP API and the MCP server run the exact engine this page uses (Subtitle engine); the response carries the same warnings the web converter shows. Check support first with GET /api/v1/pairs?from=srt&to=txt.

curl
curl -X POST https://filetypeconverters.com/api/v1/convert \
  -H "Authorization: Bearer $FTC_API_KEY" \
  -F "file=@input.srt" -F "from=srt" -F "to=txt" \
  --output output.txt
API reference

When this is the wrong conversion

  • Use /convert/srt-to-json when timing must remain available for search, QA, or downstream automation.
  • Use /convert/srt-to-csv when the transcript needs spreadsheet columns for start, end, and text.
  • Do not use TXT if a video platform still needs captions synced to media.

SubRip SRT to Plain text questions

Does SRT to TXT remove timestamps?

Yes. The output includes only cue text blocks, so every timestamp line is omitted.

Are SRT styling tags stripped?

No in the current our subtitle engine output. We saw both <i> and {\an8} appear literally in the TXT transcript.

Does overlapping cue timing matter for TXT?

Only the order matters after conversion. The overlapping torture cue stayed as the second text block, but its overlap was not represented.

Related conversions