Merging two PDFs sounds like a five-second task — until you consider that most online merge tools require you to upload your documents to a third-party server, where they sit in a queue with everyone else's contracts, invoices, and résumés.
Why uploading is the real risk
A PDF often contains exactly the data you least want shared: tax figures, signed agreements, personal identifiers. When you upload one to a random tool, you're trusting that server's storage, retention policy, and security posture sight unseen. Privacy-conscious tools sidestep the problem entirely by processing the file on your own device.
How browser-side merging works
Modern browsers can parse and combine PDFs locally using JavaScript — no server involved. You select your files, the browser reads them into memory, merges the pages in your chosen order, and hands you the combined result. The file never makes a network request, is never stored, and is gone from memory when you close the tab.
ForgePlug's Merge PDF tool works exactly this way: drag in files, reorder pages with a thumbnail preview, and download the merged PDF. Need to pull pages out instead? Split PDF extracts ranges or individual pages. And when the result is too big to email, Compress PDF shrinks it with a quality slider — all equally local.
Merge PDFs in your browser
Combine documents with drag-and-drop ordering, or split and compress — your files stay on your device the entire time.
Open Merge PDFWhat merging actually does to your documents
A PDF is not a linear stream of pages — it is a collection of numbered objects (pages, fonts, images, annotations) with a page tree describing the order they appear in. Merging means copying the objects from each source document into one new file, renumbering everything so there are no collisions, and building a combined page tree. That detail explains most of the surprises people hit, because some things survive that copy cleanly and some do not.
Page content, embedded fonts, and images come through reliably. Internal links, bookmarks, and form fields are where behaviour varies between tools, because each requires rewriting references that pointed at the old document structure. It is worth checking these specifically in the output rather than assuming they carried over.
Four things that catch people out
Mixed page sizes are the most visible. Merging an A4 document with a US Letter one produces a file where pages are physically different dimensions — fine on screen, awkward when printed, and it looks like a mistake to whoever receives it. PDFs support per-page sizing, so nothing errors; you just get an inconsistent document.
Form field collisions are the most damaging and the least obvious. Interactive form fields are identified by name, so merging two copies of the same template — two filled-in application forms, say — gives you a document with two fields both called "full_name". Many viewers treat identically-named fields as the same field, so typing in one updates the other, and the merged form can show one person's data in both places. If you are combining filled forms, flatten them first so the values become static page content.
Digital signatures do not survive, and this is by design rather than a bug. A signature certifies one exact byte sequence; merging produces a different file, so the signature no longer validates. If a document needs to remain verifiably signed, it has to stay a separate file — merge the unsigned material and attach the signed document alongside it.
File size is rarely the sum of the inputs. Two 3 MB documents built from the same template often merge to well under 6 MB, because shared fonts and repeated images can be stored once. Conversely, merging documents that each embed a different full font set can produce something larger than expected. If the result needs to clear an email attachment limit, check the actual output size rather than adding the inputs together.
Getting the order right the first time
Reordering after the fact means either re-merging or shuffling pages in a separate step, so it is worth arranging files before you run the merge. For document bundles that someone else will read — a rental application, a grant submission, a case file — order the sections the way the recipient's checklist is written rather than the order you happened to collect them. Whoever reviews it is working down a list, and a bundle that matches that list is materially faster to process.
Look for the privacy promise
Before using any document tool, check whether it processes files locally. If a tool says "upload" anywhere, your document is leaving your device.