PDFLite doesn't have a "no upload" policy — it has no server-side processing code at all for your files. There's nothing to configure not to happen; it was never built to send files anywhere.
Policy vs. architecture
Most tools: a policy
The file is uploaded, processed on a server, then the vendor promises to delete it. You're trusting a policy, enforced by people you can't see, on infrastructure you can't audit.
PDFLite: an architecture
The processing code runs in your browser tab, not on our servers. There's no upload endpoint for your file to hit — it's not a rule being followed, it's how the software is built.
What actually runs in your browser
Each tool — merge, split, redaction, signing, image and document conversion — uses established open-source JavaScript libraries, loaded once with the page and executed locally by your browser's own engine. They read your file's contents directly in memory and build the output the same way.
This is the same category of technology that runs spell-check or a print preview in your browser — ordinary client-side code, not a novel or unverifiable claim.
How to verify this yourself
You don't have to take our word for it — this is checkable in about a minute, without any technical background:
Open your browser's DevTools (F12, or right-click → Inspect) and go to the Network tab.
Load PDFLite, then merge a file. Watch the Network tab the whole time.
Look for a request carrying your file's data. There isn't one — only the page's own assets loaded once at the start.
What this does — and doesn't — guarantee
✓ What it means
Your file's contents are never transmitted to PDFLite or anyone else during merging, splitting, or conversion. Nothing to breach, subpoena, or misuse on our end — we simply never receive it.
✕ What it doesn't cover
Your own device's security (malware, an unlocked laptop), or browser extensions with broad permissions. Local processing removes one risk, not every risk.
Library names and versions may change over time as the tool is updated; the architecture principle — processing runs client-side, not on a PDFLite server — remains the design going forward.
See it for yourself — merge, split, or convert a file with nothing uploaded.
Try it free