Merge PDF Online
Combine PDF files free in your browser with no registration.
Drop files here or click to upload
Max 100 MB
PDF merging combines multiple documents into a single file by joining their page trees. This is the most common PDF operation for consolidating contracts, invoices, scanned pages, and reports into one deliverable. Merging matters when you need a signed, single-document workflow β email attachments with 12 separate PDFs are unwieldy, and many portals only accept one upload. Combining first also makes downstream tasks (page numbering, watermarking, signing) simpler because they operate on one file instead of ten. This tool runs entirely in your browser using pdf-lib. Files are read into memory, their page trees are re-parented into a new document, and the merged result is served as a download. Nothing is sent to a server, and the operation completes in seconds for typical office documents.
Last reviewed: July 2026
What is this?
A PDF's page tree is a hierarchical structure where every page is a leaf under a root node. Merging two PDFs means taking the leaves from document B and re-parenting them under document A's root, then rewriting the cross-reference table so the resulting file remains valid. Shared resources β fonts, images, color profiles β are copied over rather than deduplicated, which is why merged files can be larger than the sum of their inputs. Understanding this helps explain why merge order matters (later pages appear later) and why merging identical templates repeatedly bloats file size.
How to use this tool
- 1Choose two or more PDF files. Drag them in or use the file picker. The order shown is the merge order β reorder before processing if needed.
- 2Review the file list. Remove any file you added by mistake. If a file is password-protected, unlock it first using the Protect tool, since merging encrypted files usually fails.
- 3Click Process to combine the files. The tool parses each PDF, re-parents pages into one document, and rewrites the internal reference table. This runs locally in your browser.
- 4Download the merged PDF. Open it in your PDF reader to verify page order before sending it onward β merge is fast but not foolproof for edge cases like linearized PDFs.
Tips & best practices
- Merge order equals output order. If you want a cover letter first, put it at the top of the list before processing.
- Total input size above 100MB may exhaust browser memory on mobile devices (iOS Safari caps at roughly 40-60MB per tab).
- Merging PDFs that share fonts produces a larger output than either input because pdf-lib re-embeds fonts rather than deduplicating.
- If a merged PDF opens with warnings in Adobe Acrobat but not in Chrome's viewer, one of the inputs may use an unusual encoding β re-save it through the Compress tool first.
- For repetitive merges (monthly reports), consider maintaining a template order rather than merging fresh each time to keep file size predictable.
Common use cases
- A paralegal consolidating a signed contract, its exhibits, and a certificate of service into a single filing packet.
- An accountant preparing a quarterly tax return by joining scanned receipts, bank statements, and a summary spreadsheet exported to PDF.
- A student compiling scanned lecture notes, assignment drafts, and reference articles into one revision document.
- A real estate agent combining a property listing, inspection report, and disclosure statement before sending to a buyer.
- A researcher merging a manuscript, cover letter, and figure supplements into a single submission file for a journal.
- An HR coordinator assembling an onboarding packet from a benefits guide, tax forms, and company handbook chapters.
Technical notes
- The tool uses pdf-lib's copyPages() to transfer pages, which preserves rotations, annotations, and hyperlinks in most cases.
- Page order in the output follows the order in the input list β reorder before processing, not after.
- PDF 1.4 through 1.7 documents merge reliably. PDF 2.0 files usually work but complex features (e.g., portable collections) may lose fidelity.
- Very large PDFs depend on available browser memory; Chrome desktop typically handles 200MB total, mobile browsers 40-80MB.
- Forms (AcroForm), digital signatures, and encrypted content usually require preprocessing (decrypt, flatten, or remove) before merging cleanly.
- Bookmarks from source files are not automatically merged into a unified outline β use the Edit Bookmarks tool afterward if a table of contents is needed.
Private by design
This tool runs in your browser. Your file is not uploaded to our server while using the tool.
Limitations
- Password-protected PDFs cannot be merged directly. Remove the password first with the Protect tool.
- Digital signatures on input PDFs will be invalidated in the output because merging changes the byte content the signature covers. If signatures must be preserved, keep those documents separate.
- AcroForm fields with the same name across files may conflict in the merged output; consider flattening forms first using the Flatten tool.
- Linearized (web-optimized) PDFs are re-serialized in a non-linearized form after merging. Run Compress afterward if fast web viewing matters.
- The tool does not deduplicate embedded resources. Merging 20 copies of a template with the same 5MB image produces a large file β this is a pdf-lib behavior, not a bug.
- Merged output is compatible with modern viewers (Adobe Reader 11+, Chrome, Firefox, Safari), but older Preview.app versions may misrender pages that use PDF 1.7 extension levels.
Frequently Asked Questions
What actually happens when I merge two PDFs?
The tool reads both files, extracts their page trees, and combines them under a single root in a new PDF. Shared resources like fonts and images are copied into the output. The result is a fully valid PDF that any reader can open.
Why is my merged PDF larger than the sum of its inputs?
pdf-lib re-embeds resources rather than deduplicating them. If two source files share the same fonts, both copies end up in the output. This is normal β run the Compress tool afterward if size matters.
Can I merge password-protected PDFs?
Not directly. Unlock the file first using the Protect tool. If the file has an owner password but no user password, some viewers ignore it, but our merger still refuses to open it. Removing the password is the reliable path.
What happens to bookmarks and links after merging?
Internal hyperlinks (e.g., a table of contents link within one document) usually survive because they target pages that are still present. Bookmarks from the source files are not merged into a unified outline β you would need to rebuild the outline manually or use the Edit Bookmarks tool.
How large a merge can my browser handle?
On desktop Chrome or Firefox, up to about 200MB of combined input is safe. Mobile browsers are stricter β iOS Safari typically caps a single tab at 40-60MB of PDF data before crashing. Split very large jobs into batches.
Do digital signatures stay valid after merging?
No. A digital signature covers a specific byte range of the file. Merging changes that byte range, so any signature is invalidated. Keep signed documents separate, or merge first and then re-sign.
Is there a limit on the number of files I can merge at once?
There is no hard limit, but practical limits come from browser memory. Fifty small PDFs is usually fine. Fifty scanned image-heavy PDFs (say 20MB each) may exceed the browser's memory budget.
Are my files uploaded to a server?
No. The merge runs entirely in your browser using pdf-lib. When you close the tab, all working data is gone. This tool has no upload endpoint.
Why does the output open with warnings in some viewers?
Merged PDFs may inherit encoding quirks from source files. Adobe Acrobat is stricter than Chrome's built-in viewer. If you see warnings, run the merged file through the Compress tool once β it re-serializes the document and usually clears benign warnings.