Convert M4A to M4B — Free Online Tool
Convert M4A audio files to M4B audiobook format while preserving chapter markers and AAC audio encoding. Since both formats share the same MPEG-4 container and AAC codec, this conversion adds M4B's bookmarking and audiobook metadata support with minimal quality impact.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your M4A file here
or click to browse
Free — no uploads, no signups. Your files never leave your browser.
Settings
Note: Browser-based encoding uses approximate quality targets. For precise CRF compression, copy the FFmpeg command above and run it on your desktop.
Estimated output:
Conversion Complete!
DownloadHow It Works
M4A and M4B are structurally nearly identical MPEG-4 containers — the primary difference is the file extension and the metadata flags that signal audiobook-aware behavior to players like Apple Books, Podcast apps, and iTunes. During this conversion, FFmpeg re-encodes the AAC audio stream at 128k bitrate and applies the `-movflags +faststart` flag, which relocates the MOOV atom to the beginning of the file. This atom relocation is what enables M4B files to begin playback immediately and support position bookmarking without seeking through the entire file. Any chapter data present in your M4A source is carried over into the M4B output, since both containers use the same MPEG-4 chapter structure. The result is a file that audiobook players recognize natively, enabling features like resume-from-last-position that M4A files do not reliably trigger.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg tool. In the browser-based version of this tool, FFmpeg runs locally via WebAssembly (FFmpeg.wasm) — your M4A file never leaves your device. |
-i input.m4a
|
Specifies the input M4A file. FFmpeg reads the MPEG-4 container and identifies the AAC audio stream and any chapter atoms present in the source audiobook or podcast file. |
-c:a aac
|
Sets the audio codec to AAC for the M4B output. Since M4A already contains AAC audio, this re-encodes the stream in AAC — the only lossy audio codec natively supported in the M4B format for maximum compatibility with Apple Books and iOS audiobook players. |
-b:a 128k
|
Sets the AAC audio bitrate to 128 kilobits per second. For spoken word audiobooks this is a solid default balancing file size and clarity; you can lower it to 64k or 96k for smaller files or raise it to 192k or 256k if the source M4A was encoded at a higher quality. |
-movflags +faststart
|
Moves the MOOV atom to the beginning of the M4B file after encoding. This is essential for audiobook functionality — it allows players like Apple Books to begin playback immediately, save listening position for bookmarking, and stream the file from cloud libraries without reading the entire file first. |
output.m4b
|
Defines the output filename with the .m4b extension. This extension is what signals to Apple Books, iTunes, and other audiobook players that the file supports bookmarking and should appear in the Audiobooks library rather than the Music or Podcasts sections. |
Common Use Cases
- Converting a multi-chapter M4A audiobook purchased or downloaded from a non-Apple source into M4B so Apple Books can track your listening position across devices
- Packaging a podcast series exported from a DAW as a single M4A file into M4B format so listeners can resume playback mid-episode on iPhone without losing their place
- Turning a self-recorded lecture or language learning audio file into an M4B so it appears in the Audiobooks library on iOS rather than the generic Music app
- Converting an M4A chapter compilation of a public domain audiobook into M4B to make it compatible with dedicated audiobook players like Libro.fm or Bound
- Preparing a finished M4A narration file for distribution on audiobook platforms that require M4B format with fast-start streaming enabled
- Reformatting an M4A meditation or guided sleep audio session into M4B so the listener's position is bookmarked if they fall asleep mid-playback
Frequently Asked Questions
There is a small degree of quality loss because FFmpeg re-encodes the AAC audio stream rather than copying it directly. Both formats use AAC, but this conversion transcodes to 128k AAC rather than performing a lossless stream copy. If your source M4A was already encoded at 128k, the quality impact is minimal but technically present. To minimize generational loss, you can raise the bitrate in the command to `-b:a 192k` or `-b:a 256k` if your source was encoded at a higher quality.
Yes. Both M4A and M4B use the same MPEG-4 chapter atom structure, so chapter markers present in your source file are carried through to the M4B output during this conversion. Audiobook players like Apple Books and VLC will display these chapters, allowing listeners to jump between sections. If your M4A has no chapter data, the resulting M4B will also have none, but you can add chapters using tools like mp4chaps or Chapterize after conversion.
The `-movflags +faststart` flag moves the MOOV atom — the index that describes the file's structure — to the beginning of the MP4/M4B container instead of the end. Without this, a player must download or read the entire file before it can begin playback or bookmarking. For M4B audiobooks, which are often large files streamed from cloud libraries, fast-start is critical for enabling immediate playback and reliable position saving. Apple's audiobook ecosystem in particular expects this atom placement.
Apple Books and iTunes use the file extension as the primary signal to categorize audio as an audiobook. An M4A file is treated as music or a podcast, routing it to the Music or Podcasts app instead. M4B signals to Apple's ecosystem that the file is an audiobook, unlocking the Audiobooks library, persistent bookmarking, and variable playback speed controls. The audio codec inside both files is identical AAC — only the container extension and metadata flags differ.
Replace the `-b:a 128k` value in the command with your desired bitrate. For spoken word audiobooks, `64k` or `96k` is often sufficient and produces smaller files. For music or high-fidelity narration, `192k` or `256k` will better preserve quality, especially if your source M4A was encoded at a higher bitrate. The full command with a higher bitrate would look like: `ffmpeg -i input.m4a -c:a aac -b:a 192k -movflags +faststart output.m4b`.
Yes. On Linux or macOS, you can loop over files with a shell one-liner: `for f in *.m4a; do ffmpeg -i "$f" -c:a aac -b:a 128k -movflags +faststart "${f%.m4a}.m4b"; done`. On Windows Command Prompt, use: `for %f in (*.m4a) do ffmpeg -i "%f" -c:a aac -b:a 128k -movflags +faststart "%~nf.m4b"`. This is especially useful when converting a full audiobook series or podcast archive. The browser-based tool processes files individually, so the FFmpeg command is the recommended approach for batch jobs.
Technical Notes
M4A and M4B are both MPEG-4 Part 14 containers, making this one of the closest format relationships in audio conversion — they are structurally the same format with different extensions and behavioral metadata. The key technical distinction is that M4B containers are expected to carry the MOOV atom at the file head (enabled by `-movflags +faststart`) and are recognized by audiobook-capable players as bookmark-eligible media. This conversion re-encodes the audio as AAC rather than stream-copying, which introduces a generation of lossy compression. A true stream copy (`-c:a copy`) would avoid quality loss, but it skips the movflags rewrite that correctly structures the output as a fast-start M4B. iTunes metadata fields (title, artist, album) present in the M4A source are generally preserved in the M4B output through FFmpeg's default metadata passthrough behavior. M4B does not support multiple audio tracks or subtitles, matching M4A's limitations. Files with embedded cover art in the M4A source may or may not carry artwork through depending on how the source was tagged; if artwork is missing in the output, it can be re-embedded with `-map 0` added to the command. The 1GB browser processing limit makes this tool practical for most single-title audiobooks; multi-part series or very long recordings should use the desktop FFmpeg command directly.