Choose two or more PDFs to merge them.
The documents people merge are contracts, payslips, medical records and scanned IDs. Every other merge tool on the web asks you to send them somewhere first.
Here the files are read from your disk into this tab and combined there. No upload, no server.
And the order is the whole operation. Merging is not “combine these”, it is “combine these IN THIS ORDER” — and a picker that hands back whatever order the operating system listed produces a document nobody asked for. The files are listed with arrows, and the order is printed above before anything is built.
Pages are COPIED, not moved. A page is not a self-contained thing — it references fonts, images and colour spaces that live elsewhere in the document — and copying is what brings those along. Taking the page object alone produces a page that opens blank.
No. They are read from your disk into this browser tab and combined there. There is no upload and no server — which is the point: the documents people merge are contracts, payslips, medical records and scanned IDs, and every other merge tool on the web asks you to send them somewhere first.
It is the whole operation. Merging is not "combine these", it is "combine these in this order", and a picker that hands back whatever order your operating system listed produces a document nobody asked for. The files are listed with arrows to move each one up or down, and the band at the top prints the order before anything is built.
Because copying a hundred pages between documents is not instant, and doing it again every time you move a file up one place would make the page feel broken. Every other tool on this site recomputes as you type because the work takes microseconds; this one tells you what it will produce and waits to be asked.
The name is a label, not a fact. This page reads the first bytes of the file — a PDF begins %PDF- — because a document renamed .pdf is still whatever it was, and merging it would either fail or produce something broken. Open it in a PDF reader to see what it actually is.
It is refused, on purpose. The pages of an encrypted PDF cannot be read without the password, and merging it anyway produces a document that looks right and shows blank pages — which is worse than a refusal, because you would not find out until somebody else opened it. Remove the password in the program that made it first.
No. The pages are copied whole, with the fonts, images and colour profiles they reference — that is why it copies rather than moves them, since a page on its own renders blank. Nothing is re-rendered or re-compressed, so the merged document is exactly as sharp as its sources.
A total size rather than a count, and the page shows it. Everything happens in this browser tab, so ten files are all held in memory at once along with the document being built. The limit is refused up front with a number rather than failing part of the way through the merge.
Page content, images and fonts come across. Document-level structure — the bookmark tree, form field definitions, attachments — generally does not survive a merge, here or in most tools, because those belong to the document rather than to a page. If a filled form matters, flatten it before merging.
The files are read in your browser and nothing about them is transmitted or stored. Pages are copied whole and nothing is re-rendered — but document-level structure such as bookmarks and form fields generally does not survive a merge, here or anywhere. Nothing you type here is sent to our servers — the calculation runs entirely in your browser.
