How to check if a PDF tool is uploading your files

Most online PDF tools look identical on the surface. You drop in a file, click a button, and get the result back in seconds. Whether your document traveled to a server in that window is not something the interface tells you. It just happens quietly in the background.

Here are four checks you can run yourself, right now, without any technical background required.

1. Open the Network tab while you process a file

Every browser keeps a log of every request a page makes to the outside world. To see it:

1. Open the PDF tool in Chrome, Firefox, or Edge.
2. Press F12, or right-click anywhere and choose Inspect.
3. Click the Network tab at the top of the panel that opens.
4. Drop in a PDF file and start processing it.
5. Watch what appears in the list.

If you see POST requests going to an external domain during processing, your file is being uploaded. If the list stays quiet or only shows requests for scripts, fonts, and the tool's own assets, the work is happening locally in your browser.

You don't need to understand every entry in the list. Just look for anything that sends data outward while the processing is happening.

2. Try it while offline

This is the simplest test of all. Load the tool and wait for the page to finish loading. Then disconnect from Wi-Fi or unplug the ethernet cable. Now try to process a PDF.

A tool that runs locally will still work. A server-dependent tool will fail or hang, because the upload can't complete without a connection.

Some tools load entirely from cache and won't obviously fail. In that case, the Network tab test is more reliable.

3. Read the privacy policy for the right phrases

Privacy policies are long, but you're only looking for a few specific things. Search the page for words like "store," "retain," "server," or "upload."

• Phrases like "your files are processed on our servers" or "we store your document for X days" mean the file is going somewhere.
• Phrases like "all processing happens in your browser" or "your file never leaves your device" mean it doesn't.
• If the policy doesn't mention file handling at all, that's worth treating as a yellow flag.

4. Watch the progress bar and URL during processing

A tool that uploads your file usually shows a progress bar that tracks upload speed, not processing speed. On a fast connection it moves quickly. On a slow connection it crawls, even if the task is simple.

A local tool processes at CPU speed, which is consistent regardless of your network. If the speed of your internet changes how fast the tool works, the file is being sent somewhere.

Also watch the URL bar. Some tools redirect you to a result page after processing, something like /result/abc123 or /download/xyz. That address usually points to where your file was stored temporarily on their server.

When uploading is actually fine

None of this means server-side tools are bad. For very large files, optical character recognition on big batches, or conversions that need specialized software, a backend makes sense. The issue is when a simple operation sends your file to a server without telling you clearly.

For the tasks most people do every day, compressing, merging, splitting, rotating, there is no technical reason the work has to leave your device. It can all run in your browser.

PDFShore is built on that model. Every tool processes your file in the browser. If you want to verify it yourself, open the Network tab, drop in a PDF, and watch. Nothing goes out.