· 2 min read
SRT and WebVTT are both plain-text timed subtitle formats. They share the basic idea of cues with a start time, end time, and text, but their headers, timestamp punctuation, and support for cue settings differ.
The short comparison
| Format | What stands out |
|---|---|
| SRT | Simple numbered cues with comma milliseconds; widely supported by editors and upload workflows. |
| WebVTT | Starts with WEBVTT, uses dot milliseconds, and can carry cue settings such as line or position. |
Timestamp syntax matters
An SRT timestamp looks like 00:00:01,500. WebVTT uses 00:00:01.500. The cue must also have a positive duration and the file should keep cues in chronological order. A converter should refuse malformed input rather than download a partial file.
Before
00:00:01,500 --> 00:00:03,000
After
00:00:01.500 --> 00:00:03.000
The text and timing are the same; only the format-specific timestamp punctuation changes.
What happens to VTT cue settings?
WebVTT can attach presentation settings to a cue. Basic SRT has no equivalent field, so a safe SRT conversion should warn that those settings cannot be represented. The warning is part of a truthful conversion, not an error to hide.
Which one should you use?
Use the format required by the destination. If you need broad compatibility with a simple subtitle track, SRT is often the practical choice. If you need WebVTT’s web-oriented settings or are working with a browser text track, VTT is the more expressive format.