Merge PDF without uploading
Combine multiple PDF files into one — in your browser.
Drop PDF files here, or click to upload
Select multiple PDFs — they'll merge in the order shown below
This merges PDF files without uploading them. Your documents are read into your browser's memory, combined with the pdf-lib JavaScript library, and written back out as a single download — no file data is ever sent to a server. That matters because most free PDF mergers work the opposite way: they upload your document, process it remotely, and rely on a retention policy to tell you it was deleted afterwards. Here there is no upload to retain. Pages are copied object by object rather than re-rendered, so embedded fonts, selectable text and image compression survive the merge unchanged and the output is roughly the sum of its inputs in size. The practical ceiling is your device's memory rather than a server-side quota: a few dozen ordinary documents merge comfortably on any modern machine, while a set totalling several hundred megabytes may stall a low-memory phone. The one file it cannot open is a password-encrypted PDF, which must be unlocked in a viewer first.
About the PDF Merger
Merge PDF files without uploading them anywhere. Your documents are read into your browser's memory, combined locally with pdf-lib, and handed straight back as a single download — no server ever sees them. Open your developer tools while you merge and you will see no request carrying your file, because none is made.
How to use the PDF Merger
- 01Drag and drop your PDF files, or click to choose them from your device.
- 02Reorder the files by dragging them up or down in the list.
- 03Remove any files you don't need with the × button.
- 04Click “Merge & download” to save the combined PDF.
Why use our PDF Merger
- 01
Unlimited files
Combine as many PDFs as your browser memory allows, in any order.
- 02
Drag-to-reorder
Arrange the merged document exactly how you want with a simple drag.
- 03
Fully client-side
Powered by pdf-lib — your documents never leave your computer.
- 04
No watermarks
Free forever, no sign-up, and absolutely no watermarks added to your file.
How does merging a PDF in the browser work?
When you drop files in, each one is read with the FileReader API into an ArrayBuffer that exists only in the tab's memory. pdf-lib parses the PDF object structure, and the merge copies page objects from each source document into a new one, preserving the content streams, embedded fonts and images byte-for-byte. Nothing is re-rendered or re-encoded, which is why a merged PDF looks pixel-identical to its sources and why text stays selectable and searchable afterwards. The finished document is turned into a Blob and handed to the browser as a download via an object URL. You can verify the whole claim yourself: open your browser's developer tools, switch to the Network tab, and merge a file. No request carrying your document appears, because none is made. Disconnecting from the internet after the page loads and merging anyway is an even simpler test — it still works.
Why uploading a PDF is a bigger deal than it looks
PDFs are the format people use for exactly the documents they would least like to hand over: signed contracts, medical letters, bank statements, passport scans, tax returns, tenancy agreements. Uploading one to a free web service means it exists on infrastructure you do not control, governed by terms you probably did not read, for a retention period you cannot audit. Even where the operator is entirely honest and deletes files on schedule, the document has still traversed a network, been written to disk somewhere, and possibly passed through a CDN or a logging layer on the way. The strongest privacy guarantee is not a good policy — it is an architecture where the sensitive data never leaves the device, so there is nothing to retain, breach, subpoena or mishandle. That is the actual difference between this tool and a server-side merger, and it is why the file-size ceiling here is your device's memory rather than an upload limit.
Practical limits and what to do about them
Everything runs in your browser's memory, so a very large job is bounded by available RAM rather than by a server quota. Merging a few dozen ordinary documents is unremarkable; merging several hundred-megabyte scanned files at once can make a tab sluggish or, on a low-memory device, crash it. If you hit that, merge in batches and then merge the results. Encrypted PDFs are the other constraint — a document protected with an open password cannot be parsed until it is decrypted, so remove the password in your PDF viewer first and merge the unlocked copy. Files that use owner passwords to restrict printing or editing, rather than to restrict opening, generally merge without trouble. Finally, form fields and annotations are carried across, but two documents containing form fields with identical internal names can collide in the merged file; if you rely on fillable forms, check the output before distributing it.
Client-side merging compared with an upload-based service
| Aspect | In your browser | Upload-based service |
|---|---|---|
| File leaves device | No | Yes |
| Works offline after load | Yes | No |
| Size limit | Your device's memory | Server-imposed cap |
| Retention risk | None — nothing stored | Governed by their policy |
| Speed | No upload or download wait | Bounded by connection |
| Watermarks | Never | Common on free tiers |
Verify the first row yourself: open the Network tab in developer tools and watch for a request while merging.
Frequently asked questions
Are my PDF files uploaded to a server?
No. Merging runs entirely in your browser using pdf-lib. You can confirm it by opening the Network tab in developer tools while merging, or by disconnecting from the internet after the page loads — the merge still works.
Is there a limit on how many PDFs I can merge?
There is no imposed cap. The practical limit is your device's memory, so dozens of ordinary documents merge comfortably while several very large scanned files at once may strain a low-memory device.
Will the merged PDF keep the original formatting?
Yes. Pages are copied at the object level rather than re-rendered, so fonts, images, layout and vector content are preserved exactly and text remains selectable.
Can I merge a password-protected PDF?
Not while it is encrypted. Open it in your PDF viewer, remove the password, save an unlocked copy and merge that. Owner-password restrictions on printing or editing usually merge fine.
Does the merger add a watermark?
Never. The output contains only your original pages — no branding, no added cover page, no sign-up.
Can I control the order of the pages?
Yes. Drag the files up or down in the list before merging; the merged document follows that order exactly.
What happens to fillable form fields?
They are carried across, but fields sharing identical internal names across two source documents can collide. Check the merged file if the forms matter.
Does merging reduce quality?
No. Nothing is re-compressed or rasterised — the page content is copied as-is, so the merged file is visually identical to its sources.
Why is my merged file larger than I expected?
Each source keeps its own embedded fonts and images, so the merged size is roughly the sum of the parts. Run the result through the PDF compressor if you need it smaller.
Last updated
Built on pdf-lib for PDF object manipulation. Behaviour verified against the PDF 1.7 specification (ISO 32000-1) for page-tree copying and document structure.