Skip to main content

Audio Chapter Editor — Free Podcast Chapter Marker Tool

Add, edit and remove podcast chapter markers in any audio file. Outputs an industry-standard ID3v2 chapter frame compatible with Apple Podcasts, Pocket Casts, Overcast and every modern podcast app.

Tap to select a file

Supports MP3, M4A, up to 200MB

Runs entirely in your browser

What to do next

Related tools

About Audio Chapter Editor

Audio Chapter Editor is part of a collection of single-purpose audio editing and conversion tools. Add, edit and remove podcast chapter markers in any audio file. Outputs an industry-standard ID3v2 chapter frame compatible with Apple Podcasts, Pocket Casts, Overcast and every modern podcast app. Each tool is intentionally narrow — it does one thing well rather than offering many overlapping features — which makes the common path predictable and the result easy to verify before you download or copy it.

Audio Chapter Editor is shaped around the recurring needs of two audiences: podcasters preparing episodes, who use it as a quick utility between bigger tools, and sound designers prototyping cues, who use it as their primary way of getting the job done. Both groups get the same defaults and the same speed.

Audio Chapter Editor is shaped for the gap between "I'll do it by hand" and "I'll script it." When the job is small enough that automating it would take longer than doing it, but annoying enough to want a focused tool — that is the situation this page is built for.

The processing pipeline is straightforward: your input is parsed by the Web Audio API, transformed according to the options you select, and serialised back into a downloadable result. Accepted input formats are MP3 and M4A. The 200 MB per-file ceiling matches what a typical browser tab can handle without paging to disk.

Because everything runs in the page, the tool scales the same way for one user or a million — there is no per-user backend cost. The page is static, the engine is the same JavaScript bundle for every visitor, and the work happens on the visitor's own device. That keeps the tool free and keeps it fast on the first interaction.

Audio Chapter Editor sits in a small group of related tools. Useful neighbours include Audio Trimmer, Audio Merger, Audio Converter, and AI Audio Transcriber. They are designed to compose: the output of one is a sensible input to the next, so a multi-step task is usually a sequence of single-click operations.

The architecture imposes only the limits the browser itself imposes. The published 200 MB ceiling is conservative; most modern devices comfortably handle inputs up to that size, and the cap exists so the tool degrades gracefully on phones and budget laptops rather than running out of memory.

The transformation in Audio Chapter Editor is deterministic — the same input plus the same options produces the same result every run. That predictability matters when the result has to match an upstream specification or be reproducible later.

Output handling is intentionally boring: Audio Chapter Editor produces `{name}-chapters.mp3` and triggers your browser's standard "save" behaviour. If you have a default download folder configured, that is where it will land. There is no Favtoo-side history of jobs you have run.

From a product perspective, Audio Chapter Editor is one of the simplest possible expressions of "do one thing well." The catalog contains dozens of related tools that each handle a slightly different audio editing and conversion task, and every one is a separate page rather than a tab inside a larger app. That separation keeps each tool fast to load and easy to bookmark.

Audio Chapter Editor is built around the moment of need: a focused page you open when you have a specific task, complete the task, and close. The catalog contains many adjacent tools so the same model serves the surrounding parts of a typical audio editing and conversion workflow.

If you want to get the most out of Audio Chapter Editor, three small habits help. Drag-and-drop is faster than the file picker once you get used to it. The keyboard shortcut for downloading the result is whatever your browser uses for "save link as," because the result is a normal download. And if you are working on a sensitive file, processing in an Incognito or Private window is a good extra layer — it leaves no trace in browser history when the tab closes.

Common gotchas worth flagging: Audio Chapter Editor only accepts MP3 and M4A, so if your file is in another format you will need to convert it first. The 200 MB ceiling is per-file, not per-session; you can run as many separate jobs as you like, but a single oversized input will be rejected on load.

That is essentially everything Audio Chapter Editor does and how it does it. Open the tool above, drop in your input, and the work happens in the page. If you find yourself reaching for it often, bookmark the page — it loads quickly on subsequent visits, and your most-recent settings are remembered for the rest of the session.

