Why merge PDFs locally instead of using iLovePDF or Adobe?

Server-based merge tools upload your files. For documents like signed contracts, tax forms, medical records, or NDAs that's a privacy trade you may not want to make. Local merge runs in your browser; the file bytes never leave the page.

Is there a file-size limit?

25 MB per input PDF on Free File Converter. Most contracts and document scans land well under that. Need to merge larger files? Run multiple passes.

In what order do the pages end up?

PDFs merge in the order you added them. Drag them onto the page in the sequence you want them to appear. Re-drop in a different order if you got it wrong — it takes about two seconds.

Will the merged PDF lose any formatting?

No. The merge copies pages byte-for-byte from each source PDF into the output. Fonts, images, form fields, hyperlinks, and digital signatures are preserved. The only thing that changes is which PDF the page now lives in.

Does this work offline?

Yes. Once the page has loaded once, the merge code is cached as part of the Progressive Web App. You can merge PDFs on a plane with no Wi-Fi, on a locked-down corporate network, or in any other no-upload environment.

How to Merge PDFs in Your Browser Without Uploading

You need to combine three signed PDFs into one — a contract, an NDA, and a W-9. You search "merge PDF," click the first result, and notice the small print: "Drop your files to upload." The site promises to delete the files later. But you're being asked to hand a signed contract to a server in another country on faith. Maybe that's fine. Maybe it isn't.

There's a way to do this that doesn't involve any of that. Modern browsers can read, edit, and write PDFs locally using a library called pdf-lib. No server in the loop, no upload, no signup. Here's how it works.

Merge PDFs locally

The three-step browser merge

Open freefileconverter.ai/merge-pdf.
Drop your PDFs onto the drop zone in the order you want them combined.
Click Convert. The merged PDF downloads as merged.pdf.

That's the whole flow. There's nothing else. No "verify your email," no "you've reached the free limit," no countdown timer urging you to upgrade. The work happens on your laptop or phone.

Why the upload model exists at all

PDF merging used to require a server because:

JavaScript engines weren't fast enough to parse and rewrite multi-megabyte binary documents.
The PDF libraries that did the work (Ghostscript, qpdf, iText) were native code and couldn't be shipped to a browser.

Both changed around 2019. Modern V8 and SpiderMonkey can crunch PDFs at reasonable speed, and pure-JavaScript libraries like pdf-lib handle the format competently. There's no longer a technical reason to upload — only a business reason (server-based tools serve ads while you wait).

iLovePDF / Adobe / Smallpdf vs. local merge

	Server-based merge	Local browser merge
File leaves your device?	Yes	No
Signup required?	Often, for >2 files or >25 MB	No
Free file-size limit	Typically 25–100 MB total	25 MB per file (no daily cap)
Works offline?	No	Yes, after first visit
Speed	Limited by upload bandwidth	Limited by your CPU
Ads while waiting?	Usually	No
You can verify no upload?	No	Yes (DevTools Network tab)

How to verify it really is local

Worth checking yourself if you're handling anything sensitive:

Open /merge-pdf and press F12 to open DevTools.
Click the Network tab and clear it.
Drop your PDFs and click Convert.
You'll see the resulting download as a blob: URL — there's no outbound POST carrying your PDF data.

Or, even more decisively: load the page, then disconnect from Wi-Fi entirely. Drop your files and merge. It still works.

When you'd want this

Signed contracts. A counter-signed PDF should not be sitting on a random server's hard drive.
Tax forms (1099s, W-2s, K-1s). These contain your full name, address, and SSN. Don't upload them.
Medical records. HIPAA isn't directly your problem as a patient, but the principle holds.
Internal corporate documents. Many companies' acceptable-use policies prohibit uploading work documents to consumer SaaS tools. Local merge is in-policy by default.
Combined receipts for expense reports. The accountant wants one PDF. You don't want every receipt on a third-party server.

Pages out of order? Reorder before merging

The merge order is the drop order. If you got it wrong:

Click Convert another to clear the file list.
Re-add the PDFs in the correct sequence.
Convert again.

If you need to drop a specific page from one of the source PDFs first, use Split PDF to break it into its component pages, then merge the pages you want in the order you want them.

Related PDF tasks that also stay local

The same browser-based approach handles other common PDF jobs:

Split a PDF — break a large file into individual pages.
Rotate PDF pages — fix sideways scans before sending.
PDF to JPG — extract a page as an image.
PDF to text — pull text content out of a PDF without OCR-uploading.
Image to PDF — bundle photos into a new PDF (great for receipt scans).

The bottom line

Combining PDFs is a common task that briefly involved uploading them to strangers' servers because the browser couldn't do it. The browser can now do it. The upload step is a habit, not a requirement.

Open the PDF merger