How to Merge Multiple PDFs Into One Ebook With Chapters and a Table of Contents

Prepare Your Chapter PDFs Before You Merge

A few minutes of preparation before you merge prevents page-size mismatches, font errors, and bloated output files that are painful to fix after the fact.

Standardize page size. Chapters exported from different applications often use different sizes: A4 (210 x 297 mm) from LibreOffice, US Letter (216 x 279 mm) from Microsoft Word. A single ebook should use one consistent size throughout. Re-export every chapter from the same application, or run mismatched files through a PDF printer to normalize dimensions before merging.

Verify font embedding. Open each chapter's document properties and check that all fonts are listed as embedded. Non-embedded fonts render as system substitutes on the reader's device, which breaks your typography entirely. Modern Office exports embed fonts by default; legacy conversions sometimes skip this step. Re-export from the source with embedding forced on if you spot any unembedded entries.

Control file size before merging. iSharePDF accepts input files up to 100 MB per file and 100 MB across all inputs in a single merge operation. Photo-heavy chapters with full-resolution illustrations regularly exceed this. Run oversized chapters through the PDF compressor first. A 90 MB chapter with scanned artwork typically compresses to under 20 MB in 8 to 12 seconds, with no visible degradation at screen resolution. Reducing sizes early also speeds up the merge step significantly.

Name files in order. Rename each chapter as 00-cover.pdf, 01-intro.pdf, 02-chapter-one.pdf, and so on. When you drag the folder into the merge tool, alphabetical sorting matches your intended sequence automatically, so you spend zero time reordering manually.

Step-by-Step: Merge Your PDFs Into One Ebook

Once your chapters are clean and consistently sized, the actual merge takes under a minute. Open the PDF merge tool on iSharePDF. No account is required and nothing installs on your device.

1. Add your files. Click "Add files" or drag your chapter PDFs directly onto the drop zone. You can add up to 20 files in a single operation, with a combined size ceiling of 100 MB across all inputs.
2. Set the order. The merge tool displays a visual thumbnail preview of each file. If your naming convention was not strictly alphabetical, drag thumbnails into the correct sequence here. You can also expand each file to reorder individual pages, which is useful when a chapter title page ended up at the back during export.
3. Configure merge options. By default, the tool merges files sequentially without inserting any extra pages. If you want each chapter to begin on a right-hand (odd-numbered) page, as is standard in print layout, enable the "Start each document on a new odd page" option. The tool inserts a blank page where necessary, matching professional typesetting conventions.
4. Merge and download. Click "Merge PDF". Processing runs locally in your browser using WebAssembly. A 10-chapter ebook at 45 MB total typically merges in 3 to 7 seconds on a modern laptop. The output file downloads automatically with no watermark, even on the free tier.

The output is a valid PDF 1.7 document. All source-level metadata is merged cleanly into a single document outline, ready for the next step: adding a table of contents.

Adding a Table of Contents to Your Merged Ebook

A merged PDF without a table of contents forces readers to scroll the entire document to navigate between chapters. Adding a functional TOC transforms a flat file into a navigable ebook that readers can actually use.

Two types of TOC: visual page vs. PDF bookmarks. A visual TOC page is a formatted page at the front of your document listing chapter titles and page numbers. PDF bookmarks (also called the document outline) are clickable entries visible in the navigation sidebar of any PDF viewer. For a professional ebook you want both.

Creating the visual TOC page. Before merging, count the pages in each chapter PDF. If your cover is 1 page, introduction is 4 pages, and chapter one is 22 pages, then chapter two starts on page 28. Build your TOC page in your word processor with this count, export it as a PDF, and merge it as file number two, right after the cover, using the merge tool.

Adding PDF bookmarks. After merging, open the output file in the annotation tool. Navigate to each chapter heading, select "Add bookmark", and name it with the chapter title. These bookmarks populate the PDF outline panel and give readers one-click access to any chapter, whether they open the file in Adobe Acrobat, Apple Books, or a browser PDF viewer.

For academic ebooks or technical documentation, also consider creating a list of figures and a list of tables as separate PDF pages, merged after the TOC but before the first chapter. Insert them during the merge step so page numbers remain accurate throughout.

Compress, Protect and Finalize Your Ebook

Your merged ebook is a single file. Before distributing it, two optional but highly recommended steps will make it significantly more professional: compression and copy protection.

Compress the output file. Merging PDFs often produces a file larger than the sum of its parts because the output carries all embedded resources from every source file, including duplicate font tables and redundant metadata. A 10-chapter ebook might weigh 55 MB uncompressed. Run it through the PDF compressor. The "Ebook" preset targets 150 DPI, optimal for screen reading on tablets and e-readers. That same 55 MB file typically shrinks to 8 to 14 MB, a reduction of 75 to 85 percent, in 12 to 20 seconds. For print-on-demand, select the "High quality" preset instead, which preserves original resolution.

Apply password protection and permissions. If you are selling or distributing a premium ebook, protect it using the PDF protection tool. iSharePDF applies AES-256 encryption, the same standard used in financial data systems. Set an owner password to control permissions: you can allow reading while blocking printing, text copying, or document modification. An optional user password requires readers to enter a code before opening the file. All encryption runs locally in your browser. The key is never transmitted to any server.

Add a signature if needed. If your ebook is a proposal, a consulting report, or a contract addendum, add a signature block with the PDF sign tool before applying protection. Place your signature on the final page, then lock the document so the signature cannot be replaced or removed after delivery.

