One book from many
Join a series, a run of web novel volumes, or course readers into a single EPUB that opens as one title in your reading app.
Merge EPUB files into one book with a combined table of contents, directly in your browser.
or drag and drop two or more .epub books here
Join a series, a run of web novel volumes, or course readers into a single EPUB that opens as one title in your reading app.
Each book's own chapters are kept and nested under its title, or listed flat, in both the EPUB 3 nav and the EPUB 2 NCX.
A new OPF, unique identifiers, the original spine order, and a validated ZIP with the uncompressed mimetype entry first.
Your original books stay unchanged; the merged EPUB is a new file.
Choose or drop two or more DRM-free .epub books, or try the sample files.
Drag books or use the arrows. Check the title, author and chapter count of each book.
Name the collection, pick the cover and choose a grouped or flat table of contents.
Get one validated EPUB file. The original books are not changed.
No. Your browser opens each EPUB, copies its chapters and assets into the new package, and builds the download locally. There is no upload, no account, and nothing is stored after you close the page.
Yes. Every book keeps its own folder of chapters, CSS, images and fonts, so internal links still resolve. The new table of contents is rebuilt from each book's navigation, falling back to chapter headings when a book has none.
An EPUB looks like a single file, but it is a ZIP package with a fixed structure. It starts with a small mimetype file, followed by META-INF/container.xml, which points to the package document (the OPF file). The OPF file is the heart of the book: it holds the metadata, lists every file in the package, and defines the reading order. The chapters themselves are separate XHTML files, styled by CSS and accompanied by images and fonts. The full rules are in the W3C EPUB 3.3 specification.
Because of that structure, you cannot merge two EPUB files by gluing them together the way you might join two text files. Merging means building a new package that contains the content of every source book and a single set of instructions that describes all of it. This is what the EPUB Merger does in your browser.
Every file from each source book is copied into its own folder, such as OEBPS/book-01/ and OEBPS/book-02/. Inside that folder the book keeps its original layout, so a chapter that loads ../Styles/book.css or shows ../Images/map.jpg still finds those files. The tool then writes a new OPF manifest that lists every copied file. Each manifest id gets a book prefix because two books often use the same ids, such as chapter1 or cover, and duplicate ids would make the package invalid.
The source books' own OPF files, container files and mimetype entries are not copied as content. The merged book gets fresh metadata instead: a new urn:uuid identifier, the title, author and language you choose, a modification date, and the cover image you select.
The spine is the ordered list of chapters a reading system pages through. The merged spine is each book's spine in turn, in the order of your file list. Items marked linear="no", such as footnote pages or a cover page that the publisher keeps out of the main flow, keep that flag, so they do not suddenly appear in the middle of the text.
EPUB 3 books have a navigation document (nav.xhtml) and EPUB 2 books have an NCX file (toc.ncx). The merger reads whichever one each book has, rewrites its links to the new folder, and builds a combined table of contents. With the grouped style, each book becomes one entry with its own chapters nested underneath, which keeps a 20-book collection easy to browse. The merged EPUB contains both a nav.xhtml and a toc.ncx, so newer and older reading apps show the same contents. If a book has no table of contents at all, its chapters are listed from the spine using each chapter's first heading.
There are trade-offs. Reading progress, highlights and notes are tied to a specific file, so they do not carry over from the separate books. A merged book is also larger, which matters on older e-readers with little memory. If you only want to read books one after another, a reading app with collections may be enough.
The best-known way to merge EPUB files on a computer is the EpubMerge plugin for Calibre, written by the author of FanFicFare. You install Calibre, add the plugin from Preferences, import the books into your library, select them, and run EpubMerge. It is a mature tool with many options, and if you already manage your ebooks in Calibre it fits naturally into that workflow. A companion plugin by the same author, EpubSplit, can split a merged book back into its parts.
This EPUB Merger is for the cases where installing software is not practical: a Chromebook, a work laptop, a borrowed computer, or a one-off job where a full library manager is more than you need. It runs in the browser, keeps the books on your device, and produces an EPUB 3 file with an EPUB 2 NCX for compatibility. It does not add the books to a library or manage metadata for you, and it cannot split books apart again.
Before the download is offered, the tool opens the new EPUB again and checks that the mimetype entry is first and uncompressed, that container.xml points to the OPF file, and that every file listed in the manifest exists. For a full conformance report, run the file through EPUBCheck, the official validator. Warnings from EPUBCheck often come from the original books, so run it on a source book too if something looks unfamiliar.
The quickest practical test is to open the book in a real reader. You can read EPUB online without installing anything, or use a desktop or mobile app. Our comparisons of the best EPUB readers for Windows, Mac, Android and iPhone and iPad list apps that handle long, multi-book EPUBs well.
Books bought from many stores are encrypted with Adobe, Apple, Kobo or similar DRM. Their chapters cannot be read outside the licensed app, so they cannot be merged. Only DRM-free books work, such as books from DRM-free stores, public domain sites, your own manuscripts, or files produced by web novel downloaders. The other books in the list are not affected when one is rejected.
The book order follows the numbered list. Within a book, chapters follow that book's own spine. If a source book has its chapters in the wrong order, fix that book first, then merge again. File names such as volume-10.epub and volume-2.epub may sort unexpectedly when you add them together, so check the numbers before merging.
When a book has no usable navigation, chapter names come from the first heading in each chapter, or a numbered label when there is no heading. To change chapter text or headings across a book, edit it with EPUB Find and Replace and then merge the corrected file.
Each book keeps its own CSS, so a collection of books from different publishers will look slightly different from section to section. That is expected and keeps every book looking as its publisher intended. Most reading apps let you override the font and size for the whole book.
Image-heavy books add up quickly. Send to Kindle accepts larger files through its app and website than by email, so use those for big collections. If an older e-reader struggles, merge fewer books per file, for example one omnibus per trilogy instead of a whole series.
Everything happens in browser memory, so very large merges are best done on a desktop with other heavy tabs closed. The tool processes files in small steps to keep the page responsive and shows progress for each book.
Browse the EPUB tools and guides hub for more ebook resources, including the best EPUB readers for Ubuntu and Chromebook. If your book started as separate drafts, you can combine the source files first with Merge Word Files, the Markdown Merger, the HTML Merger or the TXT Merger.
Read the merged book online, fix text across chapters, or explore more EPUB tools.