Guide
How to merge PDF files without uploading — using the PDF Pro local merger.
This guide is for anyone stitching together a contract pack, an expense bundle, or a board deck — and who'd rather not push the whole thing through somebody else's server first. Five steps, real screenshots, and the small handful of mistakes that turn a tidy merged PDF into a 90-page mess in the wrong order.
What you'll need
- A modern browser (Chrome, Edge, Firefox, or Safari from the last two years)
- Two or more PDF files on your device — local disk, USB, or a synced folder all work
- About two minutes, including the time to drag rows into the right order
- No installs, no account, no upload
The five steps
Open the local merger
Head to the PDF Pro local merger. The page is a single HTML document with the merge engine bundled as WebAssembly — once it loads, you can disconnect from the internet and the merge still works. That's the proof your files aren't being uploaded: there's nowhere to upload them to.
Add your PDFs to the queue
Drag two or more files onto the drop zone, or click and pick them with the OS picker. Each PDF is parsed in place: the merger reads its page count, generates a thumbnail strip, and adds a row for it. Adding more files later just appends to the end of the queue — you can also remove individual rows with the trash icon.
Mixing protected PDFs into the queue is where most people trip. If a file has owner-password restrictions on assembly, the row will show a small lock icon and refuse to merge until you remove the password upstream.
Drag the rows into the right order
Each row has a grip handle on the left. Grab it and drag the row up or down — the output PDF follows the row order top to bottom. There's no "primary file"; the first row's metadata becomes the merged document's metadata by default, but you can override that in the output panel.
Pick page ranges per file (optional)
Click the page count on any row to open its range editor. The syntax is forgiving: 1-3 takes the first three pages, 2,5,7-9 takes a custom mix, and 1-end takes everything (the default). This is where you trim a 60-page board deck down to the four pages you actually need to attach.
Name it and save the merged PDF
The output panel asks for a filename — default is merged.pdf, but a name like acme-msa-package-2026-04.pdf will save you grief at the email-attachment step. Click Merge & download. The file is assembled in memory and handed to your browser's downloads folder. Open it and confirm the page order matches the queue you set up.
Common mistakes & gotchas
- Forgetting to reorder before merging. The queue order is the output order. If you drop files alphabetically and don't drag, you'll get them alphabetically — which is rarely what a contract pack needs.
- Mixing in a password-protected PDF. Owner-locked PDFs can't legally be combined without removing the restriction first. The merger will refuse and tell you which row is the problem.
- Assuming bookmarks merge. Some merge engines drop bookmarks, others concatenate them. PDF Pro keeps them and prefixes each set with the source filename so the table of contents stays useful.
- Page-range typos.
5-3is invalid (start > end). The editor highlights bad ranges in red — don't ignore that and click Merge anyway. - Naming the output
merged.pdffor the third time today. Your downloads folder will quietly turn intomerged (3).pdf,merged (4).pdf… and you'll attach the wrong one to a client. Name it descriptively at step 5.
Troubleshooting
One of my PDFs has a password — how do I include it?
If it's a user password (required to open the file), unlock it first with the PDF Pro unlock tool and then drop the unlocked copy into the merger. If it's an owner password (restricting assembly), you need explicit permission from whoever set it — bypassing those restrictions isn't something a browser tool will do for you.
The merged file is huge. Should I compress it?
Yes — merging is purely additive, so the output is roughly the sum of the inputs. After merging, run the file through the lossless compressor with Keep Text mode and you'll typically cut 40–70% with no visual change.
Page numbers in the merged PDF restart at 1 for each section. Is that expected?
Page numbers printed on the pages are part of each source file and don't auto-renumber when merged — this is by design, since rewriting them would alter signed content. If you need a unified page count, add a header/footer in a separate pass after merging.
Can I merge a PDF with an image or a Word doc using this tool?
The merger only takes PDFs, by design — converting on the fly invites font and layout surprises. Convert images or Word files to PDF first (most operating systems can print-to-PDF in two clicks), then drop the resulting PDF into the queue.
I have 50 files to merge. Will the browser handle it?
Usually yes — the bottleneck is total page count, not file count. A 50-file queue with ~500 total pages is comfortable on a modern laptop. If you're combining 5,000+ pages, split the job into two merges and combine the two outputs at the end so the tab doesn't run out of memory.
Ready to merge?
Open the local merger and run your files through the five steps above.