How it works

  1. 1Land on the Audio Chapter Editor page. The tool is ready to use the moment the page renders.
  2. 2Add your MP3 and M4A input by dropping it onto the page or browsing for it.
  3. 3Pick any non-default settings you need. Most users leave the defaults alone for the first run and only revisit if the result needs tuning.
  4. 4Trigger processing. the Web Audio API reads your input, applies the transformation, and writes the result back into the page.
  5. 5Grab the output named `{name}-chapters.mp3` as soon as the run completes. You can also copy the result instead of downloading if the next tool in your workflow accepts pasted input.
  6. 6Repeat the process for additional inputs whenever you need to. The page stays loaded, so subsequent runs are quick.

Common use cases

  • Generate a short audio cue for a video transition using Audio Chapter Editor.
  • Split a long mixtape into individual track files.
  • Record a quick test tone to verify a microphone setup.
  • Convert a band's rough mix into a format mastering software accepts.
  • Trim the cough out of the first ten seconds of a podcast take.
  • Compress a music demo small enough to share over messaging.
  • Boost a quiet interview recording to a normal listening level.
  • Stitch several voice notes into a single playable file.
  • Extract the audio from a video so it can be edited separately.
  • Normalise loudness across an episode so listeners do not reach for the volume.

FAQ

Which format is used?

ID3v2.3 / v2.4 chapter frames (CHAP + CTOC) — the standard supported by Apple Podcasts, Overcast, Pocket Casts, Castro, Spotify and every podcast catcher built on the standard ID3 stack.

Can I import chapters from a CSV?

Yes — paste chapter rows in "hh:mm:ss, title" format and they get inserted in order. You can also export the existing chapters as CSV for editing in a spreadsheet.

Does it re-encode the audio?

No. The MP3 frames stay byte-identical; only the ID3 tag block changes. The output sounds exactly like the input — no quality loss, no second-pass codec artifacts.

Does it work on M4A files?

Yes — chapters are written into the standard MP4 chunked-text track that Apple Podcasts reads natively from M4A files.

Will my audio upload?

No. The ID3 tag rewriter and the chunked-text track encoder both run on the WebAudio API in your browser tab.

How fast is Audio Chapter Editor?

Most jobs finish in seconds. Speed scales with input size and with how many CPU cycles your browser tab has available — the engine runs in your browser, so it shares resources with whatever else you have open. For inputs near the 200 MB ceiling, expect anywhere from a few seconds to roughly a minute on a typical laptop. Closing other heavy tabs noticeably speeds things up.

How do I know I am using the latest version of Audio Chapter Editor?

Audio Chapter Editor is updated whenever the underlying engine releases an improvement or a bug fix. Because the tool is delivered as a static page, every visit fetches the latest version automatically — there is no "version" to manage on your end. If a particular release ever changes default behaviour, the change is documented on Favtoo's changelog so you can confirm what shifted.

Does Audio Chapter Editor ask for any browser permissions?

Audio Chapter Editor only needs the standard web platform — file picker access for the inputs you choose to load, and optionally clipboard access if you copy the result rather than downloading it. There is no microphone, camera, geolocation or background-permission request, because none of those are needed for the work the tool does.

Can I use Audio Chapter Editor with formats other than the defaults?

Audio Chapter Editor accepts MP3 and M4A. If your input is in a format that is not directly supported, convert it first using one of Favtoo's converter tools — every Favtoo converter outputs a file that is a clean input to the next tool in the chain.

Is Audio Chapter Editor keyboard accessible?

Audio Chapter Editor uses native HTML controls wherever possible, which means keyboard navigation, focus rings, and screen-reader labels work the way the platform expects. The drop zone accepts files via the keyboard-accessible file picker as well as drag-and-drop, and result downloads use standard browser download flows. If you spot an accessibility gap, Favtoo treats it as a bug worth fixing.

Can I use Audio Chapter Editor on iOS or Android?

