Merge PDFs Privately: No Upload, No Adobe [2026 Guide]
Every free online PDF merger makes the same unspoken tradeoff: you get the tool for free, and they get your documents routed through their server for a few hours. For invoices, contracts, and tax returns this is unacceptable. Modern browsers can merge PDFs locally — no upload, no Adobe subscription, no signup.
Table of Contents
The privacy problem with online PDF mergers
Search “merge PDF online” and the top ten results are all variations of the same architecture: you drop files onto a web form, the files POST to a server, a backend process merges them, the result comes back as a download link. The UX looks instant. The privacy footprint is not.
Every one of those servers holds your documents for at least a few minutes, sometimes hours. Most privacy policies promise deletion after 1-2 hours or “when processing completes”. That is probably true for normal traffic. It is not verifiable. It does not help you if a server is compromised during the window your file is there. It does not help you if the vendor is subpoenaed. It does not help you if the vendor is secretly training a machine learning model on the documents flowing through.
For most casual use this is fine. Combining two photos of a grocery receipt — who cares. But PDF is the universal format for sensitive documents: invoices with business details, contracts with signatures, tax returns, medical records, bank statements, legal filings. Routing these through a third-party server violates internal security policies at almost every company. IT usually blocks the usage anyway.
How browser-based PDF merge works
Modern browsers are full application runtimes. They can read files from your disk via the File API, parse binary formats in JavaScript, and download the result as a Blob — without ever sending the bytes over the network.
SammaPix PDF Merge uses pdf-lib, an open-source PDF manipulation library written in TypeScript. The library implements the PDF specification well enough to:
- Parse a PDF byte stream into a document object (pages, fonts, metadata, content streams).
- Copy pages across documents while preserving shared resources (fonts, images).
- Serialize the merged document back to PDF bytes.
- Return the bytes as a Blob for download.
The entire operation happens inside your browser tab's JavaScript sandbox. Open DevTools → Network during a merge and you will see zero outbound requests that contain your PDF data. The only traffic is the initial page load (static code) and optional analytics pixels that contain no file content. Read the tool source yourself if you want certainty — pdf-lib is MIT-licensed on GitHub.
How major PDF tools handle your files
A quick audit of top-ranked PDF mergers in April 2026, based on their published privacy policies and visible network traffic during a test merge:
| Tool | Upload? | Claimed retention |
|---|---|---|
| iLovePDF | Yes — server-side | “A few hours” |
| SmallPDF | Yes — server-side | 1 hour (policy) |
| PDF24 | Yes — server-side | “Short time”, unspecified |
| Adobe online | Yes — Adobe cloud | Until deletion (manual) |
| PDFsam desktop | No — runs locally | N/A (open source, Java) |
| SammaPix PDF Merge | No — browser only | N/A (no transmission) |
The four server-based services are generally reputable and their claims are probably honest. The point is not that they are evil — it is that you cannot verify the claims and you do not have to make the tradeoff at all. Browser-based tools remove the question entirely.
When PDF privacy matters (the real-world cases)
Privacy concerns are not paranoia — they map to concrete, common situations:
- Freelance invoicing. Your invoices contain client names, rates, and business addresses. Not catastrophic if leaked, but clients often ask you to sign NDAs that technically include “do not transmit to third parties”.
- Employment contracts and offers. Signed versions contain full names, SSN, salary details, home addresses. Routinely merged into one document when applying for mortgages, visas, or apartment rentals.
- Medical records. Combining records from multiple providers for a specialist consultation. HIPAA in the US and GDPR in the EU both put meaningful liability on transmission to unqualified third parties.
- Tax returns. Year-end packages combining W2s, 1099s, and receipts. Often contain full financial fingerprints.
- Legal filings. Combining exhibits for court submissions. Many jurisdictions require attorney-client privileged material to never transit third-party cloud services.
For broader privacy patterns in image and document tools read our browser-based image tools privacy guide.
Encrypted and password-protected PDFs
PDF has two common “encryption” modes that often get conflated:
- Encrypted-for-viewing: the file is technically encrypted (permissions flag set) but the viewing password is blank. Adobe Reader opens it without prompting. Most office-generated PDFs are in this category.
- Password-required: genuinely locked, requires the password to render.
SammaPix PDF Merge loads PDFs with ignoreEncryption: true which handles case 1 transparently — the encrypted-for-viewing flag is bypassed and the content is readable. Case 2 requires the password to decrypt before merging; PDF Merge does not currently prompt for passwords, so decrypt the source in your OS PDF viewer or Adobe Reader first.
What gets preserved in the merge
| Feature | Preserved? |
|---|---|
| Text content | Yes, pixel-perfect |
| Images and graphics | Yes, pixel-perfect |
| Fonts (embedded and non-embedded) | Yes |
| Hyperlinks | Yes |
| Form fields (fillable) | Yes, mostly |
| Annotations and comments | Partial — simple ones preserved |
| Digital signatures | Preserved but invalidated (merge changes bytes) |
| Document-level bookmarks | Not preserved (known limitation) |
| Attachments (files embedded in PDF) | Partial |
For bookmark-heavy workflows (long legal packs, technical manuals) a desktop tool like Adobe Acrobat or PDFsam is better. For invoicing, contract packs, and most office use cases the browser-based merge handles everything you need.
The merge workflow step by step
- Open SammaPix PDF Merge. Any modern browser works.
- Drop up to 10 PDFs on the free plan (50 on Pro). 100 MB per file max.
- Drag rows up or down to set the final order. Click the trash icon to remove files you do not want.
- Click Merge N PDFs. Progress bar shows page-by-page combine.
- Download the merged PDF. Filename defaults to
sammapix-merged-N-files.pdf.
Need to build a PDF from images first? Use JPG to PDF first, then pipe into PDF Merge. For reverse direction use PDF to Image.
How to verify no upload happened
Do not take our word for it. Verify yourself:
- Open Chrome or Firefox DevTools (right-click → Inspect, or F12).
- Go to the Network tab.
- Check Preserve log so entries persist across page changes.
- Load
/tools/pdf-mergeand clear the log. - Drop your PDFs and run the merge. Watch the Network tab.
- No requests with your PDF bytes as payload. The only entries will be static assets (JS, CSS, images), or at most a small analytics beacon with zero file content.
Repeat this check on any privacy claim, from any vendor. It is the only way to confirm a tool actually does what it says.
Offline alternatives if you need desktop
For larger batches, bookmark-preserving merges, or air-gapped environments, these desktop tools run fully offline:
- PDFsam Basic — open source Java app, Windows/Mac/Linux, preserves bookmarks, no file size limit.
- pdftk — command-line tool for Linux/Mac, scriptable, preserves everything.
- Preview (macOS) — built-in, drag pages between PDFs in thumbnails view.
- Adobe Acrobat Pro — paid, full feature set, industry standard.
For most day-to-day merging the browser-based option wins on speed and convenience without giving up privacy.
Free browser-based PDF tools
SammaPix runs three complementary PDF tools, all client-side via pdf-lib:
| Goal | Tool | Limits |
|---|---|---|
| Merge multiple PDFs | PDF Merge | 10 files / 100 MB free |
| Build PDF from images | JPG to PDF | 20 images / batch |
| Extract images from PDF | PDF to Image | Any page count |
Full toolbox: SammaPix homepage — 35 free tools, all browser-based.
FAQ
Do most free PDF mergers upload my files to a server?
Yes — most of them. iLovePDF, SmallPDF, PDF24, and the majority of search-top PDF tools route uploads through their servers. Browser-based tools like SammaPix PDF Merge run locally via pdf-lib and never transmit your files.
Is merging PDFs in the browser secure for sensitive documents?
Yes — provably more secure than server-based alternatives. The merge runs inside your browser tab using pdf-lib. Nothing is sent over the network. Verify by opening DevTools → Network tab during a merge: zero outbound requests with your PDFs.
How does the pdf-lib library handle encrypted PDFs?
SammaPix loads PDFs with ignoreEncryption:true which handles encrypted-for-viewing PDFs transparently. Password-required PDFs must be decrypted first — do not merge PDFs you are not authorized to open.
Can I reorder PDFs before merging?
Yes. Drag rows up or down after upload. Remove files with the trash icon. The merged output follows the on-screen order.
What is the file size limit for browser-based PDF merge?
Up to 100 MB per file, 10 files per batch on the free plan (50 on Pro). The hard limit is your browser memory.
Does the merged PDF preserve bookmarks, form fields, and annotations?
Text, images, page layout, and most form fields are preserved cleanly. Document-level bookmarks are a known limitation of client-side PDF libraries. For bookmark-heavy workflows use Adobe Acrobat or PDFsam desktop.
