Why does my browser tab freeze when I process a large PDF?

ClientPDF does all merging, splitting, rotating, reordering, compressing, and page-numbering inside your browser tab, using your device's own memory and CPU, because it never uploads the file to a server. A large file or a PDF with thousands of pages means the whole document has to be decoded and held in the tab's memory at once, which can slow the page down or, in extreme cases, exhaust the tab's memory and crash it.

Is this a bug in ClientPDF?

No — it's the direct tradeoff of the no-upload design. A server-side tool avoids this by doing the heavy lifting on a machine with more memory than your device, but that requires sending your file to that server first. ClientPDF has no server-side processing step at all, by design, so the ceiling on file size is set by your device rather than by a server.

How do I process a very large PDF without the tab freezing?

Split the file into smaller chunks first if you have another tool that can do that without loading the whole thing into memory at once, close other tabs and extensions to free up RAM, use a desktop machine rather than a phone or tablet, and give the tab a minute to finish rather than assuming it has crashed — large operations can take noticeably longer without any visible progress in between.

Why does my browser tab freeze or crash on a large PDF?

ClientPDF Guide · a 2-minute read

You dropped in a large PDF — maybe a few hundred megabytes, or a scanned document running into the thousands of pages — and the tab stopped responding, the fan spun up, or the page crashed outright. That's not a broken tool. It's the direct cost of a tool that never uploads your file anywhere.

No upload means no server doing the heavy lifting

Every tool on this site — merge, split, rotate, reorder, compress, page numbers — runs entirely inside your browser tab using pdf-lib, a JavaScript PDF library loaded from this page. There's no step where your file leaves the device, and there's no server picking up the actual work of decoding and rewriting the PDF. That's the whole privacy promise: nothing is uploaded, so there's nothing to worry about being stored, logged, or breached on someone else's server.

The tradeoff is that your device's memory and CPU are the only resources available for the job. A server-side PDF tool can throw a machine with tens of gigabytes of RAM at a huge file. A tab in your browser has to decode the whole document into memory using whatever the browser process has been allotted — usually a slice of your device's total RAM — and large or page-heavy PDFs can push past that limit.

Where this shows up in practice

A single PDF in the hundreds-of-megabytes range, often a scanned book or a design file exported with high-resolution images on every page.
A PDF with several thousand pages, where the page count itself — not just file size — makes the in-memory document structure large.
Merging many files at once in the merge tool, where every file gets loaded into memory at the same time before the combined document is produced.
Doing this on a phone or tablet, where the browser is typically allotted far less memory than on a desktop.

In each case the file itself is usually fine — it's the amount of work needed to hold the whole thing in memory at once that's the limiting factor, not anything specific to ClientPDF's processing logic.

How to work around it

Give it more time before assuming it crashed. A large file can take noticeably longer to process with no visible progress in between — the tab freezing briefly during the heaviest part of the work is expected, not necessarily a crash.
Close other tabs and extensions first. Browser memory is shared across everything open, and freeing it up before you start gives the PDF work more room.
Use a desktop or laptop rather than a phone or tablet if the file is large — desktop browsers are typically allotted significantly more memory per tab.
If you're merging many files, try merging them in two smaller batches and then merging the two results, rather than all of them in a single pass.
If a file is consistently too large to handle in a browser tab no matter what you try, that's the real ceiling of any purely client-side, no-upload tool — at that point a desktop PDF application, which isn't bound by browser memory limits, is the more appropriate tool for the job.

Try it yourself: most everyday PDFs — reports, scanned forms, exported documents under a hundred pages or so — process instantly with ClientPDF's tools, entirely on this device, with nothing ever uploaded.