Skip to main content
Free guides — written by the mergepdf.dev team

PDF Guides & Tutorials — Learn How It All Works

Everything you need to know about merging PDFs privately in your browser. No fluff, no filler — just clear explanations of how the tool works and how to get the most out of it.

These guides cover the technical side of browser-based PDF merging, step-by-step instructions for different use cases, and answers to the questions we get asked most. All guides are written by the mergepdf.dev team and kept up to date.

📋

How to Merge PDF Without Uploading

Step-by-step guide to combining PDFs privately in your browser. Covers desktop, iPhone, Android, and offline use.

Read guide
⚙️

How Browser-Based PDF Merging Works

Technical explanation of the File API, pdf-lib, and why files never leave your device. Includes a DevTools verification walkthrough.

Read guide

What these guides cover

How to Merge PDF Without Uploading is the practical guide. It walks you through the four steps to merge PDFs in your browser, explains how to verify nothing is being uploaded, covers mobile (iPhone and Android), and answers the most common questions. If you just want to get something done, start there.

How Browser-Based PDF Merging Works is the technical guide. It explains what actually happens when you merge PDFs — the File API reads files into memory, pdf-lib processes them locally, and a Blob download delivers the result. It also explains why local processing is safer than upload-based tools, and how to verify it yourself using browser DevTools. If you're security-conscious or just curious, that's the one to read.

Quick answers to common questions

Why don't PDF tools just work in the browser without uploading?

Most PDF tools were built before browser JavaScript was powerful enough to handle binary file processing. Server-side processing was the only option. Today, libraries like pdf-lib make it possible to read, modify, and create PDFs entirely in JavaScript — no server required. Most tools haven't caught up because rebuilding their architecture is expensive. We built this from scratch with local processing as the foundation.

Is browser-based PDF merging as reliable as server-based tools?

For merging, yes. The pdf-lib library handles the same PDF specification that server-side tools use. Pages are copied exactly — no re-rendering, no quality loss, no format changes. The main difference is that processing speed depends on your device rather than a server. On a modern computer, this is actually faster because there's no upload/download wait time.

What's the difference between "no upload" and "secure upload"?

"Secure upload" means your files are encrypted in transit to a server. "No upload" means your files never leave your device at all. These are fundamentally different security models. With no upload, there's no server to breach, no retention policy to trust, no legal request that could expose your files. For sensitive documents, no upload is the stronger guarantee.

Can I trust a browser to handle my PDF files?

Yes. Modern browsers are sandboxed environments with strict security controls. The File API — which is how this tool reads your PDFs — only gives JavaScript access to files you explicitly select. The browser can't read other files on your device, can't access your file system without permission, and can't send data without making a network request (which you can monitor in DevTools). Browser-based processing is auditable in a way that server-side processing isn't.

PDF merging by device and platform

The core tool works the same everywhere, but each platform has its own quirks. These pages cover platform-specific tips:

PDF merging by use case

Related tools

These guides support the tools on this site. Depending on your situation, one of these pages might be exactly what you need:

About these guides

Written by the mergepdf.dev team. We built this tool because we needed a PDF merger that didn't upload files to a server — and we couldn't find one that was both private and easy to use. These guides explain the decisions we made and how the technology works.

All guides are kept up to date. If something is wrong or unclear, let us know.