About mergepdf.dev

The moment that started all of this

A few years ago, a colleague needed to combine three PDF files before a client call. Nothing complicated — just a cover letter, a proposal, and a terms sheet. He grabbed the first "free PDF merge" result on Google, dragged his files in, and got the merged document in about ten seconds. Done and dusted.

Then, eight days later, an email landed in his inbox. The tool's parent company had suffered a security incident. His files — which included the client's full legal name, address, and payment terms — had been sitting on their servers, unencrypted, the entire time. Their promise of "files deleted after one hour" turned out to be more of a suggestion than a policy.

It was such an ordinary thing to do — combining a few documents — and it had turned into a genuinely uncomfortable conversation with a client about data exposure. We kept thinking: why does a task this simple require trusting a stranger with your private information? So we decided to build something where that question doesn't even come up.

What we actually made (and what it doesn't do)

mergepdf.dev is a web page. That's it — one page, with some very clever JavaScript running behind it. When you pick PDF files, your browser reads them directly from your hard drive into its own memory. A library called pdf-lib then stitches the pages together, and your browser hands you the finished file. No server is involved at any point.

Here's what that means in practice: we structurally cannot access your documents. Not "we choose not to" — we literally have no mechanism to receive them. There's no upload endpoint. No API that accepts files. No backend process waiting for data. If our site got compromised tomorrow, the worst an attacker could do is change the CSS. Your documents would still be safe on your machine, untouched.

You don't have to take our word for it, either. Open DevTools (press F12), click the Network tab, and merge a few PDFs. You'll see zero outgoing requests. Just the initial page load and then... nothing. It's a nice feeling, actually — a web tool that does exactly what it claims and nothing more.

What sets this apart

Standing on the shoulders of open source

None of this would exist without pdf-lib, an MIT-licensed JavaScript library created by Andrew Dillon. It's the engine that makes browser-based PDF manipulation possible — reading the internal structure of PDFs, copying pages between documents, and serializing the result back into valid PDF format. All inside a browser tab.

Open source means you can read every line of the code that handles your documents. There are no black boxes, no proprietary processing steps, no "just trust us" moments. If you're the kind of person who reads the ingredients list before buying cereal, you'll appreciate that everything here is auditable. For a deep dive into how the processing actually works, our technical guide walks through every step.

The principles we run by

Privacy as architecture, not marketing

We didn't slap a padlock emoji on a normal upload tool and call it "secure." The architecture itself — client-side JavaScript, static hosting, no backend API — makes it physically impossible for us to see your files. That's not a feature. That's a design constraint we chose on purpose. Learn more about how we handle (or rather, don't handle) your data in our privacy policy.

Transparent about what we do measure

We run Google Analytics to understand which pages people visit and how they interact with the tool — things like "did someone successfully merge files?" or "which device/browser combinations work best?" We don't track what's in your documents (we can't — remember, they stay on your machine). Analytics helps us decide where to improve the experience. We'd rather be upfront about this than pretend we measure nothing.

Deliberately simple

We've been tempted to add PDF splitting, page rotation, annotation tools, watermark removal — the whole kitchen sink. But the moment a tool tries to do everything, it gets confusing. Right now, you can open the homepage, merge some PDFs, and be done in under 15 seconds. We'd like to keep that feeling.

Funded honestly

Non-intrusive ads keep the hosting bills paid. We've never sold data (we don't have any to sell). There's no "premium tier" dangling features behind a paywall. If the tool is useful and you let the ads load, that's genuinely all we need.

Under the hood (for the curious)

If you're a developer or just someone who likes knowing how things are built:

• Frontend: Vanilla JavaScript — no React, no Vue, no framework overhead. Fast, lean, auditable.
• PDF engine: pdf-lib 1.17.1, running inside a Web Worker so the UI stays responsive during large merges
• Styling: Hand-written CSS with custom properties (variables). No Tailwind, no Bootstrap.
• Fonts: Plus Jakarta Sans & Inter from Google Fonts, loaded asynchronously to avoid blocking render
• Hosting: Static files on a CDN — there is no application server, no database, no backend whatsoever
• Offline support: Service Worker (PWA) pre-caches all assets. Installable on mobile home screens.
• File handling: GB-scale support via streaming reads and chunked page copying to keep memory usage reasonable

What we're working on next

The roadmap is short and intentional. Everything keeps the same core promise: your documents stay on your device.

• Page-level previews: See thumbnail previews of every page before you merge, so you can catch mistakes early
• Individual page rotation: Rotate specific pages (90°, 180°, 270°) right in the merge interface — no separate tool needed
• PDF splitting: A companion tool to break one PDF into separate files. Same privacy architecture, same simplicity.
• Smart compression: Optionally reduce file size during the merge, especially useful for image-heavy PDFs
• Dark mode: For the late-night document wranglers. Your eyes will thank us.
• Batch filename control: Custom naming rules for the output file instead of just "[first-file]-merged.pdf"

Got a feature you'd love to see? Drop us a note. The best ideas so far have come from people actually using the tool.

Who uses this (and for what)

We hear from people in all sorts of situations:

• Freelancers combining invoices and contracts for clients on tight deadlines
• Students merging assignment parts before a Canvas or Turnitin upload
• Lawyers who can't risk client documents passing through a third-party server
• Travelers who need to combine booking confirmations and itineraries without Wi-Fi
• Healthcare workers handling patient referrals and lab results that fall under HIPAA
• Parents putting together school enrollment packets at 11pm the night before they're due
• Small business owners packaging proposals with pricing sheets and case studies

Whether you're dealing with sensitive legal documents or just organizing vacation photos into a single PDF for the family group chat — the tool works the same way. Pick files, arrange them, merge, done.

Say hello (or report a bug)

Found something that's broken? Have a question we haven't answered? Or maybe you just want to tell us the tool saved you from buying $18 in-flight Wi-Fi to merge two PDFs before a meeting? Whatever it is — we'd love to hear from you.

Help us keep the lights on

mergepdf.dev has been free since day one, and it'll stay that way. If you've found it useful, the most impactful things you can do:

• Send the link to a coworker or friend who merges PDFs regularly
• Mention it in a blog post, forum thread, or social media if it fits naturally
• Tell us what's working and what isn't — honest feedback makes the tool better
• Let the ads load (they're minimal, we promise — no pop-ups, no interstitials)

Thanks for being here. Seriously.