Audio Chapter Editor runs in any modern mobile browser — Safari, Chrome, Firefox and the in-app browsers in most messaging apps all support the underlying APIs. Performance depends on the device: a recent phone handles typical inputs nearly as fast as a laptop, while older devices may take a few seconds longer near the 200 MB ceiling. The interface lays out cleanly on small screens, so you do not need to pinch-zoom to see the controls.

Do I need a specific browser to use Audio Chapter Editor?

Audio Chapter Editor works in any modern browser released in the last few years — Chrome, Edge, Firefox, Safari, Brave, Arc and the major Chromium derivatives are all supported. The underlying engine relies on widely-supported web APIs, so there is nothing exotic to install. If you are on a very old browser version and the tool fails to load, updating to the latest release of your preferred browser is the only fix needed.

Does Audio Chapter Editor have an API?

Audio Chapter Editor is a browser-only tool by design and does not expose a hosted API. The reason is the same as the privacy story: there is no Favtoo backend doing the work, so there is no service to call. If you need to script the same transformation, the underlying engine (the Web Audio API) is open-source and can be used directly from your own code.

Can Audio Chapter Editor run inside a corporate firewall?

Audio Chapter Editor is a static page running an open-source engine in your browser, so a typical corporate firewall does not get in the way as long as it allows JavaScript to load from Favtoo. For teams that need to host it themselves on an internal network, the underlying engine (the Web Audio API) is open-source and can be packaged into a private build with the same behaviour. Reach out via the Contact page if that is something you are exploring.

About Audio Chapter Editor

Audio Chapter Editor is part of a collection of single-purpose audio editing and conversion tools. Add, edit and remove podcast chapter markers in any audio file. Outputs an industry-standard ID3v2 chapter frame compatible with Apple Podcasts, Pocket Casts, Overcast and every modern podcast app. Each tool is intentionally narrow — it does one thing well rather than offering many overlapping features — which makes the common path predictable and the result easy to verify before you download or copy it.

Audio Chapter Editor is shaped around the recurring needs of two audiences: podcasters preparing episodes, who use it as a quick utility between bigger tools, and sound designers prototyping cues, who use it as their primary way of getting the job done. Both groups get the same defaults and the same speed.

Audio Chapter Editor is shaped for the gap between "I'll do it by hand" and "I'll script it." When the job is small enough that automating it would take longer than doing it, but annoying enough to want a focused tool — that is the situation this page is built for.

The processing pipeline is straightforward: your input is parsed by the Web Audio API, transformed according to the options you select, and serialised back into a downloadable result. Accepted input formats are MP3 and M4A. The 200 MB per-file ceiling matches what a typical browser tab can handle without paging to disk.

Because everything runs in the page, the tool scales the same way for one user or a million — there is no per-user backend cost. The page is static, the engine is the same JavaScript bundle for every visitor, and the work happens on the visitor's own device. That keeps the tool free and keeps it fast on the first interaction.

Audio Chapter Editor sits in a small group of related tools. Useful neighbours include Audio Trimmer, Audio Merger, Audio Converter, and AI Audio Transcriber. They are designed to compose: the output of one is a sensible input to the next, so a multi-step task is usually a sequence of single-click operations.

The architecture imposes only the limits the browser itself imposes. The published 200 MB ceiling is conservative; most modern devices comfortably handle inputs up to that size, and the cap exists so the tool degrades gracefully on phones and budget laptops rather than running out of memory.

The transformation in Audio Chapter Editor is deterministic — the same input plus the same options produces the same result every run. That predictability matters when the result has to match an upstream specification or be reproducible later.

Output handling is intentionally boring: Audio Chapter Editor produces `{name}-chapters.mp3` and triggers your browser's standard "save" behaviour. If you have a default download folder configured, that is where it will land. There is no Favtoo-side history of jobs you have run.

From a product perspective, Audio Chapter Editor is one of the simplest possible expressions of "do one thing well." The catalog contains dozens of related tools that each handle a slightly different audio editing and conversion task, and every one is a separate page rather than a tab inside a larger app. That separation keeps each tool fast to load and easy to bookmark.

