Video chapter builder
Build YouTube chapters and show notes from a subtitle file: chapters are named from the real transcript blocks, and every timestamp is validated locally against YouTube rules before you paste it into your description.
About this tool
YouTube chapters fail in predictable ways: timestamps that do not match the video, chapters out of order, no 00:00 opener. Chatbots invent all three because they never saw your file. This builder works from your actual subtitle file — chapter starts snap to real cue times from the SRT or VTT you upload.
The model only names and summarizes chapters from the real transcript blocks. Sorting, monotonic increase and the guaranteed 00:00 first chapter are validated locally against YouTube’s rules before anything is shown, so the block you paste into your description works the first time. You also get a per-chapter summary table and show-notes Markdown for the podcast post.
How to use Video chapter builder
- Add your provider API key in the key panel.
- Upload an SRT/VTT subtitle file (or a plain transcript for untimed chapters).
- Chapters are named from the actual transcript blocks and every timestamp is validated locally against YouTube rules.
- Copy the chapter block straight into your YouTube description and export the show notes.
Keep the original files and inspect the exported result before publishing or sharing it.
Frequently asked questions
Why do the timestamps always work?
They come from your subtitle file, not from the model: chapter starts snap to real cue times, are sorted and checked locally, and a 00:00 first chapter is guaranteed — the three things YouTube requires and chatbots routinely get wrong.
What if I only have a transcript without timestamps?
You still get the chapter list with summaries as show notes, but no timestamp block — YouTube chapters need real times, and this tool will not invent them.
What else is exported?
A per-chapter summary table and a show-notes Markdown file with the chapter list and summaries, ready for a podcast description or blog post.
Where does my transcript go?
Only to the AI provider behind your own key, directly from your browser.
Related tools
- AI chat — Chat with OpenAI, Claude or Gemini using your own API key. Your key stays in your browser; requests go straight to the provider.
- AI summarizer — Summarize long text with your own OpenAI, Claude or Gemini API key. Brief, detailed or bullet-point summaries, all in your browser.
- AI translator — Translate text between 30 languages with your own OpenAI, Claude or Gemini API key. Private by design: key and text stay with you and the provider.
- AI writing assistant — Improve, expand, shorten or re-tone your writing with your own API key. Six editing modes, direct browser-to-provider calls.
- AI code explainer — Paste code and get a plain-English explanation using your own OpenAI, Claude or Gemini API key. Language auto-detect included.
- AI PDF chat — Upload a PDF and ask questions about it. The PDF is parsed in your browser; only the extracted text and your question go to your chosen AI provider.
- AI image analyzer — Upload an image and let AI describe it, extract text (OCR), or identify objects. Uses vision models from OpenAI, Claude or Gemini with your own key.
- AI voice generator — Turn text into natural-sounding speech with OpenAI TTS. Six voices, speed control, play in the browser and download MP3.
- AI data analyst — Upload a CSV and ask questions in plain English. The file is parsed locally; the AI sees only a schema summary and sample rows.
- AI spend analyzer — Turn your AI provider usage export into an independent cost receipt: per-model and per-day breakdowns, spike alerts and a monthly projection. Runs 100% in your browser — your billing data is never uploaded.