SRT vs VTT: the difference, and when it actually matters

Open an SRT file and a VTT file side by side and they look almost identical — numbered blocks, timestamps, text underneath. The difference that actually matters isn't really the format itself. It's where each one is expected.

What's actually different

WebVTT (.vtt) was built for the web. It's what HTML5 <video> elements expect natively, it uses a period in its timestamps instead of a comma, and it supports things SRT never had — positioning a caption in a specific part of the screen, styling text, tagging who's speaking as a structured cue rather than just typing their name.

SRT (.srt) predates all of that. It came out of a DVD-subtitle-ripping tool in the early 2000s, and its plainness is exactly why it's survived — YouTube, most video editors, and most media players still treat it as the format that just works everywhere, precisely because it doesn't try to do anything clever.

When it actually bites you

Most of the time you can use either one and never notice a difference — anything that reads one format tends to read both. A few situations where it doesn't work out that way:

• A platform with a strict upload requirement — some ad and streaming platforms only accept one format, not both.
• Embedding captions directly in an HTML5 <video> tag via <track> — browsers expect VTT there, not SRT.
• Using cue positioning or styling at all — that's a VTT-only feature. SRT has no equivalent, so it just gets dropped if you convert down to SRT.

Converting between them

Since the difference is mostly structural — a timestamp separator and an optional header line — converting doesn't require re-transcribing anything. It's closer to a find-and-replace than real work. Subtitle Converter does exactly that conversion in your browser, both directions, with nothing uploaded anywhere — it parses the text locally and hands you the other format instantly.