VTT to SRT Converter

VTT (WebVTT) and SRT (SubRip Text) carry identical timing data and caption text, but they're incompatible at the syntax level — which is why a VTT file downloaded from YouTube, Vimeo, or a browser-based player refuses to import into Premiere Pro, DaVinci Resolve, Final Cut Pro, or any subtitle database that expects SRT. The AT USE VTT to SRT Converter bridges that gap: paste or drop in a .vtt file, and the output is a conforming .srt file with the same timing and text, ready to open in any SRT-compatible application. Everything runs in your browser — no file ever leaves your device.

What changes in the conversion

The two formats differ in three specific ways. First, VTT timestamps use a dot as the millisecond separator (00:00:01.000 --> 00:00:04.500); SRT uses a comma (00:00:01,000 --> 00:00:04,500). Second, VTT files begin with a WEBVTT header line and may include optional NOTE, STYLE, and REGION blocks — none of which exist in SRT. Third, VTT cues can have text identifiers instead of numeric IDs; SRT requires sequential integers starting at 1. The converter handles all three: timestamps are rewritten character for character (no rounding, no loss of precision), the WEBVTT header and any cue-block sections are stripped, and all cue identifiers — whether numeric or text-based — are replaced with sequential numbers. VTT-specific inline tags such as voice spans (<v Speaker>) and CSS class annotations (<c.yellow>) are reduced to their plain text content, since SRT has no equivalent tagging system. Line breaks within individual cues are preserved exactly.

Browser-only — no file upload

The conversion runs entirely via JavaScript in your browser using the FileReader API. Your subtitle file is read locally and never sent to a server. This is relevant for subtitle files attached to unreleased content: conference recordings under embargo, client-delivered translation drafts, internal training videos, or any episode where caption text is confidential. The tool works offline once the page has loaded.

Where this conversion comes up in real workflows

The most common case is video editors downloading auto-generated captions from YouTube for footage they're repurposing or re-editing. YouTube's caption export format is VTT; editors working in Premiere Pro, DaVinci Resolve, or Final Cut Pro need SRT. A second common case is subtitle translators: localization clients often supply source VTT files captured from streaming platforms, while translation delivery specs require SRT for import into CAT tools or subtitle editors. A third case is content archivists — anyone preserving streaming video for offline storage typically converts VTT to SRT, since SRT is the more universally readable format with no format-specific header or browser-centric assumptions. LMS platforms (Moodle, Canvas, Teachable) that accept caption uploads typically specify SRT rather than VTT; course creators who recorded to YouTube and exported captions land in the same conversion step.