Subtitle tools
Subtitle tools that convert SRT in the browser: strip it to plain text, or turn it into WebVTT for an HTML5 video player. Nothing is uploaded.
Reading a subtitle file versus playing it in a browser
Both pages start from the same .srt file and both run the same parser underneath, but they solve different problems. One throws the timing away and keeps the words; the other keeps the timing and only changes what a browser needs to accept it.
- SRT to TXT
For reading, searching or pasting the dialogue somewhere that has no use for timecodes — a transcript, a summary, a script draft.
- SRT to VTT
For attaching captions to an HTML5 <video> element, which only reads WebVTT. The timing is identical, only the format wrapper changes.
What an .srt file actually contains
SubRip splits a file into blocks separated by a blank line, each one a sequence number, a timecode line (00:00:01,000 --> 00:00:04,000), and one or more lines of dialogue. Both converters here parse that structure the same way: find the timecode line inside each block, take everything after it as the text, and keep going even when a sequence number is missing or a file mixes CRLF and LF line endings — real exports from different tools are not always consistent about either.
From there the two tools diverge. Text extraction throws the block's numbers and timing away and keeps the dialogue, with the internal line breaks of a multi-line cue preserved rather than flattened. VTT conversion keeps everything the source file had — same cue order, same start and end times down to the millisecond — and only adds the WEBVTT header line the format requires, and swaps the timecode's decimal separator from a comma to a period.
What these subtitle tools cannot do
- Neither tool touches the video or audio itself — pairing a converted file with a player, or uploading it to a platform, happens outside this page.
- Styling tags inside dialogue, like <i> for italics, are passed through as literal text rather than being interpreted or stripped.
- A file with no line matching the SRT timecode pattern is rejected outright rather than returning an empty result — that usually means the file was saved in a different subtitle format to begin with.
- VTT-only features (cue positioning, STYLE blocks, NOTE comments) are not added during conversion; the output carries over exactly what the source SRT file had, nothing more.