With compression and protection applied, your ebook is ready to distribute by email, Gumroad, Payhip, or any file host.

Why Local Processing Matters for Ebook Privacy?

Most online PDF tools upload your files to a remote server, process them there, and (depending on their terms of service) may log or retain a copy. For a novel manuscript, a confidential business report, or an ebook containing proprietary research, that upload represents a real exposure vector.

iSharePDF takes a fundamentally different approach. Every tool, including merge, compress, annotate, and protect, runs entirely inside your browser using WebAssembly compiled from a PDF processing library. Your chapter PDFs never leave your device. There is no server to breach, no cloud bucket to misconfigure, and no third party that can log, analyze, or index your content.

This architecture matters most in three scenarios:

• Unpublished manuscripts. You cannot recover from a leak of content you have not yet published. Local processing eliminates the upload vector entirely, so there is nothing to intercept in transit and nothing stored remotely after the session ends.
• Client-facing deliverables. Consultants, lawyers, and agencies who merge confidential reports into a single ebook are often bound by NDAs or data-processing agreements that explicitly prohibit uploading client data to third-party cloud services. A browser-local tool is compliant by design.
• Sensitive research and medical data. Files subject to GDPR or HIPAA cannot be sent to servers in unknown jurisdictions. Since iSharePDF never transmits your data, there is no cross-border transfer to report or justify.

If you are currently using an upload-based alternative, the iSharePDF comparison with iLovePDF explains the specific architectural differences in detail. Local WebAssembly processing in 2026 matches server-side speeds for all files under 100 MB. Visit the iSharePDF home page to see all 28 tools built on this local-first model.

Troubleshooting Common PDF Merge Problems

Even with careful preparation, merges occasionally produce unexpected results. Here are the most common issues and their fixes.

Pages appear in the wrong order. Files named "Chapter 1", "Chapter 2", "Chapter 10" sort as 1, 10, 2 in most file systems because sorting is alphabetical, not numerical. Rename with zero-padded numbers: "01", "02", "10". Alternatively, use the drag-to-reorder panel in the merge tool to correct the sequence manually before clicking Merge.

Unexpected blank pages inserted between chapters. If you enabled "Start on odd page", the tool inserts blank pages to push each chapter to a right-hand page. This is intentional for print-ready ebooks. If you are producing a digital-only ebook, disable the option to remove those blank inserts.

Combined file size exceeds the 100 MB input limit. Compress individual chapters first using the PDF compressor, then merge the compressed versions. You can also use the PDF splitter to break an oversized single chapter into logical subsections before re-merging the parts in sequence. A 120 MB illustrated chapter typically compresses to 25 to 35 MB in under 15 seconds.

Fonts render inconsistently across chapters. One chapter embeds fonts; another does not. Open the problem chapter in its source application, enable "Embed all fonts" in the PDF export dialog, re-export, and replace the file before re-merging. This resolves font-substitution rendering on all reader devices.

TOC page numbers are off by one or two. This is almost always caused by not accounting for a blank back-of-cover page, or by the "Start on odd page" option inserting an extra page you did not count. Recount pages after merging and regenerate your TOC page with the corrected numbers, then swap it into position using the merge tool.

Frequently asked questions

What is the maximum number of PDF files I can merge at once?

The merge tool accepts up to 20 PDF files per operation, with a combined input ceiling of 100 MB. If your ebook has more than 20 chapters, merge the first 10 into a combined file, merge the next 10 into a second file, then merge those two together in a final pass. Each batch takes 3 to 10 seconds depending on file size and your device.

Does merging PDFs reduce image or text quality?

No. The merge operation joins source files as-is without altering image resolution, color profiles, or font rendering. Quality only changes if you run the output through the compression tool and select a lower DPI preset. The "Ebook" preset targets 150 DPI, ideal for screen reading. Choose "High quality" to preserve original resolution for print-ready output.

How do I add a clickable table of contents to my merged PDF?

Create a visual TOC page in your word processor, listing chapter titles with accurate starting page numbers, then merge it as the second file after your cover. After merging, open the output in the iSharePDF annotation tool and add PDF bookmarks to each chapter heading. These bookmarks appear in the navigation panel of every major PDF viewer, giving readers direct one-click access to any chapter.

Is AES-256 encryption available without a paid plan?

Yes. The PDF protection tool with AES-256 encryption is free for all users with no account required. You can set an owner password to restrict permissions (printing, copying text, editing) and an optional user password to lock the file on open. All encryption is computed locally in your browser. The encryption key is never transmitted to any server. Pro features add batch protection for multiple files simultaneously.

Can I merge PDFs into an ebook on a smartphone or tablet?

Yes. All iSharePDF tools run in any modern mobile browser, including Chrome and Safari on Android and iOS, with no app installation required. Select chapter files from local storage or a cloud drive through the standard file picker. Processing on mobile is slightly slower: a 45 MB, 10-chapter merge takes approximately 8 to 18 seconds on a mid-range device, compared to 3 to 7 seconds on a desktop.

What happens to my files after I close the browser tab?

Nothing, because your files never left your device. iSharePDF's tools run entirely in-browser using WebAssembly. No file data is transmitted to any server at any point during processing. When you close the tab, the browser discards the in-memory data just as it does with any local operation. There is no session to expire, no cloud copy to delete, and no support request needed to confirm removal.