A VTT file (Web Video Text Tracks file, also called WebVTT) is a plain-text file with the .vtt extension that holds timed text, such as subtitles, captions, and chapter markers, synchronized with HTML5 video and audio content. The format is defined in the W3C WebVTT specification, and browsers read it through the HTML <track> element, as the MDN WebVTT reference describes. VTT files support text styling, speaker identification, and positioning, and the W3C Web Accessibility Initiative calls WebVTT the most common format for captions on the web.
Key takeaways
WEBVTT, followed by cues. Each cue has a start time, an arrow (-->), an end time, and the caption text.00:00:01.000). SRT timestamps use a comma (00:00:01,000).<track> element or play it alongside a video in VLC.VTT files follow a specific structure that browsers and video players can interpret. Every VTT file contains these core components:
Here’s what a basic VTT file looks like:
WEBVTT
00:00:01.000 --> 00:00:04.500
Welcome to today's presentation
on transcription best practices.
00:00:05.000 --> 00:00:08.750
We'll cover everything you need
to know about caption formats. Notice that VTT timestamps use periods before milliseconds (00:00:01.000), while SRT files use commas. This small difference matters. The WebVTT specification requires the period, so a timestamp written with a comma is not valid in a VTT file. The hours part is optional in VTT, which means 00:01.000 is also a valid timestamp. A cue can also carry an optional identifier on the line above its timestamps.
What sets VTT apart from simpler formats is its support for rich formatting:
<v Speaker Name> tags label who’s talkingThese capabilities make VTT files particularly valuable for accessible web content where styling and speaker clarity enhance comprehension.
One caution from the W3C Web Accessibility Initiative: support for caption positioning and styling in browsers and media players is inconsistent, and most web videos use the player’s default caption style. Test styled VTT files in the players your audience uses.
VTT files are plain text, so you have several options for viewing and editing them:
Text Editors: Any basic text editor (Notepad, TextEdit, VS Code) can open VTT files. You’ll see the raw text and timestamps, making it easy to make quick corrections.
Media Players: VLC media player opens an external subtitle file automatically when it has the same name as your video file. The VLC 3.0 release notes list WebVTT subtitle support, including CSS styling.
Web Browsers: Browsers display VTT files through the <track> element inside a <video> or <audio> tag. MDN documents WebVTT (.vtt) as the format for <track> files. This is how most viewers actually experience your captions.
Video Platforms: YouTube accepts .vtt uploads. As of November 2026, YouTube Help lists WebVTT as an “initial implementation” that supports positioning and limits styling to bold, italic, and underline tags.
Subtitle Editors: Dedicated tools provide synchronized playback alongside the caption text, letting you adjust timing while watching the video.
You have two primary paths for creating VTT files:
Manual Creation: Open a text editor, add the “WEBVTT” header, then write your cues with accurate timestamps. Save the file as UTF-8 with the .vtt extension. This approach works for short clips but becomes slow for longer content, because every cue needs its own start and end time.
Automated Generation: Transcription software analyzes your audio or video and generates time-coded VTT files automatically. AI transcription tools can also label speakers. Sonix combines automated transcription with VTT export, so the speaker labels and time codes come from the same transcript.
Sonix creates a VTT file from an audio or video file that you upload. Sonix exports VTT, but it does not import VTT files, so you start from the media file. The steps below follow the Sonix help center as of November 2026:
Sonix states that the whole process takes about 5 to 6 minutes for each hour of video. The same project can also export SRT and TTML, so you do not redo the timing for each format. If you translate the transcript, you can export a VTT file for each language with the original cue timing.
To try it on your own file, upload it to Sonix and export the VTT. The free trial includes 30 minutes of transcription with no credit card required. After the trial, Pay As You Go costs $10 per hour of audio or video (pricing checked November 2026).
Despite VTT’s technical advantages, you’ll often need both formats. LinkedIn, for example, asks for an SRT (SubRip Subtitle) file when you add closed captions to a video, while the HTML <track> element on your website uses VTT.
The table below compares WebVTT with SubRip (.srt) and TTML, three subtitle file formats that YouTube accepts and Sonix exports.
| WebVTT (.vtt) | SubRip (.srt) | TTML (.ttml) | |
|---|---|---|---|
| Defined by | W3C WebVTT specification (Candidate Recommendation Draft dated 20 May 2026) | No W3C specification. The Matroska documentation describes it as “perhaps the most basic of all subtitle formats” | W3C Timed Text Markup Language (TTML2 is a W3C Recommendation) |
| File type | Plain text, UTF-8 | Plain text | XML |
| Required header | “WEBVTT” on the first line | None | No text header (XML document) |
| Timestamps | Period before milliseconds (00:00:01.000) | Comma before milliseconds (00:00:01,000) | begin, end, and dur attributes on XML elements |
| Cue numbering | Optional cue identifier | A sequence number starts each block | No cue numbers |
| Styling and positioning | Yes: cue settings, formatting tags, and CSS with ::cue | Timing and text only in the basic format. YouTube recognizes no style markup in .srt files | Yes: styling and layout are part of the specification |
Works in the HTML <track> element | Yes | No | No |
| YouTube upload (as of November 2026) | Yes | Yes | Yes |
| Sonix export | Yes | Yes | Yes |
| Sonix import (align with media) | No | Yes | No |
The conversion from SRT to VTT is mostly mechanical: add the “WEBVTT” header and change the comma in each timestamp to a period. The SRT sequence numbers can stay, because VTT allows a cue identifier above each timestamp line. Going from VTT to SRT reverses those steps and drops any VTT styling, as our guide on how to convert VTT to SRT explains.
Rather than maintaining separate files manually, automated subtitle tools can export both formats from a single source transcript. This ensures consistency across platforms while saving duplicate effort.
Even the best automated captions benefit from human review. When editing VTT files, focus on:
Timing Adjustments: Play the video and check that each cue appears when its words are spoken and stays on screen long enough to read. As one published benchmark, the Netflix English timed text style guide sets a reading speed limit of up to 20 characters per second for adult programs.
Text Accuracy: One wrong word can change meaning entirely. “Now” becoming “not” reverses the message. Review auto-generated captions against the actual audio.
Speaker Labels: For interviews, depositions, or panel discussions, clear speaker identification helps viewers follow the conversation.
Line Breaks: Keep each caption to two lines maximum with roughly 42 characters per line. Those are the limits in the Netflix English timed text style guide, and they are a common reference point for subtitle line length.
Professional workflows often use browser-based editors that sync caption text with video playback, letting you spot timing issues and make corrections while watching.
VTT files serve two increasingly important functions beyond basic subtitling:
Accessibility Compliance: WCAG Success Criterion 1.2.2 (Level A) requires captions for prerecorded audio content in synchronized media. In the United States, the Section 508 standards require electronic content to conform to WCAG 2.0 Level A and Level AA, and the ADA Title II web rule sets WCAG 2.1 Level AA as the technical standard for state and local government web content. The European Accessibility Act applies to e-commerce and other covered consumer services provided after 28 June 2025. None of these rules name a file format, but the W3C guidance on captions describes WebVTT as the most common caption format on the web. A <track> element can also carry VTT text descriptions of the video (the “descriptions” kind) and chapter titles.
Search Visibility: Be careful with claims here. Google’s video best practices documentation does not mention caption files (checked November 2026), so a VTT file on its own is not a documented ranking factor. What a VTT file does give you is the full text of your video with timestamps. You can publish that text on the page as a transcript, which gives readers and search engines the spoken content in plain HTML. For researchers analyzing interview footage, legal teams searching deposition archives, or marketers reusing video content, that text makes the video searchable.
VTT files support text styling, positioning, speaker labels, and CSS customization, while basic SRT files contain only numbered cues with timestamps and text. VTT uses periods for milliseconds (00:00:01.000) and SRT uses commas (00:00:01,000). VTT is the format browsers use with the HTML <track> element. SRT is the simpler format that platforms such as YouTube and LinkedIn accept.
Yes. The core conversion involves changing comma separators to periods and adding the “WEBVTT” header. If you still have the original audio or video, a transcription platform that exports both formats removes the manual step. Sonix, for example, exports SRT and VTT from the same transcript.
A VTT file is plain text, so you can open it in a text editor, copy the caption text, and delete the timestamp lines to get a plain transcript. Sonix does not import VTT files. If you have the original audio or video, you can upload that to Sonix instead and export the transcript as DOCX, TXT, or PDF, plus a VTT file from the same project.
Not directly, as far as Google documents. Google’s video best practices page does not mention caption files (checked November 2026). The practical benefit is indirect: a VTT file contains the full spoken text of your video, and you can publish that text on the page as a transcript that readers and search engines can read.
All major browsers support VTT files through the HTML <track> element. According to caniuse data, support starts at Chrome 23, Firefox 31, Safari 6, and Edge 12. Firefox does not yet support the ::cue() selector with an argument, so advanced cue styling can look different there.
Add a <track> element inside your <video> tag pointing to your VTT file: <track src="captions.vtt" kind="subtitles" srclang="en" label="English">. Viewers can then toggle captions using the player’s built-in controls.
Have a video that needs captions? Upload it to Sonix, split the transcript into subtitles, and export the VTT file.
Converting an SRT file to VTT allows you to use existing subtitles with HTML5 video…
Translating a video into English can make recorded presentations, interviews, training materials, and other content…
Google Translate can translate live speech, but it does not offer a standard feature for…
Adding captions to YouTube Shorts makes spoken content easier to follow, including when viewers watch…
Data-driven insights on how AI-powered transcription is transforming workplace productivity and meeting documentation Key Takeaways…
Zoom transcription is the process of converting spoken content from Zoom meetings into written text,…
This website uses cookies.