How to Merge EPUB Files

Merging EPUB files combines multiple separate ebooks into a single navigable file — one table of contents, one download, one file to manage. The right method depends on whether you want no-install speed, command-line control, or maximum output quality. Here are all three.

Method 1: Epublys (Browser, No Install)

1. Open the Merge EPUB tool
2. Add up to 10 files (up to 10MB each on the free tier) by dragging or clicking to browse
3. Drag the file cards to set the reading order — the first card becomes the first section
4. Click Merge EPUBs and download

CSS stylesheets from each source are kept and namespaced to prevent conflicts. Image filenames are deduplicated automatically — if two books both have a cover.jpg, one gets renamed so neither breaks. TOC entries from each source are assembled in spine order into a unified navigation document. The merge runs in-memory on a Cloudflare Worker — your files are never written to disk and are gone the moment the response returns.

Need more than 10 files or files larger than 10MB? Pro supports up to 500 files at 100MB each.

Method 2: Calibre

Select your books in Calibre's library view, right-click, choose Merge selected records. It works when your books are already in your Calibre library and properly tagged. Worth knowing: Calibre's merge is primarily a metadata deduplication function that also concatenates content — the TOC structure preservation is less thorough than a purpose-built merge. Requires a 200MB+ install and the books to already be in your library.

Calibre is the right choice when you're already using it for library management and don't want to switch tools. See the Calibre vs Epublys breakdown for a full comparison.

Method 3: epubmerge (Command Line)

pip install epubmerge
epubmerge -o combined.epub book1.epub book2.epub book3.epub

Useful options:

• --titlepage — inserts an auto-generated separator page between books with the source title
• --keepmetadata — preserves per-book metadata in separate <item> entries instead of inheriting only from the first file
• --flattentoc — flattens the combined TOC to a single level if nested chapters cause issues in strict readers

Handles EPUB 2 and 3. Always validate the output after a programmatic merge — epubmerge doesn't deduplicate IDs, so combined files from books with overlapping ID schemes will fail epubcheck.

What the Merge Does to Your Files

Metadata

The merged file inherits title, author, language, and identifier from the first book in the order. Publisher and subject fields also come from book one. If those values are wrong for the combined work, use the metadata editor to update them without re-merging.

Table of Contents

TOC entries from each source are assembled in spine order. If a source book had a well-structured NAV document, its chapter entries are included with correct nesting. If a source had no TOC or only a flat list, those entries are included at the top level. The combined TOC reflects the quality of the source files — a book with no chapter structure contributes entries without chapter labels.

CSS and Fonts

Each source book's stylesheets are preserved and scoped to prevent class name collisions. If you see visual inconsistency between sections (different default fonts, different line spacing), it's because the source books have genuinely different stylesheets. This is expected behavior. If consistent visual presentation matters for the merged work, open the result in Sigil and unify the stylesheets manually.

Font files are deduplicated: if two books embed the same font file, only one copy ends up in the merged output. This reduces size and prevents loading conflicts.

Images

Image files from each source are included. Duplicate filenames are automatically renamed to avoid collisions — cover.jpg from book two becomes cover_1.jpg in the merged output, and all references to it are updated consistently.

What Goes Wrong

• Validation fails after merge: Almost always duplicate element IDs. Source books frequently reuse IDs like chapter-1, toc, or title, which must be unique across the entire combined file. Epublys deduplicates these automatically. epubmerge and Calibre may not — run the validator after any merge and use auto-fix for ID conflicts.
• Sections look visually inconsistent: Each book brings its own CSS. If the stylesheets produce conflicting visual results, you need to open the merged file in Sigil and consolidate them into a single unified stylesheet. This is a presentation decision, not an error.
• File size balloons: Multiple cover images, multiple embedded font sets, and multiple sets of internal CSS all add up. Run the output through the EPUB compressor after merging — covers alone often account for 30–50% of a merged file's total size.
• TOC is flat when you expected nesting: The source books had flat TOCs or no chapter structure. The merger faithfully reproduces what's there. If you need a hierarchical TOC for the combined work, it needs to be built manually in Sigil or by editing the nav.xhtml after merging.
• DRM-protected EPUBs fail immediately: The merge tool can only process DRM-free EPUBs. Encrypted files can't be parsed and will error out. This is a characteristic of the files, not a tool limitation.

Real Use Cases

Author: Bundling a series into an omnibus

Self-published authors frequently combine a completed trilogy into an omnibus EPUB for sale at a discount or as a newsletter incentive. Drop all three books in, order by publication order, merge. Then update the title and cover in the metadata editor. Validate before uploading to KDP — merged files occasionally introduce duplicate IDs that Apple Books rejects.

Librarian: Consolidating multi-part volumes

Academic works distributed in parts, or donations that arrived as separate EPUB files for each chapter, can be merged into a single archivable document. The TOC from each part preserves its chapter structure in the combined file. Run validation before archiving — the merge output is what gets stored permanently.

Researcher: Building a custom reading list

Extract specific chapters from several sources using the splitter, then merge the extracted pieces into a single navigable document. Useful for seminars, reading groups, or custom study materials where the content is from multiple DRM-free sources.

After Merging

Three follow-up steps for any merge:

1. Validate — merges reliably introduce structural errors. Run epubcheck before distributing.
2. Update the metadata — title, author, and cover need to reflect the combined work, not just book one.
3. Compress — multiple books' embedded assets add up. Compression typically cuts 30–50% from a merged file.

• Merge EPUB files for free — free tier details and limits
• Edit EPUB metadata — fix title and author after merging
• Reduce EPUB file size — compress the merged result
• Calibre vs Epublys — full comparison