Structure
Overlapping cues, backwards or zero-length timing, cues out of order, and cues with no text.
Subtitle validator
Paste an SRT or VTT file and see every overlapping cue, backwards timestamp, overlong line, and caption that goes past a readable speed. The check runs in your browser and reports only.
Browser subtitle checker
Fastest cue in this file reads at 355.0 characters per second. The Netflix, adult programs profile allows up to 20.
The check runs in your browser and reports only. It does not change the file. Warnings are style limits for the selected profile, not errors in the file itself.
A subtitle file can be badly broken and still load without complaint. Players are forgiving, so the problems show up in front of an audience rather than at export. Two cues overlapping puts two captions on screen at once. A cue that ends before it starts either vanishes or hangs, depending on the player. A caption that flashes for two tenths of a second is technically present and practically unreadable.
Reading speed is the fault people notice without being able to name it. If a line is long and the cue is short, viewers feel rushed and stop reading. Netflix puts a number on this in its Timed Text Style Guide: up to 20 characters per second for adult programs, up to 17 for children's programs, with 42 characters per line, a minimum of five sixths of a second per subtitle event and a maximum of seven seconds.
Those numbers were written for long-form streaming, and they are a reasonable default for most video. For vertical short-form the line length matters more than the specification suggests, because a phone frame gives captions a much narrower safe area than a widescreen one.
Overlapping cues, backwards or zero-length timing, cues out of order, and cues with no text.
Characters per second per cue, line length, and how many lines a single cue uses.
Cues held too briefly to read, and cues left on screen longer than the profile allows.
The validator reads SRT and WebVTT. If what you have is a styled ASS or SSA file, or an SBV file from YouTube Studio, convert it first and check the result.
If every cue is off by the same amount, or the file slides further out the longer it plays, that is a whole-file timing fault rather than a set of individual mistakes. Correct it with the subtitle timing shifter and read the guide to out-of-sync subtitles to tell the two apart.
Line lengths here are counted in grapheme clusters, the units a reader perceives, rather than in code units. For English the two are the same number. For Devanagari, Kannada and the other Indic scripts they are not, and a naive count reports those lines at close to double their real length. The guide to subtitle character limits explains what that fixes and, just as usefully, what it does not: no character count measures width or height, so Nastaliq and vertically stacked scripts still need a look in the player.
Reading speed and line length warnings are wording problems, not timing problems. The fix is to shorten the line or split the cue, which is work best done where the caption text is still editable. Start from the video in the AutoCaption caption generator, and use the caption line break guide for where to split. If you need the file in another format afterwards, the SRT to VTT converter handles that.
Overlapping cues, cues that end before they start, cues out of order, cues with timing but no text, cues held too briefly or too long, lines above the character limit, more lines than the profile allows, and reading speed in characters per second.
Netflix publishes up to 20 characters per second for adult programs and up to 17 for children's programs in its Timed Text Style Guide, alongside 42 characters per line. Those are the numbers the Netflix profiles here check against.
No. Errors mean the file is structurally wrong, such as a cue that ends before it starts or two captions on screen at once. Warnings mean the file breaks a style limit for the profile you picked, which may be fine depending on where the video is going.
Vertical video gives captions a much narrower safe area than a widescreen frame, so a line that fits comfortably on a television runs past the edge on a phone. That profile is a practical working limit rather than a published external standard.
No. The validator reports and nothing else. It runs in your browser, reads the file locally, and leaves the file exactly as it was.
Timing faults that affect the whole file are usually an offset or a frame-rate mismatch, which the subtitle timing shifter handles. Wording, line breaks, and cue boundaries are best corrected where the caption text is still editable, in the AutoCaption caption generator. Open the caption generator.
Generate the track from the video, fix the wording and the cue boundaries, then export SRT, VTT, text, or a captioned video.