How to use
- Drop your file(s) into the box above — or click it to browse.
- Conversion starts immediately — no settings needed.
- Click Download on each finished file — or Download all (.zip) for a batch. Nothing was uploaded at any point.
Where VTT files come from — and why you need SRT
VTT is what you get when you rip captions from the web: online course platforms, YouTube caption exports, Vimeo, conference recordings, or your own HLS streams. It's perfect in the browser and awkward everywhere else — smart-TV media players, car systems, many hardware set-top boxes, and subtitle editors from the pre-web era expect SRT.
Conversion strips the parts SRT can't express: the WEBVTT header, NOTE and STYLE blocks, cue identifiers, positioning settings like align:start position:10%, and speaker voice tags like <v Alice> (the spoken text is kept, the tag removed). Sequential cue numbers are generated, and the millisecond dot becomes SRT's comma.
| Feature | In VTT | After conversion |
|---|---|---|
| Text & line breaks | Yes | Kept exactly |
| Timing | Dot milliseconds | Comma milliseconds, same values |
| <i>/<b>/<u> styling | Yes | Kept (players support these in SRT) |
| Cue positioning | align/position/line settings | Removed (no SRT equivalent) |
| Voice tags <v Name> | Yes | Tag removed, spoken text kept |
| NOTE / STYLE blocks | Yes | Removed |
When NOT to convert VTT to SRT
- The file is going back into a web player —
<track>needs VTT; converting to SRT would break it. - Positioning matters — VTT can pin cues to screen regions (used for speaker separation and sign captions). SRT has no standard for this, so that layout is permanently lost.
- Karaoke-style timed words — inline per-word timestamps are a VTT feature; SRT flattens them to plain lines.