Audio Chapter Editor is built around the moment of need: a focused page you open when you have a specific task, complete the task, and close. The catalog contains many adjacent tools so the same model serves the surrounding parts of a typical audio editing and conversion workflow.

If you want to get the most out of Audio Chapter Editor, three small habits help. Drag-and-drop is faster than the file picker once you get used to it. The keyboard shortcut for downloading the result is whatever your browser uses for "save link as," because the result is a normal download. And if you are working on a sensitive file, processing in an Incognito or Private window is a good extra layer — it leaves no trace in browser history when the tab closes.

Common gotchas worth flagging: Audio Chapter Editor only accepts MP3 and M4A, so if your file is in another format you will need to convert it first. The 200 MB ceiling is per-file, not per-session; you can run as many separate jobs as you like, but a single oversized input will be rejected on load.

That is essentially everything Audio Chapter Editor does and how it does it. Open the tool above, drop in your input, and the work happens in the page. If you find yourself reaching for it often, bookmark the page — it loads quickly on subsequent visits, and your most-recent settings are remembered for the rest of the session.

How it works

  1. 1Land on the Audio Chapter Editor page. The tool is ready to use the moment the page renders.
  2. 2Add your MP3 and M4A input by dropping it onto the page or browsing for it.
  3. 3Pick any non-default settings you need. Most users leave the defaults alone for the first run and only revisit if the result needs tuning.
  4. 4Trigger processing. the Web Audio API reads your input, applies the transformation, and writes the result back into the page.
  5. 5Grab the output named `{name}-chapters.mp3` as soon as the run completes. You can also copy the result instead of downloading if the next tool in your workflow accepts pasted input.
  6. 6Repeat the process for additional inputs whenever you need to. The page stays loaded, so subsequent runs are quick.

Common use cases

FAQ

Which format is used?

ID3v2.3 / v2.4 chapter frames (CHAP + CTOC) — the standard supported by Apple Podcasts, Overcast, Pocket Casts, Castro, Spotify and every podcast catcher built on the standard ID3 stack.

Can I import chapters from a CSV?

Yes — paste chapter rows in "hh:mm:ss, title" format and they get inserted in order. You can also export the existing chapters as CSV for editing in a spreadsheet.

Does it re-encode the audio?

No. The MP3 frames stay byte-identical; only the ID3 tag block changes. The output sounds exactly like the input — no quality loss, no second-pass codec artifacts.

Does it work on M4A files?

Yes — chapters are written into the standard MP4 chunked-text track that Apple Podcasts reads natively from M4A files.

Will my audio upload?

No. The ID3 tag rewriter and the chunked-text track encoder both run on the WebAudio API in your browser tab.

How fast is Audio Chapter Editor?

Most jobs finish in seconds. Speed scales with input size and with how many CPU cycles your browser tab has available — the engine runs in your browser, so it shares resources with whatever else you have open. For inputs near the 200 MB ceiling, expect anywhere from a few seconds to roughly a minute on a typical laptop. Closing other heavy tabs noticeably speeds things up.

How do I know I am using the latest version of Audio Chapter Editor?

Audio Chapter Editor is updated whenever the underlying engine releases an improvement or a bug fix. Because the tool is delivered as a static page, every visit fetches the latest version automatically — there is no "version" to manage on your end. If a particular release ever changes default behaviour, the change is documented on Favtoo's changelog so you can confirm what shifted.

Does Audio Chapter Editor ask for any browser permissions?

Audio Chapter Editor only needs the standard web platform — file picker access for the inputs you choose to load, and optionally clipboard access if you copy the result rather than downloading it. There is no microphone, camera, geolocation or background-permission request, because none of those are needed for the work the tool does.

Can I use Audio Chapter Editor with formats other than the defaults?

Audio Chapter Editor accepts MP3 and M4A. If your input is in a format that is not directly supported, convert it first using one of Favtoo's converter tools — every Favtoo converter outputs a file that is a clean input to the next tool in the chain.

Is Audio Chapter Editor keyboard accessible?

