DEV Community

zerone01
zerone01

Posted on

YouTube Chapters Generator: Timestamps That Match the Audio

Somewhere in the past year, chapters went from nice-to-have to default expectation. Viewers skim them. YouTube surfaces them as key moments in search results. And every creator learned the same tedious truth: making them means scrubbing.

On r/NewTubers, one user described their workaround with visible relief: "I've even managed to get reliable chapters with timings from claude.io" (reddit_122k4xs) — the phrasing "managed to" doing a lot of work. On Hacker News, a commenter reviewing a transcript-based tool put it more directly: "光为chapters就愿意用" — roughly, "I'd use it for the chapters alone" (HN thread 30454639).

Chapters alone. That's the whole product for some people. Here's why they're painful and how to stop paying the scrubbing tax.

What chapters actually require

A chapter is a timestamp plus a label, formatted 00:00 Intro in the description, with at least three chapters and the first at 00:00. The hard part isn't the label — an LLM writes labels fine. The hard part is the timestamp being true.

A timestamp that's 40 seconds off is worse than no chapters. Viewers click "Setting up the API key," land mid-sentence in an unrelated section, and bounce. YouTube's key-moments surfacing in search amplifies the damage — the wrong timestamp gets shown to people who haven't even clicked yet.

And true timestamps are exactly what a chat interface can't give you. Paste a transcript into any LLM and ask for chapters, and it will produce confident, plausible, frequently wrong times. The model doesn't hear the audio. It pattern-matches where introductions usually are.

Current options

Manual scrubbing. The standard. For a 20-minute video, expect 20-40 minutes of marking in-and-out points, writing labels, and re-checking. Per video. Forever.

YouTube's automatic chapters. Free, zero effort, and noticeably vague — labels like "Introduction" and "Main content" that carry no keywords and no click appeal. Frequently disabled for smaller channels anyway.

AI chat with pasted transcript. Good labels, unreliable times, for the reason above. The "managed to get reliable chapters" crowd has usually constructed some careful pipeline where the timestamps come from somewhere else and only the labels come from the model.

Dedicated chapter tools. Exist, work, and cost $12-29/month on subscription — a strange price for a task that takes a script five minutes.

The DIY path: chapters with honest timestamps, free

The reliable pattern is to make timestamps come from data, not from a language model's guess:

  1. Generate a timestamped transcript. Whisper emits segment-level and word-level timings: whisper audio.mp3 --model large-v3 --word_timestamps True. YouTube's auto-caption VTT (via yt-dlp --write-auto-sub) also carries timings, at lower text accuracy.
  2. Cut the transcript into 30-90 second windows using the segment boundaries. Don't cut mid-sentence — merge to sentence ends.
  3. Feed the windows to an LLM with this instruction: "Here are timestamped windows from a transcript. Group adjacent windows into 4-10 chapters. Return each chapter as MM:SS Label using the timestamp of its first window. Labels: specific, under 40 characters, keyword-bearing. Do not alter timestamps."
  4. Spot-check the first and last chapter boundaries by jumping to those times in your editor. This is the 60 seconds of QA that catches grouping mistakes.
  5. Paste into the description with 00:00 as the first entry (YouTube requires the first chapter at zero).

That pipeline produces trustworthy chapters for the cost of a Whisper run and a couple of API calls. It's genuinely fine. Its failure point is setup friction — getting from "I have a video" to "I have a word-timestamped transcript" is still the expensive step, especially if your audio has accents or unusual names that corrupt the segmentation.

How postwriter.cn does it

Chapters are one output of the main pipeline at postwriter.cn. Upload the video once; the audio alignment produces word-level timings, chapter breaks are chosen from those timings, labels are written from the corrected transcript. The timestamps are read from the audio, not guessed, which is the entire difference between chapters that help and chapters that mislead.

Since the transcript feeding the chapter labels is the same corrected transcript that drives your description, SRT, and social copy, the proper nouns stay consistent across everything — the chapter says the same guest name the description says.

The correction loop matters here too: when you fix a misheard term on the review page, it enters your personal dictionary, so your next upload's chapters are built on a transcript that's already more accurate. Chapters for video 30 take less of your attention than chapters for video 3.

Free in beta. $39 for 3 years at founder pricing — and per the HN commenter above, chapters alone can carry that value.

FAQ

Do chapters affect YouTube SEO?
Indirectly but really. YouTube can surface chapters as "key moments" in search results, effectively multiplying your titles. Chapters also improve average view duration on longer videos by letting viewers skip to relevant sections, and watch-time signals feed ranking.

How many chapters should a video have?
One per 1-3 minutes of video as a rule of thumb, minimum three (YouTube's floor for enabling chapters), each chapter at least 10 seconds long. A 15-minute video: 6-12 chapters.

Why do my chapters not show up?
The three most common causes: first timestamp isn't 00:00, fewer than three chapters, or a timestamp in the list doesn't match a real moment (YouTube validates loosely, but formatting errors like 0:00 vs 00:00 in mixed styles can break parsing).

Are auto-generated chapters from YouTube good enough?
For search signal, marginally. For viewers, no — generic labels get few key-moment clicks, and you don't control what YouTube picks. Specific, keyword-bearing labels out-perform.

Can I get chapters from just an audio file, no video?
Yes. The pipeline only needs audio. Podcasters use the same chapter output for show notes and episode markers.

Top comments (0)