What Are Podcast Chapters? A Plain Guide

Podcast chapters are named, time-stamped segments inside a single episode, like "Intro," "Guest's origin story," "The big argument," "Listener questions", that let someone jump straight to the part they want. They're stored either inside the audio file, inside the RSS feed, or as plain timestamps in the episode notes. The catch: which format you use decides which apps actually display them.

That last point is where most of the confusion lives. A host adds chapters, sees them in one app, then a listener swears the episode has none. Both are right. There is no single "podcast chapters" standard, there are four ways to mark them, and each app reads a different subset. Understand the four, and the mystery disappears.

What does a chaptered episode look like?

A chaptered episode is one continuous audio or video file with marker points laid along its timeline, each carrying a start time and a title (and sometimes an image or link). In a supporting app, those markers turn into a tappable list, so a 90-minute interview becomes a menu: skip the ad, jump to the segment you came for, scrub back to a quote.

Nothing about the audio changes. Chapters are metadata sitting beside or inside the file, the episode plays identically with or without them. They exist purely to make a long episode navigable. The longer your episodes run, the more chapters earn their keep, which is why interview, news, and roundtable shows lean on them hardest.

The four chapter formats (and where each one lives)

Here's the part that resolves the "my chapters don't show up" problem. Chapters come in four flavors, defined by where the data is stored. Knowing which one you used tells you which apps can read it.

1. Embedded file chapters (ID3 / MP4). The chapter marks live inside the media file itself, as ID3 chapter frames in an MP3 or AAC, or in the header of an MP4. They travel with the file when someone downloads it. The ID3v2 chapter frame addendum was published in December 2005, and tools like Forecast and Auphonic write them. The risk: some hosts re-encode your file on upload and can strip the tags. James Cridland notes ID3 tags are wiped by the technology some hosts use, "not least, Acast," so they don't always survive the trip.
2. Podlove Simple Chapters (PSC). An XML format embedded in the RSS feed, inside the episode's , using the namespace http://podlove.org/simple-chapters. Podlove's format predates the Podcasting 2.0 namespace. Its claim to relevance today is one big supporter: Spotify reads PSC.
3. Podcasting 2.0 JSON chapters ("cloud chapters"). A separate JSON file linked from the feed via . Because the data is an external file, chapters "can be edited after publishing," and they display in apps that have no access to ID3 tags, including web players. This is the format with the most momentum.
4. Show-note / episode-description timestamps. The humble list of "00:00 Intro / 12:30 Topic" you paste into the description. Not a chapter "spec" at all, just text, but some apps now parse it into tappable markers, and YouTube timestamps work the same way to auto-generate its chapter bar.

Why your chapters don't show up in some apps

Because no app reads all four formats. Apple Podcasts is the most complete: it reads embedded MP4 header chapters, ID3 chapters in MP3 or AAC, the JSON file, and timestamps in the episode description. Listeners reveal them by tapping the play-progress bar on iOS and iPadOS, or the Playing Next button on macOS. Apple also shows per-chapter artwork, but only when the chapters arrive through your hosting provider, per Apple's own documentation.

Spotify is the odd one. It went with Podlove Simple Chapters, the older XML format, plus show-note timestamps. So a JSON-only chapter file that looks perfect in a Podcasting 2.0 app can be invisible on Spotify. Apps like Podverse, Fountain, and Castamatic display the Podcasting 2.0 JSON chapters, while web players generally can't read ID3 at all. This is the whole reason RSS.com recommends supplying chapters in more than one format rather than betting on one.

One more honest caveat worth knowing: even a "supported" format can be ignored. The ID3 specification explicitly lets a parser skip frames it doesn't understand, so an app can encounter your chapter frames and silently drop them. Standards describe what's possible; each app decides what it honors.

How podcast chapters relate to the rest of your feed

Chapters are one more layer of metadata sitting on top of the parts of your feed you've already met. Whether a chapter format even reaches an app depends on the RSS feed carrying it correctly, and the JSON and Podlove versions live right inside that feed alongside the enclosure tag that points to the audio file the chapters describe.

Embedded chapters specifically are cousins of ID3 tags, both are written inside the MP3 or AAC, which is exactly why they can vanish if a host re-encodes the file. And like the episode's GUID, chapter data is something you set per episode and want carried cleanly across every app, not something to leave to chance.

A simple chapter strategy for max coverage

You don't have to choose one format and lose the others. The pragmatic move, given the support split, is to layer:

1. Add Podcasting 2.0 JSON chapters if your host supports them, they're editable after publishing and reach the widest set of modern apps and web players.
2. Add Podlove Simple Chapters through your host so Spotify shows them. Many hosting dashboards now emit both formats from the same input.
3. Always include timestamps in your show notes. It's the universal fallback, it works in Apple and Spotify, drives YouTube's chapter bar, and costs nothing.
4. Skip hand-editing ID3 frames unless you have a specific reason; they're the format most likely to be stripped, and your host is the better place to manage chapters anyway.

If your host only offers one of these, that's fine, pick the JSON path and keep the show-note timestamps as your safety net.

Frequently asked questions

Do podcast chapters help with discovery or SEO? Indirectly. Chapters don't rank you in a podcast directory, but on YouTube the timestamps generate a visible chapter bar that can improve watch-through, and clear segment titles make an episode easier to skim. The bigger discovery lever for most shows is short clips of the best moments, not chapters themselves.

Are chapters the same as timestamps? Timestamps are the simplest kind of chapter, plain text like "12:30 Topic" in the description. True chapters (embedded, Podlove, or JSON) are structured data that can also carry images and links, and they render as a dedicated navigation menu rather than clickable lines in the notes. Timestamps are the lowest-effort, most universally supported option.

Why do my chapters show in Apple but not Spotify? Almost always a format mismatch. Apple reads embedded, JSON, and timestamp chapters; Spotify reads Podlove Simple Chapters and timestamps. If you only published JSON or embedded chapters, Spotify has nothing to read except your show-note timestamps. Add PSC through your host, or rely on timestamps for Spotify.

Can I edit chapters after publishing an episode? Only with the JSON format. Podcasting 2.0 cloud chapters live in a separate file that apps fetch on playback, so you can fix a title or add a marker after release. Embedded chapters are baked into the file and would require re-uploading the audio to change.

Do chapters change the audio file? No. Chapters are metadata, markers, titles, and optional images laid over the timeline. The episode plays identically with or without them. Embedded chapters add a small amount to the file size; in-feed and JSON chapters add nothing to the audio at all.