Check and Repair an SRT File
Does your TV or player refuse to load a subtitle, or do lines disappear? Run it through the checker to see exactly what is wrong — and fix it.
🔒 Runs in your browser. Your files and text are not uploaded.
How to use the SRT Checker & Fixer
- Drop the file or paste its text.
- Set the reading-speed limit in characters per second (20 for adults; 17 for children’s content).
- Choose which problems the fixed copy should repair: sort by time, trim overlaps, repair end ≤ start and tidy spaces.
- Click Check subtitles, read the list of issues and download the fixed SRT.
What the checker looks for
| Issue | Why it matters |
|---|---|
| End time before or equal to start time | The cue is never shown, or some players stop reading the file. |
| Cues out of order | Many players expect ascending times and skip later lines. |
| Overlapping cues | Two subtitles at the same time can stack or hide each other; some TVs reject the file. |
| Empty cues | Blank text can show an empty box and confuse numbering. |
| Reading speed above the limit | Viewers cannot read the text in time. |
| Very short or very long cues | Flashing lines or lines staying too long. |
| Lines over 42 characters or more than two lines | Lines wrap badly on screens and break professional guidelines. |
Which problems are repaired automatically
The fixed copy can sort cues by start time, shorten the end of a cue that runs into the next one, repair cues whose end is not after their start, and trim stray spaces and blank lines. Content issues — such as reading speed or long lines — need an editor’s judgement, so they are only listed, with the line number and a hint.
If the subtitle still does not load
- Make sure the file is saved as UTF-8 and has an .srt extension; see the encoding fixer.
- Put the SRT in the same folder as the video with the same base name.
- Some TVs require Windows (CRLF) line endings and no BOM; try saving with those settings.
Professional guidelines used for the limits
The defaults follow common broadcast and streaming guidance: up to about 42 characters per line, two lines per cue, between roughly 0.8 and 7 seconds on screen, and 17–20 characters per second. Adjust the limits for your own platform; see the timing guide for the rationale.
Frequently asked questions
Is overlapping always an error?
Not in the SRT specification, but many players and hardware devices handle it badly, so it is safer to avoid.
Does the checker change my text?
Only whitespace is tidied if you enable it. Words are never altered.
What reading speed should I enforce?
20 characters per second is a common maximum for adult content, 17 for children’s content. Lower values give viewers more time but need longer cues.
Can it handle VTT or ASS?
Yes, it parses them and the fixed copy is output as SRT.
What does “repair end ≤ start” do?
It sets the end time to a sensible value after the start, based on the text length.
Is my file stored?
No, nothing is uploaded.