Sub Teksto
English Article

SRT File Format Explained: Structure, Timing and Encoding

The SRT file format looks simple, but small mistakes in timing or encoding can break your subtitles. Learn how an SRT file works and how to get it right.

SRT File Format Explained: Structure, Timing and Encoding

Open a subtitle file in a plain text editor for the first time and you may be surprised by how little is inside. No fancy design, no video, just numbers, timestamps and lines of dialogue. That humble layout is the SRT file format, and it quietly powers a huge share of the captions you see on streaming platforms, video players and social media. If you work with video, translation or accessibility, understanding it will save you hours of frustration.

What is an SRT file?

An SRT file is a plain text document that stores subtitles together with the exact moments they should appear. The name comes from SubRip, a small program that once extracted subtitles from DVDs. If you want the technical background, the SubRip article on Wikipedia explains how the .srt file became a de facto standard. Almost every editor, player and upload form accepts it, which is the main reason it has outlived many fancier formats.

Because it is only text, you can open it with Notepad, TextEdit or any code editor. It carries no video data and no styling beyond a few basic tags, so files are tiny and easy to share by email.

The structure of an SRT file format, line by line

Every subtitle in the SRT file format is a block made of four parts. First comes a sequence number, starting at 1. Second is the timing line, which shows the start time, an arrow made of two hyphens and a greater than sign, and the end time, written as hours, minutes, seconds and milliseconds, with a comma before the milliseconds. Third is the subtitle text itself, which can run to one or two lines. Fourth is a blank line that separates it from the next block.

That is all there is. A single missing blank line or a full stop used in place of the comma in a timestamp can make a player skip the whole file, so precision matters. If a subtitle file refuses to load, the culprit is usually one of these tiny slips.

Encoding, the silent troublemaker

Anyone who translates into languages with accents or non Latin scripts should save the file in UTF-8. Otherwise characters such as é, ß, ç or Cyrillic letters can turn into question marks and strange symbols. This is one of the most common problems we see when a translated file moves from a translator's computer to a video platform, and it is entirely avoidable. Always check the encoding setting when you export, and open the finished file once in a text editor to confirm that the accents look right.

Timing and readability rules worth following

A technically valid file can still be a poor viewing experience. Good subtitlers follow a few habits that make text easy to read without pulling attention from the picture.

Keep each subtitle to two lines at most, and aim for around forty to forty two characters per line. Display each block for at least one second, and allow roughly seventeen characters per second as a comfortable reading speed for adults. Split sentences at natural pauses, not in the middle of a phrase, and try to start a subtitle when the speaker starts talking. Leave a short gap, usually a couple of frames, between consecutive blocks so the eye registers the change.

These guidelines matter even more once you translate. German and Finnish often need more characters than English, while Chinese needs far fewer. A line that fits perfectly in the source language may need rewording, not just replacing, in the target language. Translators therefore condense meaning rather than copy every word, a skill that separates professional work from machine output. For a good example of what goes wrong when this is ignored, read about Netflix subtitle translation errors and how they change the way viewers understand a story.

SRT, captions and other formats

People often use the words subtitles and captions as if they were the same, but they are not. Subtitles assume the viewer can hear the audio and need only the dialogue translated. Captions also describe sounds, music and speaker changes for viewers who are deaf or hard of hearing. The SRT format can carry either, which is why it is so flexible. If you want to understand the difference in more depth, this guide on what closed captions are and how they differ from subtitles is a helpful read.

Other formats exist, such as WebVTT for web video, ASS for stylised anime fansubs and STL for broadcast. They add positioning, colours and fonts, but they are heavier and less universal. When in doubt, start with SRT and convert later if a platform asks for something else.

Editing and checking your file

You do not need expensive software to fix a subtitle file. Free subtitle editors let you shift timings, split long lines and preview the result against the video. For quick tweaks, a text editor is enough. Whatever tool you use, play the finished video from beginning to end at least once, because automated checks cannot tell you whether a joke lands or a line flashes by too fast. Communities such as the subtitles community on Reddit are generous with advice on software and troubleshooting.

A small file with a big job

An SRT file may look like nothing more than a list of numbers and sentences, yet it is the bridge between your video and an audience that speaks another language. Learn its structure, respect its timing rules, save it in the right encoding and have a native speaker review the translation. Do that, and your subtitles will feel invisible in the best possible way, letting viewers focus on the story rather than on the text at the bottom of the screen.

Boletín

Sé el primero.

Suscríbase a nuestro boletín