Guide

SRT vs VTT: What's the Difference?

SRT and VTT both store timed text, and the files look almost the same. The differences are small but decide which players accept them.

What this looks like in mydubly

Export SRT and VTT subtitle files from the same mydubly recognition pass
mydubly Classic subtitle style with white text and black outline on video
Burn styled mydubly captions into an MP4 from the subtitle editor

The differences

Header
VTT files must start with WEBVTT; SRT has no header.
Timestamps
SRT uses a comma for milliseconds (00:00:03,200); VTT uses a dot (00:00:03.200).
Cue numbers
Required in SRT; optional in VTT.
Styling
SRT has none officially; VTT supports cue settings and CSS-style styling.
Where it works
SRT: editors, desktop players, most upload forms. VTT: HTML5 video and web players.

The same cue in both formats

SRT
1
00:00:00,000 --> 00:00:03,200
Today we continue from the last session.
VTT
WEBVTT

00:00:00.000 --> 00:00:03.200
Today we continue from the last session.

Where each format is accepted

YouTube
SRT and VTT both work, along with SBV and several broadcast formats
Vimeo
SRT and WebVTT, plus DFXP, SCC and SAMI
Facebook and LinkedIn
SRT only
HTML5 video on your own site
WebVTT only, through the <track> element
HLS streaming
WebVTT subtitle segments
DaVinci Resolve
SRT, WebVTT and XML-based formats such as TTML
Final Cut Pro
SRT, iTT and CEA-608; WebVTT isn't on its import list
Premiere Pro and CapCut
SRT is the dependable choice; CapCut Web takes SRT only
VLC and most desktop players
Both

When a platform accepts both, SRT is the safer default because nothing in it can be misread. The editor guides for DaVinci Resolve and CapCut cover importing in detail.

SRT or VTT for YouTube

Either works. YouTube reads the timing and text from both and ignores most VTT styling, so the result looks the same to viewers. Upload in YouTube Studio under Subtitles, choose the language, and pick "With timing". If you also publish the same video on your website, keep the VTT for the site's player and upload the SRT to YouTube, so each file goes where it fits best.

What WebVTT can do that SRT can't

VTT started as a web format and carries features SRT never had:

  • Cue settings after the timestamp, such as line:0 or align:start, which move a subtitle to the top of the frame or to one side, for example to keep it off an on-screen caption.
  • A STYLE block with CSS rules for colour, font and background, applied by browsers that support it.
  • NOTE blocks for comments that players ignore, useful for translator notes inside the file.
  • Voice tags such as <v Maria> that mark who is speaking, and REGION blocks for scrolling captions.
  • Other track kinds: chapters, descriptions and metadata use the same format.

Players vary in how much of this they honour. Plain cues work everywhere; styling and regions are best treated as extras that may be dropped.

What converting loses

VTT to SRT drops everything SRT has no place for: cue settings, STYLE and REGION blocks, NOTE comments and voice tags. The text and timing survive. Check any cue that was positioned at the top of the screen, because after conversion it will sit at the bottom and may cover something important. SRT to VTT loses nothing; the file only gains a header and full stops in its timestamps. Simple tags like <i> for italics carry across in both directions in most players.

Converting by hand

  1. SRT to VTT: add WEBVTT on the first line followed by a blank line, then replace the comma before the milliseconds in every timestamp with a full stop. Cue numbers can stay.
  2. VTT to SRT: delete the WEBVTT header and any STYLE, REGION or NOTE blocks, replace the full stop before the milliseconds with a comma, remove cue settings after the end time, and number the cues from 1.
  3. Save as UTF-8 with the right extension, and open the result in a player to confirm it loads.

A find-and-replace across timestamps is risky if the text itself contains times; replace only inside lines that contain an arrow (-->).

SBV, TXT and the rest

SBV is an older YouTube format: no cue numbers, a comma between the start and end times instead of an arrow, and a full stop before the milliseconds. YouTube still accepts it, but almost nothing else does, so convert SBV files to SRT for editors. A TXT file is only a subtitle file if it follows a timed layout; a plain transcript has no timing, and uploading one asks the platform to align it. Broadcast and professional formats such as TTML, SCC and ASS are covered in subtitle file formats.

Getting both from one job

Every mydubly transcript run returns an SRT and a VTT with the same cues, plus a timestamped transcript, in the spoken language or translated into another supported language. Use the SRT generator for editors and social platforms and take the VTT from the same download for your website, or start from the VTT generator page; either way you never need to convert. What is an SRT file explains the SRT layout part by part.

Frequently asked questions

Can browsers play SRT files?

Not natively through the <track> element — browsers require VTT. Some JavaScript players convert SRT on the fly.

Which is better, SRT or VTT?

Neither is better overall. SRT is accepted by more editors and social platforms; VTT is required for HTML5 video on websites and supports positioning and styling. Use the one your destination asks for.

Can I rename a .vtt file to .srt?

No. The header and the full stops in the timestamps stay, and most programs then reject the file. Convert it properly or download the SRT version.

Does Facebook accept VTT files?

Facebook and LinkedIn take SRT files for video captions. Upload the SRT there and keep the VTT for players that need it.