Merge PDF — Multiple Files at Once

The order shown on screen is the order used. Operating systems sort files in ways that rarely match what you intended — "file10" often lands before "file2" — so always check the list rather than trusting the order they arrived in.

Each file can be up to 100 MB, and the 30-file limit is about what a browser tab can hold comfortably rather than a commercial restriction. If you need more, process in batches and then combine the results; the outcome is identical.

For very large sets, working in groups is more reliable than pushing a single run to the limit. Twenty files in two batches of ten will complete comfortably on hardware where one batch of twenty might strain memory, and nothing about the final document differs.

When you press merge, each file is read into memory as an array of bytes and parsed with pdf-lib, an open-source PDF library that runs entirely in JavaScript. The tool creates an empty destination document and then copies page objects out of each source document into it, in the order you set on screen.

Copying at the object level is what preserves quality. A page's text runs, embedded fonts, images and vector instructions are transferred as-is rather than being flattened into a picture. Rotation, when you apply it, is written as a page attribute on top of whatever rotation the page already carried, so a page that was already 90 degrees out and gets another 90 ends up at 180 rather than snapping back to zero.

Your files are not uploaded. When you add a PDF file, your browser reads it from your device into the memory of the tab you are looking at, and the merge pdf operation runs there using your own processor. Nothing is transmitted to any server at any point.

That means there is no file for anyone to store, no retention policy to trust, and no deletion schedule to take on faith. The document exists only in the memory of an open browser tab, and it is released the moment you close it, reload the page, or press start over.

The site uses standard anonymous analytics to count page views and how often each tool is used. Those events record which tool ran and whether it succeeded — never a file name, never file contents, and never anything that could identify a document or the person processing it.

No account is required, so no personal information is collected. There is no profile, no history and nothing tied to an identity, because no identity was ever created.

The strongest security property this tool has is structural: your file never travels anywhere, so there is no transmission to intercept and no server-side copy to breach. This is not a policy that could change — it is a consequence of where the code runs.

You can verify it in about thirty seconds. Open your browser's developer tools with F12, select the Network tab, and use the tool. You will see the page's scripts load — including the PDF libraries, which are fetched on demand the first time a tool runs — and then nothing further. No request carrying your document is ever made.

For a stronger test, disconnect from the network once the page has loaded. The tool will keep working exactly as before, which is only possible because nothing is being sent.

Uploaded files are validated in the browser before anything runs: the extension must match what the tool accepts, the file must not be empty, and it must be within the size limit. Malformed documents produce a clear error and a retry option rather than a silent failure.

Being clear about limits is more useful than a feature list that quietly omits them. Bookmarks, interactive form fields and document-level JavaScript are not carried into the merged file, and encrypted PDFs must be unlocked in your own reader first.

If you need capabilities beyond that — redaction, PDF/A conformance, OCR, or scripted batch processing across thousands of documents — dedicated desktop software genuinely earns its licence fee, and this is not trying to replace it. For the specific job of producing a merged PDF, everything you need is on this page.