How to Merge PDFs Without Uploading Them Anywhere

Quick answer: Open the Merge PDF tool, drop in two or more files, drag them into the order you want, and click merge. Reading the files, stitching the pages, and writing the output all happen in your browser using pdf-lib, a plain-JavaScript PDF library. Nothing is uploaded, there's no server copy of your document at any point, and the result downloads straight to your device.

Combining a few PDFs into one document is one of the most routine things anyone does to a PDF — up there with printing it or signing it. The way most people do it is not routine at all: search "merge PDF," click the first result, upload your files, wait, download. If those files are tax returns or a signed contract, you just handed them to a company you've never heard of. Maybe that's fine. Maybe it isn't, and it's worth knowing what you're actually trading away.

Key takeaways:

• Privacy: a server-based merge tool uploads your files before it can combine them; a client-side one like OxygenPDF never sends the bytes anywhere.
• Size: merged files often come out bigger than the sum of their parts, because each source PDF's fonts and images get copied in separately rather than deduplicated.
• Structure: bookmarks and outline navigation don't survive a merge unless a tool rebuilds them by hand — most, OxygenPDF included, don't. You can rebuild the bookmarks and a contents page afterwards.
• The fix: standardize page sizes and unlock protected files before merging, pick the merge mode that matches what you're actually assembling, and check the result before you treat it as final.

Why Merging PDFs Breaks

A few things go wrong regularly, and they go wrong for structural reasons, not because a particular tool is careless.

Why Does a Merged PDF End Up Bigger Than Its Parts?

Five 2MB files should produce something close to a 10MB merged document. In practice you'll often get noticeably more. The reason is how a PDF stores shared resources internally (fonts, embedded images, color profiles). According to Apryse's documentation on the PDF format, a page's resources are indirect objects, and "the same font resource can be shared across many different pages" within one file, referenced rather than duplicated. That sharing only works inside a single PDF's object table. The moment you copy pages from five separate source files into one merged file, each source file's fonts, logos, and color profiles come along as their own separate copies, because there was never a shared object table linking them across files in the first place. A company logo embedded in every one of your five files gets stored five times in the merged output, even though it's pixel-for-pixel identical every time. That's not a bug in the merge tool; it's the same object-sharing mechanism working exactly as designed, just unable to help you once the sharing needs to cross a file boundary. How much bigger the result actually gets depends entirely on how much your source files have in common — five files sharing one letterhead logo and one custom font bloat a lot; five files built from completely different templates barely bloat at all.

Mixed Page Sizes

A document from your US office uses Letter (612 x 792 points, or 8.5 x 11 inches). The one from your EU partner uses A4 (roughly 595 x 842 points, or 210 x 297 millimeters). Merge them and the pages jump between sizes as you scroll. It looks sloppy on screen and prints worse, since a printer set to one paper size either crops or shrinks every page sized for the other.

Standardizing before you merge, rather than after, is the more reliable order of operations. A page size tool resizes every page to a common target (A4, Letter, Legal, A3, A5, or a custom size you set), fitting the original content by scaling it to fit, cropping the overflow, or centering it without resizing. That takes care of the mismatch in one pass, before it ever reaches the merged file.

Lost Structure

Most merge tools concatenate pages and call it done. Bookmarks, hyperlinks, table-of-contents entries, and cross-references from the original files often don't survive the trip. A bookmark, in PDF terms, is an entry in the document's outline — a separate, document-level navigation tree that points at specific pages by reference, distinct from the page content itself. Because it lives at the document level rather than on any individual page, copying pages into a new file (which is what merging fundamentally is) doesn't automatically bring the outline tree along unless a tool goes out of its way to rebuild it, page by page, in the new document. Most don't. You get a flat stack of pages with no navigation, and a table of contents that lists sections nobody can jump to anymore.

Can I Merge Password-Protected PDFs?

Yes, and this is one place where OxygenPDF's merge tool differs from the "unlock everything by hand first" advice you'll see elsewhere. Drop a password-protected file into the merge tool alongside your other files, and it appears inline in the file list waiting for its password, with no separate unlock step required before you can arrange it, reorder it, or include it in the merge. Enter the password once, and the tool decrypts that file as part of the merge itself.

There's a real trade-off worth knowing about, though, and it's an honest limitation rather than a workaround away from one. Decrypting a password-protected PDF works by rendering each of its pages to an image and rebuilding those pages inside a new, unencrypted document. That's the only way a browser can produce genuinely unencrypted bytes from an encrypted file without a server doing the decryption for you. The result looks identical and every page displays fine, but that file's pages lose their selectable, searchable text; the words are still visible, just no longer text a browser or a screen reader can read as text. This applies equally whether you unlock the file inline during a merge or run it through the standalone Unlock PDF tool first: both go through the same decryption step, so neither one gets you a searchable result. What the standalone tool buys you is convenience, not a better outcome: rasterize the file once and you have a permanently unlocked copy you can drop into any number of future merges without re-entering the password each time, rather than repeating the same decryption inside every merge you ever run it through. If searchable text in the final document matters more than the password does, the only real fix is getting a copy of the file without a password from whoever it came from.

