What is an SRT file?

An SRT file is a plain text subtitle file. The name comes from SubRip, the program that introduced it, and the file extension is .srt. Inside there is nothing but numbered blocks: a cue number, the moment the line appears and disappears, and the words themselves.

That is the entire format. It carries no fonts, no colours and no positioning, and it never touches your video file: it sits beside it as a separate sidecar the player loads on request. Having almost no features is precisely why nearly every editor, player and platform can read it.

Below is what a single cue looks like, what each part of it does, how to open and play one, and the handful of rules that decide whether a player accepts your file or silently shows nothing at all.

1
00:00:01,000 --> 00:00:03,500
Welcome to the show

2
00:00:03,500 --> 00:00:07,120
Today we are talking about
how subtitles actually work

Step-by-step guide

Step 1: Look at one cue

A cue is four things stacked: the number 1 on its own line, then the time line 00:00:01,000 --> 00:00:03,500, then the text Welcome to the show, then a blank line. Repeat that block for every line of dialogue and you have an SRT file.

Step 2: Read the time line

Two timestamps separated by an arrow, each written as hours, minutes, seconds, a comma, and three digits of milliseconds. The comma is not a style choice: WebVTT puts a dot there, and strict SRT parsers reject a cue that has one.

Step 3: Know what the file extension means

The .srt extension tells a player that this is SubRip text and nothing else. There is no compression and no header, so the file opens in Notepad, TextEdit or any code editor and reads exactly as it is stored on disk.

Step 4: Open and play one

Put the .srt beside the video with the same name, as in interview.mp4 and interview.srt, and VLC or MPV loads it automatically. You can also drag the subtitle file onto a playing video in VLC, or add it from the subtitle menu.

Step 5: Know what SRT cannot do

No fonts, colours, positioning or karaoke timing, and no styling that travels with the file. ASS carries all of that and WebVTT carries some of it. For most creators the missing features cost nothing, because platforms apply their own styling anyway.

Step 6: Save it as UTF-8

Encoding is the first thing that breaks on international text. Save as UTF-8, and avoid routing subtitles through a word processor, which quietly swaps straight quotes for curly ones and can trip up older players.

Step 7: Check it before you rely on it

Import the file into the player or editor that will actually use it. One invalid time line can stop everything after it from appearing, and the failure is silent: the video plays normally and the subtitles simply are not there.

Tips for better subtitles

• Name the subtitle file exactly like the video so players pair them automatically.
• One language per file, with a language code in the name when you have several.
• Save as UTF-8; it is the first thing to break on accents and non-Latin script.
• Keep a cue on screen for roughly one to six seconds.
• Do not paste subtitle text through a word processor: it introduces curly quotes.
• Copy the file before any bulk find-and-replace across timecodes.

Common mistakes

• Thinking an SRT changes the video It never touches the video file. The subtitles are a separate text file the player reads, which is why correcting a typo means overwriting a few kilobytes rather than re-exporting anything.
• Using dots instead of commas before milliseconds That is WebVTT syntax. Some players forgive it and many refuse the cue outright, so a file that looks perfectly fine in an editor can show nothing during playback.
• Mixing two languages in one file Viewers get both lines at once and platforms cannot label the track. Keep one language per file and put the language code in the name.
• Saving in the wrong encoding Anything other than UTF-8 turns accents and non-Latin script into question marks. The text is not lost, but every affected line has to be retyped by hand.

SRT vs WebVTT vs plain text

FAQ

Conclusion

An SRT file is a list of numbered cues, each with a start time, an end time and a line or two of text, saved as plain text with a .srt extension. Once you have opened one, there is nothing further to learn about the format itself.

Its limits are the reason it outlived richer formats. Because it stores no styling, it moves between editors, players and platforms with nothing lost in translation.

The quickest way to understand it is to make one: convert a short recording, open the result in a text editor, and read the cues next to the audio they came from.

Related guides

• How SRT files work
• Subtitle formats explained
• How to edit an SRT file
• SRT vs VTT: what is the difference?