AUD · Audio tools

Podcast Chapter Editor

Chapters

No chapters yet. Play to a point and add one at the playhead, or import a list. Drag a marker on the waveform to move it.

Shareable link

Settings are written to the URL as you change them. Nothing differs from the defaults yet.

Oxyd To cut, arrange and export the whole episode with chapters and a loudness target: Edit the episode in Oxyd

Add chapters to an MP3 without re-encoding

Load an episode, play or click to the point where a segment begins, and press Add at to drop a chapter on the playhead. Give it a title, repeat, and save. The result is the same MP3 with a longer tag in front: the audio frames are not decoded, so a 96 kbps mono episode comes out as the same 96 kbps mono episode.

Chapters already in the file are read on load and shown in the list, ready to rename or move.

Chapter times

Each row has a start time, a title, and two optional extras: a link and an image.

  • Start is editable text. 1:02:03.5, 62:03.5, and 3723.5 all mean the same moment. The list stays sorted by start time.
  • Set to playhead moves a chapter to wherever playback is, which is the way to correct a marker by ear.
  • The number at the left of a row seeks to that chapter.

End times are not typed. A chapter ends where the next begins, and the last one ends with the file. Start the first chapter at 00:00:00: players show no chapter for the time before the first marker.

ID3 chapters inside the file

An MP3 chapter is an ID3v2 CHAP frame. It holds an element id, a start and end time in milliseconds, and a few frames nested inside it: TIT2 for the title, WXXX for a link, and APIC for a picture shown while that chapter plays. One CTOC frame, flagged as top-level and ordered, lists the chapters in sequence.

The file keeps the tag version it came with, ID3v2.3 or ID3v2.4. A file with no tag gets ID3v2.3. The two differ in ways that matter here: 2.4 writes frame sizes as syncsafe integers and stores titles as UTF-8, while 2.3 uses plain 32-bit sizes and falls back to UTF-16 for any title outside Latin-1.

Chapter images are stored once per chapter inside the tag. Ten 400 KB images add 4 MB to every download of the episode, so keep them small or leave them out.

Which apps read them

App Reads ID3 chapters from the MP3
Apple Podcasts Yes
Overcast Yes
Pocket Casts Yes
Castro Yes
AntennaPod Yes
Spotify No

Spotify builds chapters from timestamps in the episode description. YouTube does the same for video descriptions, and requires the list to start at 00:00, hold at least three entries, and keep each chapter at least 10 seconds long. The Timestamp lines export writes that form.

Chapter list formats

The list imports from pasted text or a file, and exports by copy or download. The format is detected on import unless one is picked.

  • Timestamp lines: 00:01:35 Guest introduction, one per line. Import also accepts 1:35, bracketed times, and a dash between time and title.
  • Podcasting 2.0 JSON: the chapters array with startTime in seconds, title, and url. A feed points to it with a <podcast:chapters> tag, which lets apps load chapters without downloading the audio.
  • Podlove Simple Chapters: <psc:chapter start="00:01:35.000" title="…" href="…" /> elements for the RSS item.
  • Audacity labels: tab-separated start, end, and text. Mark the episode in Audacity with point labels, export the label track, and import it here.
  • CUE sheet: one TRACK per chapter with INDEX 01. CUE counts in 75ths of a second, so times round to the nearest frame.

Links travel in the JSON and Podlove forms. Embedded chapter images exist only in the MP3, because the list formats reference an image by URL instead of carrying its bytes.

Chapters lost after another edit

A tag editor that does not know CHAP and CTOC can drop them when it rewrites the tag. A host that re-tags or re-encodes uploads can do the same. Set the title, artist, and cover art first, in the tag editor or anywhere else, and add chapters as the last step before upload. If an app shows none, download the published file and load it here: chapters that survived appear in the list.

Frequently Asked Questions

It places chapter markers on an audio file and writes them into an MP3 as ID3v2 CHAP and CTOC frames. Chapters are written to MP3 only. Any other audio file (M4A, WAV, FLAC, Ogg) still loads for listening and marking, and its chapter list exports as JSON, XML, CUE, Audacity labels, or timestamp lines.

No. Only the ID3 tag at the head of the file is rebuilt. Every byte after it, which is all of the audio, is carried into the new file unchanged, so the bitrate, length, and sound are the same.

No. Spotify does not read chapters embedded in the file. It shows chapters from timestamps written in the episode description, so export the list as timestamp lines and paste it there. Apple Podcasts, Overcast, Pocket Casts, Castro, and AntennaPod read the ID3 chapters from the MP3 itself.

They stay. Title, artist, cover art, and every other frame in the tag are copied into the new tag as they were. Only earlier CHAP and CTOC frames are removed, so saving twice replaces the chapters instead of doubling them.

Not here. M4A chapters live in a QuickTime text track or a Nero chapter atom inside the MP4 structure, and this page does not write either. Build the list against the M4A and export it as Podcasting 2.0 JSON or Podlove XML for the feed, or use the timestamp lines in the show notes.

The other editor rewrote the ID3 tag and dropped the frames it did not recognise. Chapters are the last step: finish the title, artwork, and other tags first, then add chapters and upload that file.

As HH:MM:SS.mmm, MM:SS, or plain seconds. 1:02:03.5, 62:03.5, and 3723.5 are the same moment. Press Enter or leave the field and the list re-sorts by start time.

At the start of the next one, and the last chapter ends at the end of the file. ID3 stores both a start and an end for every chapter, so the ends are filled in when the file is written.

255. The ID3 table of contents counts its entries in a single byte.

Explore Our Tools

Browse all tools