VTT to SRT Converter
Drop a WebVTT file, get a universally-compatible SRT ready for any desktop player or video editor.
Drop your VTT file here
Converts to .srt — stays on your device
Why convert VTT to SRT?
- Importing web-scraped VTT captions into DaVinci Resolve, Premiere Pro, or Final Cut Pro — all of which accept SRT natively but treat VTT inconsistently.
- Loading captions into VLC, mpv, or an older smart TV media app that doesn't recognize the WebVTT extension.
- Cleaning up auto-generated YouTube VTT downloads in Subtitle Edit or Aegisub — both default to SRT as the primary working format.
- Shipping translation work to a client whose workflow (ProTranslating, Smartling, memoQ) expects SRT for captioning deliverables.
- Merging captions downloaded as VTT from a learning platform (Coursera, edX, MasterClass) into a desktop archive of course files.
- Re-importing VTT captions into Descript or Rev after editing elsewhere — SRT is the more reliable round-trip format.
How our converter works
Your VTT is parsed into a cue list, the 'WEBVTT' header is stripped, and the result is re-emitted as numbered SRT blocks with comma-separated milliseconds (VTT uses periods, SRT uses commas). Styling metadata specific to VTT — region definitions, cue settings, style blocks — is dropped since SRT can't represent them. Plain text and basic inline tags carry through. Runs entirely in your browser; nothing is uploaded.
VTT vs SRT — what's the difference?
| Feature | VTT | SRT |
|---|---|---|
| Header | WEBVTT required | None — numbered cues start immediately |
| Timestamp separator | Period | Comma |
| Cue settings | Yes — positioning, alignment | No — dropped on conversion |
| Style blocks | Yes | No |
| Best for | HTML5 video, web delivery | Desktop players, video editors, transcription |
Frequently asked questions
Why doesn't my video editor import VTT directly?
Premiere Pro, DaVinci Resolve, Final Cut Pro, and most desktop editors were built around SRT. VTT support is uneven — some accept it, some ignore the header, some fail silently. Converting to SRT guarantees a clean import.
Do cue positioning and styling survive?
No. VTT's positioning, alignment, and style classes have no equivalent in SRT. Timings and plain text carry across; everything else is dropped. Keep the VTT as the master if you need the styling later.
What about auto-generated YouTube VTT captions?
They convert cleanly. YouTube's auto-captions use plain cues without positioning, so nothing meaningful is lost in the round trip.
Can I edit the SRT after conversion?
Yes — SRT is plain text. Open it in any editor. For anything more than a quick fix, Subtitle Edit (Windows) or Aegisub (cross-platform) are free and purpose-built.
Are my caption files uploaded?
No. The conversion runs entirely in your browser. Captions for unreleased courses, embargoed webinars, or client-confidential videos never leave your device.
Does this handle batch conversion?
Yes. Drop multiple VTT files; each becomes its own .srt. For four or more files, the output is packaged as a ZIP.
About the VTT format
WebVTT (Web Video Text Tracks) is the W3C's web-native captioning format, designed for use with the HTML5 <track> element. It extends SRT with positioning, cue settings, and CSS-like style blocks, making it richer than SRT at the cost of compatibility with older desktop tooling. SRT (SubRip Text), dating from 2001, is the universal lowest-common-denominator caption format: every media player, every editor, every subtitle extractor reads and writes it. The conversion is the standard bridge between web-first captioning (which arrives as VTT) and desktop video workflows (which expect SRT), losing VTT's styling but preserving the timing and content that matter for 99% of use cases.