One Audiobook, Not a Folder Full of Parts
I built ChapterForge's M4B merge tool for a very ordinary annoyance: an audiobook that should feel like one book, but arrives as Part 1, Part 2, Part 3, and so on.
You can keep those files separate. Most audiobook players will open them. But the experience is clumsy: artwork can vary, chapter numbering may restart in every part, and moving between files never feels quite like moving between chapters in one book.
The obvious fix is to merge the parts. The less obvious question is what the merge tool does to the audio while it is working.
If compatible audio can be copied into a new M4B container, decoding and encoding it again would be wasted work. It takes longer and gives a lossy codec another opportunity to change the sound. ChapterForge therefore tries to preserve the existing audio stream and concentrates on the part that really does need rebuilding: the audiobook structure around it.
The short version: on compatible M4B files, ChapterForge can join the existing audio streams without re-encoding them. It then creates one continuous chapter timeline and writes the book information you review in the merge workspace.
What “Lossless Merge” Means Here
“Lossless” can be a slippery word. In ChapterForge, it describes the merge path—not a claim that every source file contains lossless audio.
Most M4B audiobooks contain AAC audio, which is usually lossy. A lossless merge does not magically turn that AAC into lossless audio. It means the app uses stream copy when the inputs are compatible, so the compressed audio packets are moved into the new file without being decoded and compressed again.
That distinction matters:
- The audio stream is copied, not re-encoded. There is no extra generation of codec loss on the stream-copy path.
- The M4B container is rebuilt. The output still needs a valid timeline, chapters, and book-level metadata.
- The result is usually much faster than a full encode. The app is moving data and rebuilding structure instead of processing every second of narration through an encoder.
This is more accurate than saying the whole file is copied “byte for byte.” The output M4B is a new file. Its container, chapter timing, and selected metadata are deliberately rewritten even when the audio payload is preserved.
Why the Files Cannot Simply Be Glued Together
An M4B is more than a strip of audio. It is an MP4-family container with tables that describe the media, its timing, its chapters, and its metadata. If you append two complete M4B files with an ordinary file-copy command, you also append two independent sets of container instructions. Players do not automatically turn those into one coherent audiobook.
A useful mental model is moving chapters from several binders into one new binder. The pages do not need to be rewritten, but the table of contents does.
ChapterForge follows that model:
- It inspects the source files and reads their durations, stream details, chapters, metadata, and artwork.
- It places the source audio in the order you chose.
- It rebuilds the chapter timestamps as one continuous timeline.
- It writes the title, author, narrator, cover, and other output details you reviewed.
- It exports one M4B to the folder you selected.
The practical benefit is not an abstract lesson in MP4 atoms. It is opening one book in your player, seeing one chapter list, and pressing play without having to remember which “part” comes next.
The Part You Still Control
Automation helps most when it removes drudgery without hiding important decisions. Both ChapterForge apps give you a merge workspace before export, so you can check what the finished audiobook will look like.
Depending on the platform and version, that workflow includes:
- arranging the source files in playback order
- reviewing the chapters extracted from every source
- renaming individual chapters or cleaning several names with Find & Replace
- setting the finished book's title, author, narrator, and cover art
- choosing the output folder and file name
- watching progress and cancelling a merge if you spot a mistake
That review step is important. If Part 2 begins with another “Chapter 1,” preserving the source title exactly may be technically correct and still produce a confusing finished book. ChapterForge exposes the combined list so you can fix that before it reaches your library.
What Happens When the Audio Does Not Match?
Stream copy depends on compatible source streams. Codec, sample rate, channel layout, and other properties can differ between files that all happen to end in .m4b.
The Windows implementation checks those properties before using its stream-copy path. If the files are not safe to copy together—or if the copy attempt fails—it falls back to AAC LC at 128 kbps so the merge can still finish. The progress message changes to make that re-encode visible.
That safeguard is more useful than promising that every possible set of files can be merged without re-encoding. It also means you should check the status shown by the app if avoiding any additional encode is essential to your workflow.
On macOS, the current App Store version presents M4B merge as a no-re-encode workflow and lets you review the extracted chapters before exporting. As with any merge, start with healthy source files and listen to a few joins in the finished book before deleting or archiving the originals.
Keep the source files until you have opened the merged M4B, checked its artwork and book details, and listened across several chapter boundaries. A successful export is not a substitute for a quick quality check.
Metadata Is Rebuilt, Not Blindly Preserved
The old version of this article said that all metadata is preserved perfectly. That was too broad.
ChapterForge reads useful information from the sources, carries chapter structure forward, and can include cover art. But the merge output is intentionally given one coherent set of book-level fields. On Windows, for example, the merge executor writes reviewed fields such as title, album, author, narrator, genre, and year, then builds fresh chapter entries from the combined list.
That is usually what you want. Two source files may disagree about the book title, use different artwork, or contain different comments. Copying every tag without choosing which one represents the finished book would create ambiguity rather than preserve quality.
Where This Workflow Helps
A multipart download
You have a long book split into several M4Bs. Put the parts in order, confirm the chapter list, choose one cover, and export a single book.
Recording sessions from different days
An author or narrator has one M4B per session. Merge the sessions after editing their chapter names so the final release reads as one continuous production.
A lecture or podcast archive
You want a season or course to behave like an audiobook. Each episode or lecture can remain a chapter while the collection becomes one portable M4B.
A library that needs cleaner presentation
The sound is already right, but the files are fragmented. A stream-copy merge can solve the organization problem without treating the audio as if it needed remastering.
What the Merge Tool Does Not Try to Be
ChapterForge's merge workflow is deliberately focused:
- It combines existing M4B audiobook parts; Windows also accepts compatible M4A sources in its merge workspace.
- It does not repair corrupted media or guarantee that every unusual file will be stream-copy compatible.
- It rebuilds a clean output metadata set rather than promising to retain every private or vendor-specific tag.
- It does not decide the “right” chapter order for you; the order shown in the workspace is the order that will be exported.
- It does not make listening checks unnecessary.
For people who prefer scripting every FFmpeg flag, command-line tools offer deeper control. ChapterForge is for the person who wants the same kind of careful workflow in a visual desktop app: add the parts, see the chapters, fix the names, and export.
ChapterForge Is Available on Mac and Windows
The merge feature is available in both current store versions. The surrounding apps share the same goal—turning loose audio into organized M4B audiobooks—but each platform has its own interface and automation options.
ChapterForge for macOS
The Mac version combines a native interface with lossless M4B merge, chapter cleanup, batch queueing, Smart Auto-Import, and watch-folder workflows. The store offers a free mode so you can try a small merge with your own files.
Download ChapterForge on the Mac App Store →
ChapterForge for Windows
The Windows version includes a dedicated M4B/M4A merge workspace, chapter and metadata review, stream-copy compatibility checks with a visible AAC fallback, Smart Auto-Import, batch processing, and watch-folder workflows.
Get ChapterForge from the Microsoft Store →
You can also compare the Mac and Windows versions on the ChapterForge product page.
A simple first merge
- Open Merge Existing M4B in ChapterForge.
- Add two or more parts and put them in playback order.
- Review the combined chapters and clean up repeated or inconsistent titles.
- Choose the finished book's metadata, artwork, and output location.
- Start the merge, then open the result and listen across a few joins.
One finished audiobook is easier to browse, easier to move between devices, and easier to keep tidy. The audio should not have to take an unnecessary trip through an encoder just to get there.
I build ChapterForge because I wanted audiobook cleanup to feel less like operating a media laboratory. The internals still involve FFmpeg, stream compatibility, and container metadata; the person using the app should be able to focus on whether the finished book looks and sounds right.
