Cookies for analytics and advertising
We use cookies for analytics and advertising, both sent to Google. Refusing changes nothing you can see.Read the privacy page
Add two or more PDFs, put them in the order you want, and get one document back. The merging happens inside your browser — which for the things people actually merge, like a signed contract and its annexes or a set of scanned statements, is the part that matters. Nothing is uploaded, nothing is stored, and nothing is stamped on the result.
Where it runs
PDF files are read in the browser. Nothing is uploaded.
No queue, no account
It starts the moment you drop the file, and it never asks who you are.
No watermark
What comes out is the file you made, with nothing added to it.
Merging copies the page objects across rather than redrawing them, so the result is not a picture of your documents — it is your documents. Text stays selectable and searchable, vector artwork stays sharp at any zoom, and images are carried over byte for byte. There is no quality setting here because there is no quality decision to make.
That also means the finished file is roughly the sum of its parts. If the result is larger than you want, compressing it afterwards is the separate step, and it is a real one rather than something a merge tool should be doing to your file without asking.
Bookmarks, form fields, the document outline and any embedded attachments are lost. These are structures that point at pages by reference, and carrying them correctly across several documents whose page numbering has just changed is a much harder problem than copying pages — one that tools which claim to do it often get subtly wrong.
Saying so up front is better than letting somebody merge a hundred-page report and discover afterwards that its table of contents no longer goes anywhere. If your documents rely on any of those, merge them in a full PDF editor instead. For the ordinary case — scans, statements, a contract and its annexes, pages that arrived in separate emails — none of it applies.
Look at what people merge: signed contracts, invoices, medical letters, bank statements, application packs with passports in them. It is one of the most sensitive things anybody does with a file, and the usual way to do it is to hand all of the documents at once to a website in exchange for a download link.
Here they never leave your device. You can check that rather than believe it — open the network tab in your browser’s developer tools and watch while you merge, or disconnect from the internet entirely and merge anyway. It works, because the code doing the work is already on your machine.
No. The merge runs entirely in your browser and the files never leave your device. Given that people mostly merge contracts, statements and application documents, this is the reason the tool is built this way rather than a nice extra.
Yes, and the order is the whole operation — the list you arrange is the document you get, with the first file becoming the first pages. Files are never silently sorted by name, because that would be a different tool from the one you asked for.
Not at all. The pages are copied rather than re-rendered, so text stays selectable, vectors stay sharp and images are carried across byte for byte. There is no quality setting because there is no decision to make.
No, and this is the honest limit of the tool. Bookmarks, form fields, outlines and attachments point at pages by reference, and carrying them across documents whose numbering has just changed is a much harder problem than copying pages. If your files depend on those, use a full PDF editor.
No limit that we impose, and no account or watermark. Because nothing is uploaded there is no capacity to ration — the practical ceiling is your own memory, so a very large set is the case most likely to strain a phone.
No. A protected file cannot be read without its password, so there is nothing to copy. Open it with the password, save an unprotected copy and merge that. We name which file is the problem rather than failing with a generic error.