Merge PDF Files Online, Free and Private

What is a PDF merger?

A PDF merger takes several PDF files and combines them into a single document, in the order you choose. This one runs the merge entirely inside the browser tab: the files you drop in are read and reassembled on your own device, and no copy of them is ever sent anywhere. That matters because of what people actually merge — a payslip and a bank statement for a mortgage application, a stack of scanned medical letters, a passport photo page and a visa form. Handing those to a server you do not control, even briefly, is a choice most competing tools make for you without asking.

Merging is different from editing a single PDF: nothing about the pages themselves changes, only their arrangement into one file. Drop in a contract, an invoice and a signed cover sheet, put them in the right order, and the tool builds one PDF with every page from every source file, ready to send or print as a single attachment.

How to use it

1. Add your PDFs. Drag a batch of files onto the drop zone, or click it to pick them from your device. Each one appears in a list showing its name, page count and size.
2. Put them in order. The list order is the merge order, so use the up and down buttons on each file to arrange them, remove one you do not need, or click Add more files to bring in another. The total page count and output size update as you go, and Clear starts you over.
3. Download the merged file. Once the order looks right, click Download to save the combined PDF. If your files do not all share a page size, a note tells you before you download so it is not a surprise at the printer.

What survives the merge, and what does not

Page content survives exactly. That is not just an assumption — it was tested by merging two sample files and reading the result back with a completely different PDF library, one that had no part in building the merge. It reported the pages in order: ALPHA page 1, ALPHA page 2, BETA page 1, BETA page 2, BETA page 3, matching the order the files were listed in, not their filenames. Text, fonts, images and vector art all carry across untouched, because the merge copies the actual page objects rather than re-rendering them.

What does not survive is the document-level information that sits above the pages. A test file with the title The Original Title and one fillable form field came out the other side with no title and zero form fields, while its page text was intact. That is structural, not a bug: bookmarks, interactive form fields and metadata belong to the document, not to the pages inside it, and a merge produces a new document. If you have filled in a form and need those answers to survive, flatten the form in the app that made it before merging.

The merged file also carries no fingerprint of its own. Most PDF tools write their own name into a file's Producer field every time they save, and the library behind this one does it even when it merely opens a file — that is switched off here, and it was checked directly: the Producer field in the merged output is empty. A tool that promises no watermark should mean it literally, not just visually, and that includes not signing the file behind your back.

Page sizes, file sizes and the honest limits

Page sizes are preserved exactly, not normalised to a common size. Merging an A4 file (595 by 842 points) with a US Letter file (612 by 792 points) produces one document where each page keeps its original dimensions — nothing is resized, scaled or letterboxed to match. When a set of files does not share a page size, the tool flags it, because it is the kind of thing you want to know before you print, not after.

Merging is not compression, and it is worth being precise about that. Two small test files totalling 2,363 bytes merged down to 1,550 bytes, 34 percent smaller, but only because each PDF's own header and trailer overhead gets paid once instead of twice. Run the same test on two 60-page files totalling 26,210 bytes and the merged output comes to 25,467 bytes, 97.2 percent of the sum: once the files are big enough for that one-time overhead to stop mattering, the output size just tracks what went in, because every page's content is carried over in full rather than shared or squeezed.

That has a practical consequence: merging cannot make a large file smaller. Two 40 MB scans merged together come out around 80 MB, not less. The tool also cannot open a password-protected PDF — remove the password in the app that created it first — and it caps a single merge at 5,000 pages so an accidental folder-wide selection cannot lock up the tab. Because the whole merge runs on the page's main thread, a very large batch will make the tab pause while it works.

Why is it free?

This tool runs entirely in your browser, so there is no server cost tied to how many files you merge or how often, no reason to charge for it, and no account to create just to try it.

There is no watermark, and now you know exactly what that means here: the merged file's Producer field is empty, checked directly rather than assumed. No paid tier unlocks a cleaner file, because there is not a dirtier one to begin with.