SRT stands for SubRip Subtitle. It is a plain-text subtitle format that stores subtitle text together with start and end times. Its simplicity is why SRT remains one of the most common exchange formats for video platforms, editors and subtitle workflows.
How an SRT file is structured
An SRT file is made of cue blocks. A clean cue normally contains four parts: a sequence number, a timecode line, one or more text lines and a blank line before the next cue.
| Part | Example | Purpose |
|---|---|---|
| Sequence | 1 | Orders the cue blocks. |
| Timecode | 00:00:01,000 --> 00:00:04,000 | Defines when the subtitle appears and disappears. |
| Text | Welcome to our SRT tutorial. | The text shown to the viewer. |
| Blank line | — | Separates one cue from the next. |
1
00:00:01,000 --> 00:00:04,000
Welcome to our SRT tutorial.
2
00:00:05,500 --> 00:00:08,000
Each cue has timing and text.Understanding SRT timecodes
The common SRT timecode syntax is hours:minutes:seconds,milliseconds. Start and end times are separated by an arrow. The end should be later than the start, and cue order should normally follow the timeline.
Example: 00:01:12,500 --> 00:01:15,800 means the subtitle starts at 1 minute 12.5 seconds and ends at 1 minute 15.8 seconds.
Which encoding should an SRT file use?
UTF-8 is the safest default for modern subtitle workflows, especially for accents and non-Latin scripts. A UTF-8 file without a BOM is often the most portable choice, but support varies by application. If a player shows broken characters, check both the file encoding and the software importing it.
Can SRT store styling?
SRT is primarily a timing-and-text format, not a design format. Some players accept simple HTML-like tags, but support is not consistent across platforms.
- Usually portable: Plain text, line breaks and timing.
- Sometimes supported: Basic tags such as italic or bold, depending on the player.
- Not reliably portable: Fonts, colors, exact screen positions, animations and advanced effects. Use ASS when those features must survive export.
How to create an SRT file
- Create numbered cue blocks starting at 1.
- Add a valid start and end time to each cue.
- Place the subtitle text directly below the timecode.
- Insert a blank line between cue blocks.
- Save the file as UTF-8 with the .srt extension.
- Validate the file and review it against the actual video before publishing.
Common SRT errors
1
00:00:04.000 --> 00:00:01.000
Broken timestamp
3
00:00:03,500 --> 00:00:06,000
This cue overlaps the previous one.| Problem | What happens |
|---|---|
| Invalid timestamp syntax | Players or editors may ignore the cue or reject the file. |
| End time before start time | The cue has an invalid duration. |
| Overlapping cues | Two subtitles can appear at the same time or fail validation. |
| Empty cue | A timestamp exists without visible subtitle text. |
| Broken numbering | Often tolerated by some players, but a clean sequential order is safer for exchange. |
| Wrong text encoding | Accents or non-Latin characters can display incorrectly. |
Technical validity is not the same as readability
A perfectly valid SRT can still be difficult to read. There is no single universal character or reading-speed limit for every platform and language, so editorial review matters.
- Keep each cue on screen long enough to be read comfortably.
- Split long sentences at natural linguistic boundaries.
- Avoid covering several ideas in one very long cue.
- Check mobile as well as desktop playback.
- Review timing visually; a validator can find structure errors but cannot judge every editorial choice.
Where SRT is commonly used
Video platforms
Upload subtitle tracks to platforms and hosting systems that accept SRT.
Editing workflows
Exchange timed text between subtitle editors and video tools.
Translation
Translate text while keeping the original cue timing.
Accessibility
Provide a selectable subtitle track instead of burning text permanently into the video.
A reliable SRT workflow
- Generate or create the first SRT version.
- Correct transcription and punctuation.
- Review cue timing and line breaks.
- Validate structure, numbering and overlaps.
- Translate from the clean master if needed.
- Convert only when the destination requires another format.
- Test the final subtitle file in the real publishing environment.
SRT is popular because it does one job well: it combines readable subtitle text with simple, portable timing. Keep the structure clean, validate it and choose a richer format only when your workflow actually needs richer formatting.
Frequently asked questions
What does SRT stand for?
SRT is commonly expanded as SubRip Subtitle, named after the SubRip subtitle extraction software.
Can I open an SRT file in Notepad?
Yes. SRT is plain text, so it can be opened and edited in standard text editors.
Why does SRT use commas in timecodes?
The common SRT syntax uses commas before milliseconds, for example 00:00:01,500.
Can SRT contain colors and fonts?
Not in a reliably portable way. Some players accept limited tags, but ASS is better for advanced styling.
How do I know whether an SRT file is valid?
Check timestamp syntax, durations, cue order, overlaps, empty blocks and encoding, then review the result against the video.