VTT to SRT Converter
Convert WebVTT (.vtt) captions downloaded from YouTube, Vimeo or a streaming service into SubRip (.srt), the format understood by VLC, Plex, Kodi, smart TVs and virtually every video editor. Batch conversion included; nothing leaves your computer.
Accepted: .srt, .vtt, .sbv · You can add several files at once.
Your files never leave your device.
How to use this tool
- Drop one or more .vtt files on the box above.
- Review the warnings — for example if a file was missing its WEBVTT header.
- Download the .srt files individually or all at once.
Why convert WebVTT to SRT?
WebVTT is what the web wants, but the rest of the world still speaks SRT. Desktop players such as VLC and MPC-HC, media servers like Plex, Jellyfin and Emby, most smart TVs and set-top boxes, and editing suites including Premiere Pro, DaVinci Resolve and Final Cut load .srt files out of the box. Many of them either ignore .vtt files or handle them poorly, dropping cues or showing raw tags on screen.
SRT is also the lingua franca for subtitle communities, translation tools and OCR software, so converting to it keeps your captions usable everywhere.
What changes during conversion
Timing is translated from 00:01:02.345 to 00:01:02,345 and cues are renumbered sequentially, which SRT requires. WebVTT-only markup — voice tags like <v Speaker>, class spans such as <c.yellow>, ruby annotations and inline karaoke timestamps — is unwrapped so only the spoken text remains. Simple <i>, <b> and <u> tags are kept because SRT players understand them.
Cue settings for position and alignment, NOTE comments, STYLE and REGION blocks have no equivalent in SRT and are removed. Cue identifiers (named or numbered) are discarded as well; SRT numbering is rebuilt from scratch.
Broken files are welcome
Files exported by some tools omit the WEBVTT header, use hour-less timestamps (01:02.345) or mix commas and dots. All of these are parsed correctly and reported as warnings, so you never have to fix a file by hand just to convert it. Encoding is detected automatically, so accented characters in Windows-1252 files come through intact.
Frequently asked questions
- Why does my VTT file from YouTube have duplicate lines?
- Auto-generated YouTube captions use rolling cues where each cue repeats part of the previous one. The converter keeps the cues as they are; use the Fix Subtitles tool afterwards to clean up overlaps if needed.
- Will positioning information be kept?
- No. SRT has no standard way to position text, so cue settings such as line:0 or align:start are dropped. The text and timing are preserved exactly.
- Does the converter work with .webvtt files?
- Yes. The extension does not matter — the content is detected by inspecting the file. You can even feed it an SRT file and it will pass through correctly.
- Are my subtitles sent anywhere?
- Never. Parsing and serialising run in your browser tab. There is no backend and no analytics on your file contents.