Convert VTT to SRT
Convert VTT to SRT free in your browser. No upload, no signup, no watermark. Files stay on your device.
drop a .vtt file
or click to browse
related
more subtitle converters
see all subtitle converters →guide
how to convert vtt to srt
Drop your VTT file
Drag your VTT file into the drop zone above, or click the box to pick a file from your computer or phone. The browser reads the file directly — nothing uploads.
Click Convert
The page runs subtitle (npm) on your device to decode the WebVTT and encode it as SubRip Subtitles. Most conversions finish in a few seconds; large or codec-heavy files (RAW, video) can take longer.
Download the SRT file
When the conversion finishes, the SRT file is ready to download. Save it anywhere on your device.
FAQ
common questions
Why convert VTT to SRT — isn't VTT the newer format?
SRT is universally supported by desktop players (VLC, MPV, MPC), every NLE (Premiere, Resolve, Final Cut), and most upload platforms including YouTube, Facebook, and many streaming pipelines that don't accept VTT directly. VTT is web-only by design, so SRT remains the safer interchange format outside the browser.
Will I lose styling, positioning, or speaker tags?
Yes — SRT has no concept of cue positioning, CSS classes (<c.classname>), regions, or voice tags (<v Speaker>), so all of those are stripped. Only the plain dialogue text, basic <b>/<i>/<u> tags, and timing survive the conversion.
What happens to inline word-level timestamps used for karaoke-style highlighting?
SRT does not support inline timestamps (<00:00:01.500> mid-cue), so per-word/karaoke timing is flattened — the words still appear, but they all show at once for the cue's duration. If word-level highlighting is essential, keep the VTT.
Will VLC or my smart TV play a VTT file directly?
Modern VLC versions read VTT, but many smart TVs, hardware media players, and older desktop apps only reliably recognise SRT. Converting to SRT (period to comma in timestamps, drop the WEBVTT header and any STYLE/REGION blocks) is the safest path for offline and hardware playback.
Why is the first subtitle missing or numbered wrong after conversion?
Almost always a UTF-8 BOM problem — some editors leave the invisible EF BB BF bytes at the start of the file, which SRT parsers can misread as part of the first cue index. Re-saving as UTF-8 without BOM (and ensuring CRLF or LF line endings are consistent) fixes it in nearly every player.