Subtitle & Caption Checker

Free · No sign-up · Runs in your browser — your file never uploads.Every problem cue, with its timestamp, ready to fix.

The rules it checks

How the checker reads your file

The file is read as plain text in this tab and split into blocks at blank lines. In each block the checker finds the timing line — the one containing --> — and parses its two timestamps: SRT writes them with a comma (00:01:02,500), VTT with a dot, and the hours are optional. The lines after it are the cue's text. A VTT header and NOTE blocks are skipped; a block with no readable timing line is reported as an error, never silently dropped.

Why each rule matters

What this tool cannot tell you

  • It checks timing and shape, not translation quality or accuracy — a perfectly-timed wrong subtitle passes.
  • The thresholds are broadcast conventions, not YouTube rules. Fast CPS in a fast-cut Short is a different judgment than in a lecture.
  • It never hears the audio: it cannot tell whether a cue lines up with the words actually being spoken — only whether the cues are consistent with each other.

Worked example: one bad cue, fixed

An invented example — labelled as such — scored by exactly the rules above:

1
00:00:04,000 --> 00:00:04,600
And this is where the whole experiment completely fell apart on us

That cue packs 66 characters into 0.6 seconds: about 110 characters per second. It also breaks the 42-character line limit and the 0.8-second minimum duration — three flags from one cue. Split at the natural pause and give each half real time:

1
00:00:04,000 --> 00:00:06,000
And this is where the whole experiment

2
00:00:06,000 --> 00:00:07,900
completely fell apart on us

The first cue now runs at 19 characters per second and the second at about 14 — inside every limit, and each line fits a phone screen.

Frequently asked questions

What makes subtitles 'bad' for viewers?

Speed and shape. Text that flashes by faster than people read (over ~20 characters per second is a strain for most audiences), lines longer than ~42 characters that wrap unpredictably, cues shorter than a second, and cues that overlap or nearly touch — each one quietly pushes viewers to turn captions off or leave.

SRT or VTT — does it matter?

YouTube accepts both (and others). VTT supports positioning/styling; SRT is the universal plain format. This checker reads both, using the same timing and readability rules.

Why 42 characters per line?

It's the broadcast subtitling convention (BBC/Netflix style guides cluster around 40–42) because it keeps two lines readable on any screen without covering the picture. It's a guideline, not a YouTube rule — we flag, you decide.

Do captions affect my video's reach?

Captions make videos watchable muted, in noisy places, and in other languages via auto-translate — all real retention and audience effects. YouTube also indexes caption text. What captions don't do is magically rank a video; they're an accessibility and completion feature first.

My auto-captions are full of errors. Fix or replace?

Replace for anything you care about. Auto-captions mangle names and technical terms, and YouTube shows the errors to exactly the viewers who need captions most. Edit the auto-captions in Studio or upload a corrected file — this checker will audit the timing either way.

Do you upload my subtitle file?

No. It's parsed in your browser and forgotten when you close the tab.

Related tools

CreatorChecks is not affiliated with YouTube or Google.