What you can verify on this page
- Core PDF workflows process files locally in your browser.
- No document bytes are sent to a remote server for local tools.
- Behaviour can be inspected in your own browser network panel.
Do Online PDF Tools Upload Your Files?
Last reviewed: March 11, 2026
Many online PDF tools do upload files to remote servers because the conversion, compression, OCR, or page-editing step happens in cloud infrastructure. That means the provider can receive the document itself, plus any hidden metadata, embedded text, and file history that travels with it.
Plain.tools is built around local browser processing for core PDF workflows. The file stays on your device while the tool runs in-browser, which reduces exposure to third-party storage, server-side processing queues, and transfer paths you cannot easily inspect. This page shows how to verify that claim in your own browser rather than relying on marketing copy.
How to inspect quickly
- Open DevTools and switch to the Network tab.
- Filter by Fetch/XHR requests while running a tool.
- Confirm no request payload contains your PDF content.
Want deeper technical context? See verification guidance , review the editorial policy, or read the status-check methodology or inspect the public repository on GitHub.
Proof: No File Uploads
This is the fastest way to validate the core privacy claim on Plain Tools. Open one of the local PDF tools, keep the Network tab visible, and watch what happens when you add a file and run the action. For the standard local workflows, you should not see file bytes being sent in Fetch or XHR requests.
Example tool interaction
Example: open Merge PDF or Compress PDF, then drag in a sample document while the Network tab is filtered to Fetch and XHR. You may still see normal page assets or analytics, but you should not see a request carrying the actual file payload for the core local workflow.
No Fetch/XHR requests with file data
Simplified network log
Name Type Status Notes main.js script 200 app bundle plausible.js script 200 analytics favicon.ico other 200 static asset Result: no Fetch/XHR upload request containing file bytes
Try a tool and watch the Network tab.
The detailed checklist below expands this quick proof into a repeatable verification method you can run yourself in any modern browser.
How Most PDF Tools Work vs Local Processing
The main privacy difference is where the processing happens. Upload-based PDF tools move the file to remote servers first, while local processing keeps the document in the browser and performs the task on your device.
Most online PDF tools
- Upload the file to a server before the task can run.
- Rely on server-side queues and remote processing infrastructure.
- Require you to trust the provider's retention, access, and deletion policy.
Plain.tools local processing
- Runs core PDF workflows directly in your browser session.
- Keeps document bytes on your device during the main tool action.
- Makes the privacy claim easier to verify with the browser Network tab.
Frequently asked questions about PDF tool privacy
These are the common privacy questions behind PDF converter, compressor, and OCR searches. The answers below are rendered in the page HTML and mirrored in FAQ schema for search visibility.
Do PDF converters upload files?
Many online PDF converters do upload files to remote servers because the conversion runs in cloud infrastructure. Plain Tools core PDF workflows are built to process files locally in the browser instead.
Are online PDF tools safe?
Some are safer than others, but safety depends on architecture and handling practices. If a tool uploads your file for processing, you are trusting that provider with the document and any hidden data inside it.
Can websites see my documents when I convert a PDF?
Yes, if the website uploads the file to its servers for processing. With local browser processing, the site can run the workflow without sending the document bytes away during the core task.
Do PDF compressors store files?
Many upload-based PDF compressors temporarily process files on remote infrastructure, and some may log or retain them according to their own policies. Plain Tools core compression is designed to run on-device instead.
Is local PDF processing more secure?
Local processing is usually a stronger privacy default because the file stays on your device during the task. It reduces exposure to third-party storage, server logs, and cloud transfer paths, but you should still verify the behaviour in DevTools.
Verification First
We Dare You to Catch Us Uploading Your Files.
Every privacy claim we make is technically verifiable. Here's exactly how to check.
Step-by-Step Verification Guide
Tick each step as you complete it. Completed: 0/4
Annotated Network Check
Step 4 target state: no request carrying your PDF file bytes.
You can compare this against your own browser while processing a real document.
Claims Registry
Every claim below maps to a concrete, repeatable verification method.
| Claim | How to verify |
|---|---|
| Files never leave your device | Open DevTools > Network and inspect requests while running a tool. |
| No ad-tech trackers | Open DevTools > Sources and Network. You should only see the Plausible privacy-first analytics script, not ad/retargeting trackers. |
| Works offline after load | Load the app, enable Airplane mode, then run a tool. |
| No accounts required for free local tools | Use core tools (merge/split/compress/redact) without registration or login. |
| No cookies required | Open DevTools > Application > Cookies and verify tool usage does not depend on cookies. |
Open Source Challenge
Don't trust us? Read the code.
Share the Proof
Satisfied we're telling the truth? Share this page with someone who uses Smallpdf or Adobe.
Share text is prefilled with: “I just verified that Plain PDF tools genuinely don't upload my files. Here's how you can check too: plain.tools/verify-claims”
Want a deeper walkthrough? Use the full verification guide.
Open Technical WalkthroughTry local workflows yourself
The quickest way to validate claims is to run a real task while watching Network requests. Start with one of these tools.
Important limitation
AI features are explicitly opt-in and may send extracted text for processing. Core local tools are the no-upload workflows verified on this page.