Check a subtitle file for errors before a player does.
Paste an SRT or WebVTT file, or choose one, and get every problem in it with the line it is on: the ones a player will act on, and the ones that only make captions harder to read.
How this tool works
- 01
Choose SRT or VTT
The two formats disagree on small things, such as the character before the milliseconds, so the check needs to know which rules apply.
- 02
Paste or choose the file
The file is read in your browser. Nothing is uploaded, and there is nothing to sign up for.
- 03
Fix what it points at
Each problem names its line. Errors first: those are the ones a player will skip, merge or refuse.
Practical guide
What to know before you download
Errors and warnings are different
An error is something a player or browser will act on: a cue with no timing line is never shown, a cue that ends before it starts never appears, two cues with no blank line between them are shown as one, and a WebVTT file without its WEBVTT line is not loaded at all. A warning is a file that plays but reads badly or trips stricter software, such as cues that overlap, cue numbers that skip, or a line too long to read. A file with only warnings is usable; fix the errors first.
The mistakes it looks for
Timing lines in the wrong form, minutes or seconds of 60 or more, cues that end before they start, cues with no text, missing blank lines, stray text above an SRT timing line, cue numbers that do not count up by one, cues that overlap or run out of order, lines over 42 characters, and cues with more than 2 lines. Every one is reported, not only the first, with the line number in the file as you pasted it.
SRT and WebVTT write time differently
SRT puts a comma before the milliseconds (00:00:01,000) and always includes hours. WebVTT uses a full stop (00:00:01.000), may leave the hours out, and must begin with the line WEBVTT. Browsers follow the WebVTT rules strictly, so a comma in a .vtt file makes them skip the cue. Many SRT players accept a full stop, which is why the same slip is only a warning there. Converting between the two with the [SRT to VTT converter](/tools/srt-to-vtt-converter) writes each correctly.
What it does not do
It reports problems and changes nothing: the file you paste is the file you keep. It does not check that the words match the audio or that the timing matches the video; for a file that is consistently early or late, use the [timing shifter](/tools/subtitle-timing-shifter). The 42-character and 2-line limits are common readability guidelines rather than rules of either format, and the [line length guide](/guides/subtitle-line-length) explains where they come from.
Questions about this tool
Does the validator upload my subtitle file?+
No. The file is read and checked in your browser, and nothing about its contents leaves your device.
Will it fix the problems it finds?+
No. It points at each problem and its line so you can decide what to change. Several of the other free tools make specific fixes, such as shifting all timing or converting between formats.
Why is a comma an error in VTT but only a warning in SRT?+
Browsers parse WebVTT strictly and skip a cue whose timestamp uses a comma. SRT has no single formal standard, and many players accept either character, so a full stop in SRT is flagged but still likely to play.
My file has only warnings. Is it broken?+
No. Warnings mean the file will play but may read badly or confuse stricter tools. Overlapping cues and long lines are worth fixing; a skipped cue number rarely matters to a player.
