WebVTT converter
Convert WebVTT files while handling cue settings, regions, comments, chapters, metadata tracks, and SRT compatibility.
.vtt
Format
About WebVTT
WebVTT is the browser-native timed text format used by HTML video and audio tracks. A .vtt file begins with a WEBVTT header and then cue blocks with timestamps that use periods for milliseconds. It can also carry cue identifiers, comments, settings such as position or alignment, regions, chapters, descriptions, and metadata tracks depending on how the player uses it. Our subtitle routes convert VTT to SRT, ASS, TXT, CSV, or JSON. VTT is usually the better web target, while SRT remains common for broad interchange with subtitle tools and video platforms.
The WebVTT specification is more defined than informal SRT, but real files still vary. Some contain only basic captions. Others include NOTE blocks, STYLE blocks, REGION declarations, cue settings, voice spans, classes, and metadata cues that are meaningful only to a custom player. A simple caption converter may preserve text and times while dropping regions or style cues. Encoding should be UTF-8, and the header must appear before cues. Blank lines separate blocks, so accidental whitespace changes can alter parsing. Browser developer tools are often the fastest way to check whether a VTT file loads at all.
Readers and writers include browsers, video platforms, caption editors, streaming workflows, learning systems, podcast tools, and accessibility QA teams. WebVTT is used for captions and subtitles, but also for chapters, descriptions for screen reader workflows, thumbnails, and timed metadata. That broader use means not every VTT should become SRT. If cue payloads contain metadata JSON or chapter titles, a plain caption target may be misleading. CSV and JSON conversions are useful for review, translation, search, and automated checks, while TXT is only a transcript-like extraction for readers and editors downstream.
VTT conversion gotchas appear when targeting simpler formats. VTT to SRT drops the header and usually loses cue settings, regions, CSS classes, and non-caption blocks. VTT to ASS can map timings and text into a styled subtitle script, but styling needs manual work. VTT to TXT removes timing. VTT to CSV or JSON can expose cues for workflows, but metadata cues must be labeled so they are not mistaken for spoken captions. Before converting, identify whether the track kind is subtitles, captions, chapters, descriptions, or metadata. Then verify cue count, timing, and player rendering with the media file.
Convert to WebVTT from…
Common WebVTT problems
A legacy caption editor accepts only SRT.
Use /convert/vtt-to-srt, then review lost cue settings such as position, align, region, and class names.
A QA team needs cues in a spreadsheet.
Use /convert/vtt-to-csv and keep track kind notes so chapters or metadata are not treated as captions.
A transcript needs text without timestamps.
Use /convert/vtt-to-txt, then edit speaker labels and repeated captions for readability.
Styled subtitles are needed for a video renderer.
Use /convert/vtt-to-ass, then add fonts, margins, and positioning because WebVTT styling does not map fully.
Automation needs cue objects for validation.
Use /convert/vtt-to-json and compare cue count with the original WEBVTT file after comments are removed.