Can I just change .srt to .vtt?

No. VTT needs a header and usually dot milliseconds. Convert the file rather than renaming the extension.

Can an SRT file contain styling?

Not officially. Some players honour basic HTML-like tags, but support is inconsistent and should not be relied on for delivery.

What breaks an SRT file most often?

Missing blank lines between cues, a dot instead of a comma in the timings, and non-UTF-8 encoding mangling accented characters.

Do sequence numbers have to be in order?

They should be sequential from one. Most players tolerate gaps, but validators and some ingest pipelines do not.

What encoding should an SRT file use?

UTF-8. A file saved in a legacy single-byte encoding will display accented and non-Latin characters incorrectly in most players, and it is the most common cause of broken subtitle delivery.

Definition

What Is an SRT File?

VideoText editorial team. Updated September 13, 2026.

Direct definition

An SRT (SubRip) file is a plain-text subtitle format. Each cue has an index, a start and end timecode using comma milliseconds, one or two lines of text, and a blank line.

The sections below explain how SRT file is used in transcription and subtitle work, what people often mix up, and which VideoText workflow applies when the next step is a file or review pass.

Key takeaways

SRT is widely supported by editors, YouTube, and most subtitle tools.
Timestamps use a comma before milliseconds, not a dot.
An SRT stores timed cues. Creating one from a video is a separate step from understanding the format.

How an SRT cue is structured

A minimal cue looks like this:

1
00:00:01,000 --> 00:00:04,000
Welcome to the recording.
(blank line)

Why SRT is common

It is simple to edit in any text editor and easy to validate. It does not natively carry the styling and region features of WebVTT or TTML.

SRT vs WebVTT

WebVTT is a W3C format for HTML5 video. It uses a WEBVTT header and dot milliseconds. Convert, do not rename the extension, if a player expects VTT.

The structure of a cue

Each cue is four parts: a sequence number on its own line, a timing line with start and end separated by an arrow, one or more lines of text, then a blank line closing the block. That blank line is structural, not cosmetic.

Times are written HH:MM:SS,mmm with a comma before the milliseconds. The comma is the single most common source of confusion when moving between SRT and WebVTT, which uses a dot.

Why it stays the default

SRT carries no styling, no positioning and no metadata, which is exactly why almost everything reads it. There is very little to be incompatible about.

The limitation shows when a job needs a caption placed away from burned-in text, or italics for off-screen speech. SRT cannot express either, so those jobs need WebVTT or a broadcast format.

Frequently asked questions

Can I just change .srt to .vtt?: No. VTT needs a header and usually dot milliseconds. Convert the file rather than renaming the extension.
Can an SRT file contain styling?: Not officially. Some players honour basic HTML-like tags, but support is inconsistent and should not be relied on for delivery.
What breaks an SRT file most often?: Missing blank lines between cues, a dot instead of a comma in the timings, and non-UTF-8 encoding mangling accented characters.
Do sequence numbers have to be in order?: They should be sequential from one. Most players tolerate gaps, but validators and some ingest pipelines do not.
What encoding should an SRT file use?: UTF-8. A file saved in a legacy single-byte encoding will display accented and non-Latin characters incorrectly in most players, and it is the most common cause of broken subtitle delivery.