CreatorToolWorks

YouTube tools

YouTube Subtitle File Checker

Check local SRT and SBV subtitle structure, cue timings, and overlaps before uploading to YouTube. Your subtitle file stays in your browser.

Check your subtitle file

Your subtitle file stays in your browser. CreatorToolWorks reads the local text only to perform these checks. Nothing is uploaded.

Input method

Choose .srt or .sbv for full checks. Other YouTube-listed extensions receive information only. All file types are selectable so the checker can explain format support.

CreatorToolWorks checks up to 1 MiB per local file, 1,048,576 pasted characters, and 10,000 cues. These are tool processing limits, not YouTube limits.

Neutral — choose a subtitle file or paste text to check it.

Copy is available after SRT or SBV structural checks pass.

Browser-decoded text is checked locally. This does not prove the original file encoding or guarantee YouTube acceptance, processing, styling, or display.

How to use

  1. Choose a local SRT or SBV file, or select Paste subtitle text and choose its format.
  2. File checks run after selection. For pasted text, select Check pasted text after each edit or parser change.
  3. Review errors, timing notes, summary metrics, and the plain-text cue preview.
  4. When structural checks pass, copy the checked text. Review it against your actual video before uploading through YouTube Studio.

Supported subtitle formats on YouTube

YouTube lists basic SubRip and SubViewer files (.srt, .sbv, .sub), as well as other basic, advanced, and broadcast formats. Basic SRT and SubViewer support does not include style markup. This checker fully parses only .srt and .sbv. Extensions such as .sub, .mpsub, .lrc, .cap, .smi, .sami, .rt, .vtt, .ttml, .dfxp, .scc, .stl, .tds, .cin, .asc receive format information only; their contents are not validated.

SRT vs SBV

SRT has a numeric cue identifier, a timing line using an arrow, and caption text. SBV uses a comma between two timecodes and does not need cue numbers. Separate cues with blank lines. Choose the matching paste parser; this tool never converts or repairs content.

SRT timing
HH:MM:SS,mmm --> HH:MM:SS,mmm
SBV timing
H:MM:SS.mmm,H:MM:SS.mmm

What the results mean

  • Neutral: no check yet. Recognized but unparsed files show Info and are not called invalid.
  • Ready: at least one cue parsed, every cue has text and a valid increasing time window, and cues are in start-time order.
  • Review: structural checks passed, with timing or numbering notes. The checked text is still ready for copying.
  • Error: malformed structure, missing text, invalid timecodes, an end at or before its start, out-of-order cues, empty/unreadable input, unrelated files, or a local processing bound. Copy is disabled.

These are CreatorToolWorks parser results. They do not guarantee YouTube will accept, publish, display, style, or process the captions exactly as shown.

Timing and overlap checks

A cue that starts before an earlier cue starts is an Error. A cue that starts before an earlier active cue ends produces Review. Overlapping cues counts later cues whose window overlaps an earlier active window, including nested windows; it is not a count of every overlapping pair. These cues overlap in time. You may want to review the timing before upload.

Overlap review is a local timing check, not a published YouTube prohibition. Gaps, duplicates, or changes in SRT numbering produce Review rather than a claimed YouTube failure. The first identifier does not have to be 1. The parser requires numeric, safely handled SRT identifiers and never renumbers them.

UTF-8 and file limitations

YouTube says basic SRT and SubViewer files must use plain UTF-8. The browser reads your local file as text; this checker cannot prove its original encoding. A leading UTF-8 BOM is removed, and CRLF or CR line endings become LF for checking and copying. Other source text, spacing, numbering, and timings are preserved. No silent cleanup, retiming, or format conversion is performed.

CreatorToolWorks limits local files to 1 MiB, pasted text to 1,048,576 characters, and input to 10,000 cue blocks to keep checks responsive. These are tool processing limits, not YouTube file-size or cue-count rules. The preview shows 100 cues per page; all accepted cues are checked.

Methodology and limitations

A small deterministic parser checks conventional blank-line-separated SRT/SBV, timestamp components, safe numeric handling, nonempty cue text, cue windows, and start-time order. SRT uses at least two hour digits; SBV uses one or more. Minutes and seconds must be 00–59 and milliseconds must have three digits. Caption content is displayed as plain text, including any markup.

The checker cannot determine final YouTube processing success, caption language accuracy, spelling or grammar quality, translation accuracy, accessibility quality, speaker-label correctness, synchronization against the actual video, final styling or positioning, or whether YouTube will alter presentation. Watch the caption track with your video and review it in YouTube Studio. This tool produces no quality, accessibility, SEO, or timing score.

FAQ

Does Ready guarantee a successful YouTube upload?
No. Ready means the local SRT/SBV structure passed these checks. YouTube performs its own processing, and you still need to review the captions with your video.
Can I check a VTT, TTML, SCC, or STL file?
The checker recognizes their listed extensions informationally, but does not parse their contents. They are not marked invalid just because full checks are unavailable.
Will Copy fix timing or numbering?
No. It copies the original checked text with only BOM removal and line-ending normalization. Fix any issues in your source and check again.
Does my file leave my browser?
No. There is no server upload, caption-processing service, API, or login. Your subtitle file stays in your browser.

Official sources

Related tools