PDF Merger

What the PDF Merger actually does

The PDF Merger takes two or more PDF files and stitches them into a single document, in whatever page order you specify. Drop files into the page, drag them up or down to fix the order, click Merge, save the result. That's the entire workflow.

The interesting part is what it doesn't do. It doesn't upload anything. Your PDFs never touch a server — there isn't one to touch. The merge runs in your browser using a JavaScript PDF library called pdf-lib, the same library that powers a lot of document-handling code in production apps. Your contracts, your tax returns, your medical records, whatever you're combining — it stays on your machine. You can verify this in the browser's developer tools: open the Network tab, run a merge, and you'll see zero upload requests. The architecture is the privacy guarantee.

Most popular PDF merger sites work the opposite way. iLovePDF, Smallpdf, PDF24, Sejda — they all upload your files to their servers, process them, and let you download the result. Technically that works fine. Practically it means a copy of your document sits on a third party's machine for some amount of time, governed by whatever their privacy policy says today. For a lot of documents that's a non-issue. For some documents it's a problem you'd rather not have.

How to merge PDFs in the browser

The flow is short on purpose:

1. Drop your PDF files into the upload area (or click to pick them from your file browser). You can drop several at once.
2. Reorder them with the up and down arrows next to each file name. The merged PDF follows the list from top to bottom.
3. If a file is password-protected, the tool flags it with a clear notice. Remove the password in another viewer first, then add the decrypted copy.
4. Click Merge. The merge runs locally — depending on file sizes and your machine, this is usually a second or two.
5. Click Download to save the combined PDF. It saves as merged.pdf by default; rename it to something useful.

There's no signup, no email capture, no free-trial countdown. Close the tab when you're done and the files vanish from memory.

Worked example: combining three contracts

Say you're closing a freelance project and need to send the client one packet containing the signed contract, the NDA, and the final invoice. You have three PDFs:

• contract-signed.pdf — 5 pages
• nda-signed.pdf — 12 pages
• invoice-2026-final.pdf — 3 pages

Drop all three into the merger. The list shows them in upload order, which might not be the order you want. The contract should come first, the NDA second, the invoice last — that's the natural reading order for the client opening the packet. Use the arrows to confirm or fix the order. Click Merge.

Open the result in Preview, Adobe Acrobat, or any PDF viewer. The page count should match the sum of the inputs (5 + 12 + 3 = 20). The text should be selectable on every page. Any clickable links in the original PDFs still work. If you forgot a page or got the order wrong, redo the merge — the input files in your list don't move until you reload the page.

How it compares to the big PDF sites

Most of the well-known PDF merger sites have grown into multi-tool platforms with subscription tiers, free-trial gates, and ad slots. Here's how the practical user experience compares for someone who just wants to combine three PDFs:

The Microapp limit isn't a paywall — it's the practical ceiling on what a browser can hold in memory while running pdf-lib. If your files are bigger than that, the merge would either get slow or crash the tab. A 100 MB combined ceiling covers basically every real-world merge most people will do (combining a handful of contracts, receipts, or scanned chapters). The big PDFs that push past it tend to be scanned books or high-resolution image-heavy reports, where a desktop tool is honestly the right call anyway.

What gets preserved and what doesn't

The merge appends pages from the source PDFs into the output PDF. That means:

• Page content is preserved exactly. Text, images, vector graphics, layout — everything visible on the page stays the way it was.
• Text remains selectable and searchable. The merger doesn't rasterize anything; if your source PDF had selectable text, the merged version does too.
• Internal hyperlinks within a page stay clickable. External links (mailto, http) carry over.
• Bookmarks (the outline panel) often don't carry over. pdf-lib copies pages but doesn't reliably rebuild the document-level outline tree. For most use cases this doesn't matter; if you're merging a 300-page reference manual where bookmark navigation is essential, a desktop tool like Adobe Acrobat handles it better.
• Form fields may not survive. If your PDFs have interactive AcroForm fields, the merger may flatten them. Sign before merging, not after.
• Digital signatures will be invalidated. This isn't a bug — it's how PDF signature security works. A signature certifies the exact bytes of a document; the moment those bytes change (and merging changes them), the signature is no longer cryptographically valid. Sign the final merged PDF if you need a signature on the combined document.

If your merge needs to preserve every last metadata detail — bookmarks, form fields, signatures, complex annotations — that's a job for Adobe Acrobat Pro. For the everyday case of "combine these documents into one file in this order," the browser-based merger covers it.

When the merge fails (and what to do)

If a file is rejected, it's almost always one of three things:

• The file isn't actually a valid PDF. Sometimes a download arrives corrupted, or a screenshot got renamed with a .pdf extension. The tool flags invalid files individually before you try to merge them. Re-download or use a real PDF.
• The file is password-protected. The merger refuses to silently merge encrypted files because the result would be unpredictable. Remove the password first — Preview on Mac will save an unprotected copy if you have the password; on Windows, Adobe Acrobat or a tool like qpdf does the same. Then re-add the decrypted version.
• The combined memory footprint is too large. If your files together push past ~100 MB, the tab can run out of memory mid-merge. Split the job into two passes: merge the first half, save it, then merge that output with the second half.

If a file looks fine and isn't password-protected but the merge still fails on it, it's usually a non-standard PDF (some scanned documents from older devices, or PDFs generated by obscure software, produce structurally valid files that strict parsers still choke on). Re-saving the file through Preview or a print-to-PDF flow normalizes the structure and usually fixes it.

Related tools

The PDF Merger is one piece of a small PDF toolkit on Microapp. All of them run in the browser the same way — no upload, no signup, no watermark:

• Split PDF — the reverse operation: take one PDF and break it into smaller files, either by page count or page range.
• Delete PDF Pages — remove specific pages from a PDF without merging or splitting. Useful when a scan picked up extra blank pages.
• Reorder PDF Pages — drag pages within a single PDF to a new order. Often the right tool when "merge" wasn't really what you needed.
• Rotate PDF — fix pages that scanned in sideways or upside down.
• PDF Extract Text — pull plain text out of a PDF for editing or searching elsewhere.
• Image to PDF — turn JPG or PNG files into a PDF you can then merge with other PDFs.

Frequently asked questions

Are my PDFs uploaded anywhere?

No. The merge runs entirely in your browser using pdf-lib, a JavaScript PDF library. Your files stay on your device. You can verify this directly: open your browser's developer tools, go to the Network tab, and run a merge. There will be no upload requests. Closing the tab clears everything from memory.

Is there a file size limit?

Roughly 50 MB per file and 100 MB combined. The limit comes from browser memory, not from a paywall — push too far past it and the tab can slow down or crash. For most real-world merges (contracts, receipts, signed documents), you'll never come close to either limit. If your files are larger, compress them first or split the merge into two passes.

Why do iLovePDF and Smallpdf upload my files when this tool doesn't?

Different architecture choice. Server-side processing lets those services run more complex PDF operations (high-quality compression, OCR, full bookmark editing) than a browser realistically can. The tradeoff is that your file leaves your machine. For merge — which is fundamentally a copy-pages-into-a-new-file operation — the browser-side version handles the job fine without sending your document anywhere.

Can the tool handle password-protected PDFs?

No. When you add an encrypted PDF, the tool flags it with a clear notice and refuses to merge it. Trying to silently merge an encrypted file would produce broken output, so the merger won't pretend. Strip the password in another tool first (Preview on Mac, Adobe Acrobat, or qpdf on Linux), then add the decrypted copy.

Will my page numbers be renumbered after the merge?

No — the merger doesn't add or modify page numbers. If your source PDFs each show "Page 1 of 5" in their footers, those footers stay exactly as they were. The merged PDF will show your PDF viewer's page count (1 through 20 for a 20-page merge) in the viewer chrome, but the printed footers on each page reflect whatever was in the original document. If you need consistent page numbering across the merged document, regenerate the PDF from a source format (Word, Pages, Google Docs) with continuous numbering, or use a desktop tool that supports page-number re-stamping.

Will the merger invalidate my digital signatures?

Yes — this is a feature of PDF security, not a bug. A digital signature certifies that the document's bytes haven't changed since signing. Merging changes the bytes, so the signature is no longer cryptographically valid. The signed pages still display the visible signature stamp, but verification tools will mark the signature as invalidated. If you need a signed combined document, merge first and sign the result.

Can I drag and drop to reorder files?

For now, use the up and down arrows next to each file in the list. Drag-and-drop reorder is on the to-do list but isn't shipped yet. The arrows do the same job in two clicks instead of one.

Why is the merged file larger than I expected?

The merge appends pages without re-encoding them. So if your source PDFs have high-resolution embedded images, large embedded fonts, or duplicate resources, the merged file inherits all of that weight. The merger doesn't compress or re-encode; it stitches pages in the order you specify. For a smaller file afterward, run a separate PDF compressor — that's its own tool category for a reason (re-encoding is a tradeoff between size and quality you'd want to control explicitly).

Can I merge PDFs with Word documents or images?

Only PDFs in this tool. Mixed-format merging requires conversion first — turn your Word docs into PDFs (most operating systems have a Print to PDF option built in) and your images into PDFs (use the Image to PDF tool), then drop everything into the merger together.

Does the merger preserve color profiles, font embedding, and high-resolution images?

Yes for everything that's already embedded in the source files. pdf-lib copies pages with their associated resources, so embedded fonts, ICC color profiles, and image streams move into the merged document unchanged. If a page rendered correctly in the source PDF, it renders correctly in the merge.