The Privacy Side of It

When you upload a PDF to an online merge tool, the file travels to a remote server, gets processed, and comes back. During that window, your document lives on infrastructure you don't control and, in most cases, can't audit.

People routinely merge PDFs containing:

• Bank statements and tax returns
• Contracts, NDAs, and legal filings
• Medical records and insurance claims
• Passports and identity documents
• Proprietary business reports

Some services claim to delete files after processing. There's rarely a way to verify that from outside the company, and backup systems can retain copies well past whatever the stated retention window says. Terms of service for AI-powered tools sometimes reserve the right to use uploaded documents for model training, disclosed, if at all, several clicks deep.

The regulatory exposure is concrete, not theoretical. Under GDPR Article 83, the most serious category of infringement (which includes mishandling personal data or failing basic security obligations) carries fines of up to €20 million or 4% of a company's total worldwide annual turnover, whichever is higher. "Processing" under GDPR is defined broadly enough that a third-party server briefly holding your file just to merge it counts. On the US side, HHS's HIPAA rules require a signed Business Associate Agreement before any outside service can touch protected health information on a covered entity's behalf. An online merge tool with no BAA in place is not a permitted place to combine a patient's records, no matter how routine the operation feels. And if you've signed an NDA that prohibits sharing documents with unauthorized third parties, a cloud merge tool you didn't clear with the other party is exactly the kind of third party the NDA has in mind.

None of this means uploading a PDF is illegal. It means the question "which server touched this file, and what does their retention policy actually say" is one that you, your compliance team, or a client has to be able to answer on request, and a lot of free merge tools make that question unanswerable by design.

Your Options for Merging PDFs

Server-Based Online Tools

iLovePDF, Smallpdf, Adobe Acrobat Online, PDF24. Upload, process, download.

Your files leave your device for the duration. As of September 2026, iLovePDF's own pricing page caps its free-tier Merge PDF tool at 25 files per task and 100MB total, with unlimited processing gated behind a paid Premium plan — a fairly typical shape for this category: enough headroom for an occasional light merge, a wall the moment it becomes a regular task.

Desktop Software

Adobe Acrobat, Nitro Pro, PDFsam (free, open source). Files stay on your machine once the software is installed.

As of September 2026, Adobe prices Acrobat Standard at 14.99 US dollars a month and Acrobat Pro at 19.99 US dollars a month on an individual plan billed annually, a lot of subscription if merging a handful of PDFs a month is most of what you need it for. Nitro's pricing runs in a similar range. PDFsam is free and handles merging well, at the cost of a less polished interface and a steeper learning curve than a browser tool. None of the three have a hard file-size ceiling, since processing happens locally on hardware you control — but all three require installing something first, which rules out a shared or locked-down machine.

Client-Side Browser Tools

Web apps that run PDF libraries directly in your browser tab. The interface is online, but the processing happens on your device — same privacy profile as desktop software, no installation required.

OxygenPDF works this way. It loads pdf-lib in your browser, copies pages from your source files into a new document entirely on your device, and hands you the result. No upload step, ever — not even a background one. The only hard limit is 50MB per individual file, enforced client-side regardless of how many files you're merging or what plan you're on; there's no cap on the number of files beyond what your device's memory can comfortably hold in a browser tab.

Merge Modes, Explained

OxygenPDF's merge tool offers three ways to order pages once your files are loaded, and picking the right one matters more than it sounds like it should:

Sequential appends every page of the first file, then every page of the second, and so on down the list — the default, and what most people mean when they say "merge these PDFs." A quarterly report followed by its three appendices becomes one document in exactly that order.

Interleave takes page 1 from the first file, then page 1 from the second, then page 1 from the third, and repeats with page 2, page 3, and onward until every file is exhausted. It exists for parallel documents that need to read as a single interwoven sequence — a set of questions in one PDF and its answer key in another, for instance, where you want each question immediately followed by its answer rather than all the questions and then all the answers.

Duplex Scan Fix solves a specific scanning problem. A single-sided scanner fed a double-sided stack captures every front page in order, then every back page in reverse order (since the stack gets flipped as a whole between passes). This mode interleaves the two files the same way Interleave does, but first reverses the page order of every other source file — so a fronts file and a backs file recombine into the correct front-back-front-back reading order without you re-scanning anything or manually re-sorting pages by hand.

