Convert WebVTT to SubRip (.srt)

WebVTT and SubRip encode the same basic idea (a timed list of caption text), but their syntax differs in three concrete ways. First, WebVTT's header line (WEBVTT) and any NOTE/STYLE/REGION blocks have no SRT equivalent and must be dropped. Second, WebVTT separates milliseconds with a period (00:00:06.120) while SRT requires a comma (00:00:06,120), a one-character difference that will make strict SRT parsers reject the file if left unconverted. Third, WebVTT's optional cue identifier can be any string, while SRT expects a strictly sequential integer starting at 1 with no gaps.

SubToolDesk's converter handles all three automatically: it parses the VTT locally with the FileReader API, re-derives clean sequential numbering, swaps the millisecond separator, and discards anything SRT has no syntax for.

How to convert VTT to SRT (step-by-step)

• Drop your .vtt file onto the converter above, or paste its contents into the left pane.
• Confirm the format badge detects VTT.
• Leave Strip formatting tags on so voice tags and position metadata don't end up as literal text in your SRT.
• Press Download to save a correctly-formatted .srt file, or Copy to paste it elsewhere.

Side-by-side: the same cue, two formats

WebVTT:
00:00:06.120 --> 00:00:09.400 align:start
<v Jordan>Happy to be here.

SRT:
1
00:00:06,120 --> 00:00:09,400
Happy to be here.

Why this still matters in 2026

Browser-native captioning and AI transcription tools (YouTube, Zoom, OpenAI Whisper exports) default to WebVTT because it's the HTML5 <track> standard. But a large share of desktop video editors, legacy media players, and subtitle-upload forms for streaming platforms still expect, or only accept, .srt. Converting keeps your captions portable across both worlds without retyping anything or re-syncing timing by hand.

Nothing leaves your browser

Because the conversion is pure text transformation (no video processing, no OCR, no external API), it runs instantly and entirely client-side. That also means it works for confidential recordings (depositions, internal all-hands videos, unreleased trailers) that you'd rather not hand to a third-party server just to reformat a caption file.

Who converts VTT to SRT, and why

Video editors receiving AI-generated captions (Whisper, Otter.ai, Zoom, Teams) often need SRT specifically because their editing suite's subtitle import (Premiere, DaVinci Resolve, Final Cut) was built around the older, more universally supported format. Localization vendors frequently request SRT as their standard intake format regardless of source. And anyone uploading captions to a video platform or ad server that predates widespread WebVTT support will hit a wall trying to upload a .vtt file directly. Converting once, locally, avoids re-exporting from the original captioning tool or re-typing timecodes by hand.

What gets renumbered, and why it's required

WebVTT's cue identifier is optional and, when present, can be any string: a UUID, a timestamp, or nothing at all. SRT's spec is stricter: every cue must carry a sequential integer index starting at 1, with no gaps and no repeats, or many players will refuse to parse the file past the first broken index. SubToolDesk discards whatever identifier (if any) was in the source VTT and generates a clean, gap-free sequence on export, so the result is valid SRT regardless of how irregular the original numbering was.

A note on cue settings and styling

WebVTT's positioning metadata (align:start position:10%, line offsets, and similar settings) has no SRT equivalent. SubRip subtitles always render at a player's default position with no per-cue placement control. That metadata is dropped during conversion rather than left in as stray text, which is what the Strip Formatting Tags toggle controls. If your WebVTT file relies on custom positioning for accessibility or stylistic reasons, that detail won't survive a move to SRT, which is a limitation of the SRT format itself, not of this converter.