What “runs in your browser” actually means
Most PDF sites upload your document to a server they own. Here is what the alternative is, and how to check the claim yourself.
Most free PDF sites work the same way. You pick a file, it uploads to a server, the server does the work, you download the result. It is invisible, it takes a few seconds, and it means your document — the contract, the medical letter, the passport scan — has been copied onto a machine you do not own.
What actually happens to an uploaded file
Usually nothing sinister. It sits in temporary storage, gets processed, and is deleted on some schedule the privacy policy describes in the vaguest terms available. But "deleted within an hour" is a promise, not a mechanism. You cannot verify it. It depends on the company's retention policy, its backups, its staff, its jurisdiction, and its security — and on that company still existing next year.
The alternative
Browsers got good. Everything most people do to a PDF — merging, splitting, rotating, compressing, converting to images — is work a browser can do on its own, using JavaScript running inside the tab you already have open. The file is read from your disk into memory, changed, and handed back as a download. It never goes anywhere.
That is what BabaPDF is. There is no upload endpoint, no processing server, and no storage bucket — not as a policy, but because the site is static files and there is nowhere to send anything.
Do not take our word for it — check
This is the useful part, and it applies to any tool making this claim, including ours. Open your browser's developer tools, go to the Network tab, and use the thing. Every request the page makes is listed there. If your file were being uploaded you would see it: a POST request, megabytes in size, going to some server. If the claim is true, you will see nothing of the kind.
Try the same on a site that promises "secure processing" and "files deleted after one hour". You will watch your document leave. Both statements can be true at once — it can be encrypted in transit and deleted on schedule and still be a copy of your file on someone else's computer.
What it also buys you
- No upload wait. A 40MB file starts instantly, because it does not travel.
- No accounts, because there is nothing to store or bill for.
- No size caps set by someone's bandwidth budget — the limit is your own memory.
- It works offline once the page has loaded, which is the clearest proof the processing is local.
Where it stops
Being honest about the edges: some jobs genuinely need a server. Converting a live web page to PDF means fetching that page, and browsers are not allowed to fetch arbitrary sites on your behalf. Very large files are bounded by your device rather than a datacentre. And OCR-quality text recognition is still better server-side. When a browser cannot do something properly, the right answer is to say so, not to quietly upload your file.
Merge PDFCombine multiple PDFs into one file, in the order you choose.