A fourth option, insert blank pages, sits alongside the mode selector rather than being a mode of its own: turn it on and, in Sequential mode only, a blank page gets inserted after any source file with an odd page count (except the last one in the list) — the print-shop convention for making sure the next document in a stack starts on a fresh sheet. It has no effect in Interleave or Duplex Scan Fix mode, since there's no single point "after a file" to insert one into once pages are already being woven together from all the files at once.

Merging with OxygenPDF, Step by Step

1. Open the Merge PDF tool and drop in two or more files, or add more at any point with the same dropzone.
2. Drag files into the order you want, or use the sort menu to order them by name, file size, or page count, ascending or descending, or simply reverse whatever order they're in.
3. If a file is password-protected, it shows up inline with a password prompt right in the list — enter it there rather than hunting for a separate unlock step.
4. Rotate a whole source file before merging if it came out of a scanner sideways — rotation applies per file, turning every page it contains, and carries into the merged output.
5. Pick a merge mode: Sequential for most cases, Interleave for parallel documents, or Duplex Scan Fix for a scanner that captured fronts and backs as two separate files. Toggle blank-page insertion on if you need it and you're in Sequential mode.
6. Click merge and download. The result is named by mode (merged-, interleaved-, or duplex-fixed-, followed by the date) so you're not left guessing which settings produced which file later.

Nothing here touches a server. If the result needs a tweak, "Edit again" reloads your original source files (not the merged output) back into the arranger, so you can fix the order or swap a file without starting the whole upload-and-arrange process from zero.

Mistakes That Undo a Clean Merge

Sorting after you've hand-arranged files. Dragging files into a specific order and then clicking a sort option (by name, size, or page count) replaces that manual order entirely — sort is a one-time reordering action, not a filter layered on top of what you already arranged. If you've spent time getting a custom sequence right, that's the last step before merging, not something to reach for casually afterward.

Expecting "insert blank pages" to do anything outside Sequential mode. It's easy to leave the toggle on from a previous merge, switch to Interleave for a different job, and wonder why no blank pages showed up. The option is scoped to Sequential mode specifically, for the reason described above.

Merging a password-protected file and expecting the text to stay searchable. The rasterization trade-off described earlier isn't a bug to report — it's how decrypting a PDF client-side has to work, in the merge tool and in the standalone unlock tool alike. If the merged output needs to stay text-searchable and one of your sources is encrypted, the realistic options are getting an unencrypted copy from whoever sent it, or accepting that file's pages will be images in the final result.

Fixing page size or rotation after merging instead of before. Both operations work fine on an already-merged file, but if three of your five source files need a rotation fix or a page-size standardization and you don't notice until after merging, you're now hunting for the affected pages inside a longer combined document instead of fixing three short, individually manageable files.

Assuming a merge preserves form fields identically across the whole result. Fillable form fields generally travel with their page, but a JavaScript calculation on one form field that references a field living on a different page — common in interactive tax or benefits forms — can break once those two pages end up in different documents, or even just move relative to each other within the same one. Test any interactive form fields in the merged result before treating it as the final version.

Practical Tips

Before merging:

• Name files with numeric prefixes (01-intro.pdf, 02-chapter1.pdf) so a name-based sort — or a quick manual scan of the file list — puts them in the right order without extra work.
• Standardize page sizes first if your sources mix Letter and A4. Run the page size tool before merging rather than living with the mismatch in the combined file.
• If you'll be merging the same protected file into several different documents, run it through Unlock PDF once so you're not re-entering the password on every merge — but expect the same text-searchability trade-off either way (see below).
• Open each file individually first to check for corruption. One badly formed file can derail an otherwise clean merge.

After merging:

• Scroll through the entire result. Confirm every page is present and in the right order, and click a few hyperlinks and bookmarks to see what, if anything, survived.
• Compress the output if it came out larger than expected. Merged files carry duplicated fonts and images from every source file, as covered above, and a compression tool targets exactly that kind of embedded-resource bloat — often bringing a merged file most of the way back down without touching page content. (For the mechanics of what compression actually changes, see compressing a PDF without losing quality.)

Common Use Cases

Finance teams batch invoices and purchase orders together for an audit trail. Tax season means consolidating W-2s, 1099s, and bank statements into one file per filing.

In legal work, contracts get assembled with amendments and signature pages into one authoritative document, and court filings need exhibits and declarations combined into a single submission rather than a scattered set of attachments.

University applications require transcripts combined with recommendation letters. Journal submissions need paper sections merged with supplementary materials. Visa applications, real estate closings, and insurance claims all involve consolidating identity documents and financial proof into one file that a reviewer can open once instead of five times.

Frequently Asked Questions

Is it safe to merge PDFs online?

It depends entirely on which kind of "online" tool you mean. A server-based merge tool uploads your files to process them remotely, which is a real exposure for anything sensitive — the file exists somewhere outside your control for however long processing takes. A client-side browser tool like OxygenPDF is "online" only in the sense that the page loads from a URL; the actual merging runs locally in your browser, and no file content ever leaves your device. The safety difference comes down to where the processing happens, not whether the tool has a website.

