FOR THE TIMESTAMPS YOU ALREADY WROTE

Check the chapters.
Keep your words.

Find timestamp problems before pasting your chapter list into YouTube. Nothing gets sorted, deleted or rewritten.

Local text check · no video link or upload

One timestamp and title per line. Use minutes:seconds or hours:minutes:seconds. This checks the chapter block, not a whole video description.

Needed to check the last chapter’s length. We never fetch the video.

Up to 20,000 characters and 500 lines. Your input stays in this tab; refreshing clears it.

What gets checked—and what stays unknown

YouTube’s chapter instructions ask for a first timestamp at 00:00, at least three timestamps in ascending order, and chapters at least ten seconds long.

This checks your submitted chapter block in its original order. The supported spelling is minutes:seconds or hours:minutes:seconds, optionally in brackets, followed by a space and a title. This is our supported grammar, not a complete specification of YouTube’s parser.

A small fictional example

00:00 Getting ready
00:20 First try
01:10 What changed

The first two gaps are 20 and 50 seconds. Supply a video duration of 1:30 to check that the last chapter also lasts 20 seconds. Without a supplied duration, its length remains unknown.

There is no automatic sorting, deleting, merging, title generation or added Intro. Malformed rows are reported, not silently ignored. You decide which edits match the video.

A text check cannot inspect Advanced features access, channel restrictions, content eligibility or YouTube processing. A list can pass every available text check and still not appear as video chapters.

Your chapter text stays here.

Inspection and report creation run in your browser. No video is fetched and your chapter list, titles, timestamps, supplied duration and report are not uploaded or saved in browser storage. Copying or downloading a report is deliberate.

Optional Google Analytics and Statsig receive fixed action categories and coarse size/duration buckets—not your input. Eligible US visits may use notice-based measurement unless declined; elsewhere or when policy is unknown, it stays off unless allowed. Saved declines and browser privacy signals override it. Providers may receive connection/device information and a browser identifier when enabled. Ordinary hosting requests still happen. Read the shared privacy notice.