Combine PDFs into one file without uploading them anywhere — the merge runs entirely in your browser, so contracts and invoices never leave your device.
100% private: merging happens in your browser via WebAssembly-free JavaScript — your files are never uploaded anywhere.
What this free tool is great for: a quick, one-off job with no signup — it runs entirely in your browser, so nothing leaves your device and there's nothing to manage.
Its honest limit: it's a quick one-off in your browser — it won't save, track, automate or scale what you do with it.
Search for a PDF merger and you'll land on one of the big upload services: pick your files, send them to a server somewhere, wait, and download the result. It works — but think about what you just did. Contracts, invoices, medical records, ID scans: the documents people merge are routinely the most sensitive files they own, and the standard workflow ships them to a third party's server on trust. This tool takes the other path. The merging happens entirely inside your browser, on your machine, using a well-established open-source PDF library. Your files never leave your device — not to us, not to anyone. That's not a marketing line; it's how the code works, and you can verify it by loading the page, going offline, and merging anyway.
A PDF is a container of objects — pages, fonts, images — with an index describing where everything lives. Merging means creating a new container and copying the page objects from each source document into it, in order, while rewriting the index. Historically that required server software, but modern browsers can run this comfortably: the JavaScript library loads once from a public CDN, then reads your files directly from memory via the browser's file API. Nothing is transmitted. The practical limits are your device's memory — merging a handful of normal documents is instant; merging hundreds of megapixel-scanned pages may take a moment on an older phone — and encrypted files, which need their password removed first.
Copying pages preserves what's on them: text, images, vector graphics, fonts. A few things behave differently and are worth knowing. Interactive form fields can flatten or misbehave when documents with conflicting field names are combined — check any fillable forms after merging. Bookmarks and the document outline generally don't carry over, since they belong to the old containers. Page sizes are preserved per page, so merging an A4 report with a US-letter scan produces a document with mixed page sizes — fine for screens, occasionally surprising in print dialogs. The habit that catches everything: open the merged file once and scroll it before you send it anywhere important.
The tool merges files in the order they appear in your list, and that order is the whole game for documents that will be read by someone else: cover letter before contract before appendix, invoice before receipts. Add files in the order you want, or remove and re-add to rearrange. For bigger assemblies, a naming trick from people who do this weekly: prefix your files with numbers (01-cover, 02-contract, 03-annex) before selecting them, so every file picker in the world sorts them correctly and you can select the whole set in one go. Thirty seconds of naming beats ten minutes of untangling a mis-ordered 60-page merge.
Any time a website offers to process a document, the question is: where does the processing run? If the answer is 'on our servers,' you're trusting their retention policy, their security, their staff and their jurisdiction — usually described in a privacy policy you'll never read. Reputable services do delete files after processing, but 'trust us, we delete it' is still a policy, not a guarantee, and breaches happen to reputable companies every year. Client-side tools change the category of the question: there's nothing to delete because nothing arrived. For casual documents the difference may not matter; for contracts, financials and anything with personal data, it's the difference between a policy and physics.
A few patterns cover most real use. Assembling an application or tender: cover letter, forms, certificates, references — merge once, check page order, send one clean file. Consolidating receipts or invoices for a bookkeeper: merge a month per file, name it clearly (2026-06-receipts.pdf), and your accountant loves you. Combining scanned chapters or handouts: watch orientation — a landscape scan among portrait pages stays landscape, which is correct but can startle. Preparing e-sign packets: merge the contract and annexes before uploading to your signing tool, so the counterparty signs one document instead of five. In every case the merged file is a normal PDF, openable everywhere, no watermarks, no page limits.
Honesty about scope: this is a merger, not a full PDF studio. It doesn't split documents, rotate pages, delete individual pages from the middle of a file, compress oversized scans, run OCR on images, or edit text — and it can't open password-protected files, because they're encrypted precisely so tools can't silently process them. Some of those jobs have honest browser-based answers we may add; others genuinely need heavier software. If you hit those walls weekly — reordering pages visually, stamping, redacting, converting — you've outgrown free single-purpose tools, which is exactly the honest upgrade path described below. One more habit that pays off: after any merge you plan to archive, give the file a name your future self can search — party, subject, date — because a folder of merged.pdf, merged(1).pdf and merged-final-v2.pdf is where documents go to disappear. The merge takes seconds; the naming is what makes it findable in three years.
If PDFs are an occasional chore, this tool plus your browser's print-to-PDF covers most of life, free. But if documents are a daily part of your work — editing text in place, reordering and deleting pages visually, OCR on scans, redacting sensitive lines, compressing files for email, requesting legally-binding e-signatures — you want a real PDF suite rather than a dozen single-purpose tools. That's where Foxit does more: it's the serious Adobe Acrobat alternative at a fraction of the price, with full editing, OCR and e-signing in one app. Merge free here as often as you like; upgrade only when your PDF work outgrows single tasks — and you'll know when it does.
No. The merge runs entirely in your browser using an open-source PDF library — your files never leave your device. You can even go offline after the page loads and it still works.
No artificial limits and no watermarks. The practical limit is your device's memory: everyday documents merge instantly, while hundreds of heavy scanned pages may take a moment on older hardware.
No — encrypted PDFs must have their password removed first (open in any reader with the password and re-save/print to PDF). That protection exists precisely so tools can't silently process them.
Page content (text, images, layout) is preserved. Document-level extras like bookmarks generally don't carry over, and fillable form fields can flatten — check any interactive forms after merging.
Blogger, teacher or toolmaker? Put this calculator on your own page — free forever, no strings. Copy the snippet below (the credit link is appreciated and keeps the tool free):
This tool is free and runs entirely in your browser. The link above is an affiliate link: we may earn a commission if you sign up, at no extra cost to you, and it never changes our honest take.