Audio Chapter Editor uses native HTML controls wherever possible, which means keyboard navigation, focus rings, and screen-reader labels work the way the platform expects. The drop zone accepts files via the keyboard-accessible file picker as well as drag-and-drop, and result downloads use standard browser download flows. If you spot an accessibility gap, Favtoo treats it as a bug worth fixing.

Can I use Audio Chapter Editor on iOS or Android?

Audio Chapter Editor runs in any modern mobile browser — Safari, Chrome, Firefox and the in-app browsers in most messaging apps all support the underlying APIs. Performance depends on the device: a recent phone handles typical inputs nearly as fast as a laptop, while older devices may take a few seconds longer near the 200 MB ceiling. The interface lays out cleanly on small screens, so you do not need to pinch-zoom to see the controls.

Do I need a specific browser to use Audio Chapter Editor?

Audio Chapter Editor works in any modern browser released in the last few years — Chrome, Edge, Firefox, Safari, Brave, Arc and the major Chromium derivatives are all supported. The underlying engine relies on widely-supported web APIs, so there is nothing exotic to install. If you are on a very old browser version and the tool fails to load, updating to the latest release of your preferred browser is the only fix needed.

Does Audio Chapter Editor have an API?

Audio Chapter Editor is a browser-only tool by design and does not expose a hosted API. The reason is the same as the privacy story: there is no Favtoo backend doing the work, so there is no service to call. If you need to script the same transformation, the underlying engine (the Web Audio API) is open-source and can be used directly from your own code.

Can Audio Chapter Editor run inside a corporate firewall?

Audio Chapter Editor is a static page running an open-source engine in your browser, so a typical corporate firewall does not get in the way as long as it allows JavaScript to load from Favtoo. For teams that need to host it themselves on an internal network, the underlying engine (the Web Audio API) is open-source and can be packaged into a private build with the same behaviour. Reach out via the Contact page if that is something you are exploring.

Compress Audio

Shrink any audio file to a smaller size by lowering the bitrate. Pick a target quality (96, 128, 192, 256, or 320 Kbps) or output format (MP3, OGG, M4A) and the file is re-encoded right inside your browser using FFmpeg WebAssembly. Nothing is uploaded — your audio never leaves your device.

Convert Audio

Convert any audio file between MP3, WAV, OGG, FLAC, M4A, AAC, and Opus right in your browser. Pick the output format and (for lossy formats) the target bitrate. Everything runs locally with FFmpeg WebAssembly — your file is never uploaded and no account is required.

Audio Recorder

Record from your microphone directly in the browser. Pick quality (high, medium, low), toggle echo cancellation, noise suppression and auto-gain, then save to WebM/Opus or M4A/AAC. Audio is captured locally — nothing is uploaded.

Text to Speech

Type or paste text, pick a system voice, and listen instantly. Adjust speaking rate (0.5×–2×), pitch, and volume in real time. Uses your browser's built-in Web Speech API — no cloud TTS, no API keys, no costs.

Tone Generator

Generate a pure tone at any frequency from 20 Hz to 20 kHz. Pick a sine, square, triangle, or sawtooth waveform, choose duration, amplitude, and mono/stereo. Exports a 16-bit PCM WAV file at 44.1 kHz with built-in click-preventing fades.

Silence Generator

Generate a perfectly silent WAV file of any length from 1 second up to 1 hour. Pick mono or stereo, get a 16-bit PCM WAV at 44.1 kHz. Useful as padding between clips, intro silence, leader audio for video timing, or test material.

White Noise Generator

Generate white, pink, or brown noise as a 16-bit PCM WAV file. Pick noise type, duration up to 1 hour, amplitude, and mono/stereo. Useful for sleep, focus, masking distractions, audio testing, and as a backing layer for ambient music.

Metronome

A precise browser-based metronome powered by the Web Audio API. Set BPM from 30 to 300, choose a time signature, accent the first beat, and use tap-tempo to sync. Click timing is sample-accurate using lookahead scheduling — much steadier than typical JavaScript setInterval beats.

View all Audio Tools