PDF tools that don’t upload your files — verified, not claimed
Many PDF sites say “secure” or “private”, but the only way to know where processing happens is to watch the network. We did exactly that: in recorded walkthroughs we processed files on the five biggest PDF sites with DevTools open. All five uploaded the file to their servers. That is not an accusation — server-side processing is a legitimate architecture with honest deletion policies — but if your requirement is “the file must not leave my device”, you need browser-local processing, and you should verify it yourself.
iLovePDF
major PDF sites
Uploads observed (api112.ilovepdf.com/v1/upload)
Paplume
Local tools run entirely in your browser — no file upload (verify in DevTools → Network)
Smallpdf
major PDF sites
Uploads observed (pluto.smallpdf.com → cloud storage)
Paplume
Local tools run entirely in your browser — no file upload (verify in DevTools → Network)
PDF24
major PDF sites
Uploads observed (filetools*.pdf24.org); ad-funded, genuinely free
Paplume
Local tools run entirely in your browser — no file upload (verify in DevTools → Network)
Sejda
major PDF sites
Uploads observed (/api/files/upload); auto-deleted after 2 hours per their policy
Paplume
Local tools run entirely in your browser — no file upload (verify in DevTools → Network)
Adobe Acrobat online
major PDF sites
Uploads observed (Adobe blobstore → unity.adobe.io)
Paplume
Local tools run entirely in your browser — no file upload (verify in DevTools → Network)
| major PDF sites | Paplume | |
|---|---|---|
| iLovePDF | Uploads observed (api112.ilovepdf.com/v1/upload) | Local tools run entirely in your browser — no file upload (verify in DevTools → Network) |
| Smallpdf | Uploads observed (pluto.smallpdf.com → cloud storage) | Local tools run entirely in your browser — no file upload (verify in DevTools → Network) |
| PDF24 | Uploads observed (filetools*.pdf24.org); ad-funded, genuinely free | Local tools run entirely in your browser — no file upload (verify in DevTools → Network) |
| Sejda | Uploads observed (/api/files/upload); auto-deleted after 2 hours per their policy | Local tools run entirely in your browser — no file upload (verify in DevTools → Network) |
| Adobe Acrobat online | Uploads observed (Adobe blobstore → unity.adobe.io) | Local tools run entirely in your browser — no file upload (verify in DevTools → Network) |
Competitor facts verified in our own hands-on walkthrough on 2026-07-31. Prices and limits change over time — always check the competitor’s current pages. We state only what we observed; no ratings or scores are invented.
The honest part
Two honest caveats. First: Paplume’s AI features (translate/summarize/chat) do send extracted text — not your PDF file — to an AI service, and say so on the page; only the local tools are fully local. Second: browser-local processing has limits too — very large files are constrained by your device’s memory, where a server farm is not. Each tool page states its limits.
Try it yourself
Free during Beta · no sign-up · no watermark · processed locally in your browser.
FAQ
How do I verify any PDF tool myself?
Open DevTools (F12) → Network tab, clear it, then process a file. If you see a request uploading your file’s megabytes, processing is server-side. On Paplume local tools you will see no file upload — try it.
How can I check that Paplume really does not upload my file?
Open your browser DevTools → Network tab, then process a PDF with any local tool. You will not see a single file-upload request — processing happens in your browser via WebAssembly.
Is server-side processing unsafe?
Not inherently — reputable sites publish deletion policies (Sejda even prints its 2-hour deletion under the upload button). The difference is trust versus verification: with local processing there is no policy to trust, because the file never leaves your device.