Subtitle Validator for SRT and VTT

Subtitle validator checks an SRT or VTT file for supported timing and structure problems before you use it.

UTF-8 source only. Maximum 200,000 characters and 2,000 cues. Files are read in this page; no video upload or transcription. The page loads analytics scripts, so avoid confidential captions.

Paste text or choose file. File extension is a hint, not proof of format.

Supported subset: numbered sequential UTF-8 SRT with comma milliseconds, or WebVTT with dot milliseconds. VTT NOTE, STYLE, REGION, cue settings and header text remain unchanged for same-format shifting; rendering semantics are not checked. Inline timed payloads stop shifting; markup, settings, metadata and nonserial identifiers stop cross-format conversion rather than disappear. Output uses LF and omits BOM. Overlap is advisory; end not after start blocks task use. See W3C WebVTT draft and Library of Congress SRT description. SRT has no universal formal grammar.

Adjust subtitle timing. Convert subtitle format.

Why check a subtitle file?

Find the cue

The report names the physical source line and cue, so a reversed time is easier to locate.

Separate advice

Malformed structure and reversed times are errors, while an intended overlap is only a review advisory.

Check both formats

Choose SRT or WebVTT using the same report flow without changing or repairing the source.

What does the validator inspect?

A cue has a start, arrow, end and optional caption lines. Numbered SRT uses comma milliseconds; WebVTT has its own WEBVTT header and dot milliseconds. A reversed cue such as 00:00:03.000 --> 00:00:01.000 triggers a blocking end-before-start report at its timing line.

WebVTT permits overlapping cues. The report treats overlap as an advisory, not a file-wide error. A NOTE or STYLE block ending at the file end needs no final blank line. A clean result means supported checks found no blocking problems, not that the words match a video or every player accepts it.

Errors and advisories

  • Blocking timingMalformed timestamps, reversed or zero-length cues and out-of-order cue starts name line and cue.
  • Overlap advisoryTwo cue intervals can overlap in WebVTT. Review only if their simultaneous display is unintended.
  • Not checkedCSS styling, region rendering and rich voice or markup semantics are outside these supported checks.

Common Use Cases

Before upload

Inspect cue structure before trying an editor, platform or video player.

After conversion

Check destination file syntax separately rather than assuming a renamed extension suffices.

Find a typo

Use the line-specific report to locate a wrong time or cue index in your source.

How to check SRT or VTT

1

Add source

Paste or open a UTF-8 timed subtitle file. Keep the original for correction.

2

Confirm format

Review detected SRT or VTT; choose the correct format when detection is ambiguous.

3

Read the report

Run the check and read blocking errors, advisories and unchecked features separately.

4

Correct and rerun

Edit the source, check it again, then copy or download the current text report.

Actionable file checks

Named location

The diagnostic includes a source line and a cue where the structure allows one.

Current feedback

Editing input clears the previous report; exports refer only to the most recent check.

Honest result

No blocking errors only means the checks listed here passed; this is not a playback certification.

What a report cannot prove

  • •Listen to media: File structure cannot verify spoken words or synchronization.
  • •Review overlaps: Overlapping WebVTT cues can be intentional, so they remain advisories.
  • •Keep source: The downloaded .txt report does not repair or replace your subtitle file.

Check the next subtitle file

Paste or open the file above and run supported SRT or WebVTT checks.

Correct line-specific issues in the source, then run the checker again before publishing.

Related tools

Frequently Asked Questions

What does the subtitle validator check?

It checks supported SRT and VTT cue structure and time ranges, reporting cue and source line. Advisories are separate.

Are overlapping VTT cues invalid?

No. WebVTT allows overlapping cues. The report marks overlap as a review advisory, not a blocking format error.

Can a NOTE or STYLE block end at the file end?

Yes. A block can end at EOF under WebVTT parsing; a blank final line is not required by itself.

Does a passed check mean captions match my video?

No. Compare timing and words against your media separately.