Podcast Show Notes Generator

Summarizing an episode solves most of this, which is worth knowing because show notes get written badly — they are written last, after the editing, when the episode is already late. So they end up as a paragraph of description and a guest bio.

That is a shame, because timestamped notes are the single feature listeners use most on a long episode.

What listeners actually use

Worth establishing before deciding what to generate, because the answer is not what most podcasters spend their show-notes time on.

Not the summary. The timestamps.

Somebody who has already listened uses show notes to find the bit they want to share. Somebody deciding whether to listen uses them to see whether the episode covers their thing. Both are navigation tasks.

A well-written paragraph serves neither. A list of segments with times serves both, and takes less writing.

The chapter map is most of the work

Everything that follows assumes you have generated one. If you have not, that is a thirty-second job and the rest of this page depends on it.

Run the episode through, take the chapter map, and you have timestamped segments in order with a line describing each.

That is the skeleton of good show notes and the part that takes longest by hand, because doing it manually means scrubbing back through a three-hour recording noting where topics changed.

Tidy the wording so it sounds like your show, and you are most of the way there in about five minutes.

What still needs you

Three things, and they are the three that distinguish notes worth reading from a machine-generated index.

The hook. The first two lines decide whether anyone reads the rest, and generated text is reliably flat there. Write it yourself.

Links. Every book, tool and paper mentioned should be linked, and a transcript gives you the mention but not the URL. This is manual, and it is the part listeners thank you for.

Quotes. A summary paraphrases, so pulling a quote from it puts words in your guest's mouth. Use the timestamp to find the moment and transcribe it properly — see copying a transcript for the exact wording.

Length and format conventions

Show notes have loose conventions worth following, since listeners scan them the same way across shows.

Two or three lines of hook, then the timestamped segments, then links. Guest bio near the bottom, because people who wanted it will scroll and people who did not are trying to get past it.

Segment lines should be short enough to scan in a list — a topic rather than a sentence. A generated map tends toward full sentences, so trimming each line to four or five words is usually the main editing pass.

Chapters in the player

The same timestamps do double duty. Pasted into a YouTube description in the right format, they become clickable chapters in the player itself.

That is worth more than the written notes for most listeners, because it works without leaving the video. The map gives you both from one pass.

If your episode is also distributed as audio, most podcast hosts accept timestamps in the episode description too, though support for clickable chapters varies by app.

Why timestamps help discovery too

Beyond convenience for listeners, segmented episodes are more findable.

Google's documentation on video key moments describes surfacing specific points within a video, each addressing a distinct topic, so someone searching for that topic can jump straight to it.

Well-structured chapters give a long episode many possible entry points rather than one. For a three-hour conversation covering eight subjects, that is the difference between being findable for one thing and eight.

Notes for a back catalogue

If you have a hundred episodes with thin notes, retrofitting them is the highest- value use of this on a podcast.

Old episodes are effectively invisible — nobody scrubs a two-year-old three-hour recording hoping to find something. Adding timestamped segments makes the archive searchable, both for listeners and for you when a guest comes back.

Five a day on the free tier means a hundred-episode catalogue is a few weeks of background work, done in batches while you do something else.

Where it falls down

Speaker attribution. Automatic captions carry no speaker labels, so who said what is inferred from context. On a two-host show with a guest, check before attributing anything by name.

Names and terms. Guest names, company names and technical vocabulary are exactly where automatic transcription fails. Every proper noun in your show notes should be checked — publishing a misspelled guest name is a small thing that reads as carelessness.

Audio-only episodes. This works from YouTube's caption track, so an episode needs a YouTube version.

A five-minute routine

1. Summarize the episode and take the chapter map.
2. Tidy the segment descriptions into your show's voice.
3. Write the hook — two lines, by hand.
4. Add links for everything mentioned, checking each at its timestamp.
5. Verify guest names and any quoted line against the audio.

Steps three to five are the ones that make it yours. Steps one and two used to take an hour and now take five minutes, which is the whole benefit.

What good show notes are worth

More than most podcasters assume, and in a way that compounds.

They are the only searchable surface your episode has. Audio is opaque to search, to skimming and to anyone deciding whether to commit ninety minutes — the notes are where all of that happens.

Which makes the five minutes spent tidying a generated chapter map one of the higher-return things available to a show, particularly one with a back catalogue that is currently invisible.

Frequently asked questions