Does merging PDFs keep bookmarks, hyperlinks, and form fields intact?

Hyperlinks and form fields that live entirely within a page generally travel with that page when it's copied into the merged file. Bookmarks are the exception: they live in the document's outline, a structure separate from any individual page, and most merge tools — OxygenPDF's included — don't rebuild that outline tree in the new document, so chapter navigation from the original files doesn't carry over. A table of contents made of real hyperlinks (not a bookmark tree) generally still works, since those links are page content rather than document-level structure.

Can I merge password-protected PDFs?

Yes. Drop the locked file in alongside your other files and enter its password when prompted inline in the file list — there's no separate unlock step required before you can merge it. The trade-off: decrypting that file's pages works by rendering them as images, so the merged file loses selectable, searchable text for that file's pages specifically, even though it displays identically. This isn't specific to merging or avoidable by unlocking the file separately first — any client-side removal of a PDF password goes through the same rasterization step, so a pre-unlocked copy has the identical text loss.

Will the merged file be bigger than the sum of my original files?

Sometimes, and by an amount that depends on how much your source files have in common. PDFs share fonts, images, and other resources internally, but only within a single file — merge five files that each embed the same logo or the same custom font, and that resource gets copied into the merged output once per source file instead of once total. Five files with nothing in common barely bloat at all; five files built from the same template with a shared letterhead can bloat substantially. Running a compression tool afterward generally recovers most of the difference.

Can I merge PDFs that use different page sizes, like Letter and A4?

Yes, but the pages won't match visually or in print — a merge doesn't resize anything, it just places each source page as-is into the combined document. If a uniform page size matters for how the final document looks or prints, run a page size tool on the mismatched files first to standardize them to one target size, then merge.

Can I change the order after merging, or undo a merge?

There's no in-place "undo" once a merged file is downloaded, but OxygenPDF's "Edit again" option reloads your original source files — not the merged output — back into the arranger, so you can fix the order, drop a file, or add another one and re-merge from the same starting point rather than re-uploading everything. If you've already lost track of the originals, a split tool can pull the merged file back apart by page, though anything that only lived in the original document-level structure (a bookmark tree, for instance) won't reappear just because the pages are separated again.

Is there a limit on how many files or how large a file I can merge?

Each individual file is capped at 50MB, whether you're merging two files or twenty — that limit doesn't change based on your plan. There's no separate cap on the number of files beyond what your browser tab's available memory can hold comfortably; merging two dozen small files works the same way as merging three large ones, just with more files to keep track of in the arranger.

Does merging break a digital signature on one of the source files?

Yes, and this isn't specific to any one tool. A digital signature on a PDF works by hashing a defined byte range of that exact file and encrypting the hash — the signature is mathematically tied to the file's bytes as they existed at the moment it was signed. Merging builds a new document with a new cross-reference table and new object numbering, so the underlying bytes change even though the visible page content doesn't. Any signature validator checking that page afterward will report it as broken or modified, regardless of whether the merge happened in a browser, a desktop app, or a server. If a signed page needs to keep validating, it needs to stay in its own untouched file; treat combining it into a larger document as a one-way trip.

Do comments, highlights, and sticky notes survive a merge?

Generally yes, more reliably than bookmarks do. Annotations like highlights, sticky notes, and drawn markup are stored as objects attached directly to the page they appear on, the same way a hyperlink or a form field is, so copying that page into a new document carries the annotation along with it. What doesn't survive is anything that lives at the document level instead of the page level — a comment thread's reply chain in some viewers, or a reviewer list stored in the document's metadata rather than on individual annotations. If a reviewed draft is heading into a merge, open the result afterward and click through a few annotations to confirm they're still attached and still readable, the same way you'd check bookmarks and hyperlinks.

Can I merge a scanned PDF with a normal text-based PDF in the same file?

Yes, without any special handling. A merge tool operates on pages, not on what's inside them — a page built from real text and a page that's just a scanned image get copied into the combined document the same way. The result is a single PDF where some pages have selectable, searchable text and others don't, which is completely normal for documents assembled from mixed sources (a typed cover letter in front of a scanned signed contract, for instance). If you need every page to be searchable, that's a separate step — an OCR pass run on the merged file (or on the scanned source before merging) adds a text layer to the image-only pages without changing how they look.

Bottom Line

Every tool can combine PDFs. The difference is what happens to your documents while it does, and, as the modes and edge cases above show, what happens to the file's internal structure along the way.

For a recipe collection, use whatever's convenient. For anything with personal, financial, or legal content, pick a tool where the files never leave your device in the first place.

Merge your PDFs here, locally, in your browser.