PDF Converter Security: 3 Ways to Check for File Uploads

Contents
- Where does a PDF converter site process your files?
- Check 1: Does the job finish with the internet off?
- Check 2: What shows up in the DevTools Network tab?
- Check 3: How do you read the processing notice on a tool page?
- Which tools have to go through a server?
- How do I handle sensitive files like IDs and contracts?
- Summary
- Frequently asked questions
The only sure way to know whether a free PDF converter or image compressor site uploads your file to its server is to check in your browser instead of trusting what the site says. Open the tool page, cut off the internet, and see whether the job still finishes. Or open the Network tab in DevTools and see whether a transfer about the size of your file shows up.
Summary ① A tool that processes files inside the browser keeps working after you go offline once the page has loaded. A tool that sends files to a server fails when you disconnect. ② In the DevTools (F12) Network tab, a POST or PUT request appears right after you add a file, and if its size is close to the file size, that's an upload. A line starting with blob: is an address inside browser memory, not a transfer. ③ Public data lookups, web address checks, and downloaders have to go through a server by design. Image compression, PDF merging, and character counting can run in the browser alone.
Where does a PDF converter site process your files?
Online tools handle files in one of two ways. The screen looks the same either way — "choose a file → click a button → download" — so you can't tell them apart from the outside.
Browser processing. When you pick a file, the browser reads it into your computer's memory (File API). Images are redrawn onto a Canvas and saved, PDFs have their page structure edited by a JavaScript library, and videos are handled by a conversion engine ported with WebAssembly. All the computation happens on your device, and the result downloads straight to your device.
Server processing. The file goes to the site's server and the converted result comes back down. In that case, how long the file stays on the server depends on that site's policy. From the outside, the only thing you can check is the retention period written in the privacy policy.
The word "upload" on screen isn't a clue either. Our PDF merge screen below has an up-arrow icon too, but the file never goes to a server. That's why the three checks below are the reliable way to know.
Check 1: Does the job finish with the internet off?
This is the simplest method. A tool that has to send files to a server can't finish without a connection.
- Open the tool page and wait until the screen is fully loaded.
- Turn off Wi-Fi or switch on airplane mode. On Chrome for PC, you can also change "No throttling" in the DevTools Network tab to "Offline."
- Without reloading the page, add your file and run it as usual.
- If you get a result and the download works, the tool processes files inside your browser.
We ran the same test with our tools on November 16, 2026. After the page loaded, we switched the browser to offline and added two sample PDFs. The merge finished and the download button appeared.

A tool that goes through a server fails under the same conditions. A business registration number lookup has to send the number you type to the National Tax Service API, so offline it shows an error instead of a result.

One thing to watch for. Tools that download an AI model or conversion engine the first time you run them — like AI background removal or video compression — can fail offline even though they never upload your file. For those, use Check 2 and look at which direction the request goes.
Check 2: What shows up in the DevTools Network tab?
On Chrome or Edge for PC, you can see the requests the browser records. It takes a bit more work than the offline test, but it also shows what is going where.
- On the tool page, press F12 (Cmd+Option+I on Mac) to open DevTools and select the "Network" tab.
- Turn on "Preserve log" so the record isn't cleared when you move to the result screen, then empty the list with the clear button.
- Add a file, run it, and look at the new lines that appear.
- Click a line whose method is POST or PUT and check whether the file name shows in the Payload tab and whether content-length under Headers is close to the file size.
Here's what we recorded for two of our tools on the same day. These are the requests captured from the moment we added the file until 5 seconds after the result appeared.
| Tool | What we added | Requests recorded | Verdict |
|---|---|---|---|
| Image compression | 3.08MB PNG photo | 2 blob: addresses, 0 server requests | Browser processing |
| Business registration number lookup | 10-digit number | 1 POST, 23-byte body | Goes through server |
The two blob: lines in image compression are addresses the browser creates to point to the image in memory. They show in the Network tab, but they aren't transfers going out. The 23 bytes in the business registration lookup is the size of one typed number, which reveals exactly what is being sent.
If the page carries ads or visitor analytics, those requests can be mixed into the list too. The test that matters is whether a request about the size of your file goes out at the moment you add it.
Check 3: How do you read the processing notice on a tool page?
Last, read what the site says about itself. "Processed in your browser" or "never sent to a server" is a claim that it doesn't upload. "Uploaded files are deleted after a few hours" means the file does go to a server.
Keep in mind that a notice is just the site's claim, so check it against methods 1 and 2. Our own site once had "processed in your browser" on lookup tools that actually go through a server. We found it while reviewing the live screens and split the wording by tool.
As of November 16, 2026, out of 768 tools, the 32 that go through a server (9 public data lookups, 19 media downloaders, 3 web address checks, 1 IP location lookup) and the 2 where the browser asks an outside service directly each carry different notices. Every other tool shows a "100% processed in your browser" notice right below it, like this.

Free · no install, runs in your browser · each tool explains how it processes files
Which tools have to go through a server?
Not every tool can run inside the browser. The nature of the job tells you which side it falls on.
| Task | Where it runs | Why | Our tools |
|---|---|---|---|
| Image compression, resizing, EXIF removal | Browser | Redrawn onto a Canvas and saved | Image Compressor, Image Resizer, EXIF Remover |
| PDF merge, split, image → PDF | Browser | A library edits the PDF structure | Merge PDF, Split PDF, Image → PDF |
| Text work such as character counting | Browser | Only the characters you typed are counted | Character Counter |
| AI background removal, video compression | Browser (engine is downloaded) | Model and engine are downloaded and run on your device | Background Remover, Video Compressor |
| Public data lookups | Server | The server holds the agency API key | Business Registration Number Lookup, Live Exchange Rates |
| Web address checks, downloaders | Server | The browser can't read another site's response directly | Share Card Preview, All-in-One Media Downloader |
Public data lookups have to be requested with a key issued by the agency, and that key can't be exposed in the browser, so the server asks on your behalf. Tools that read a web address usually go through a server because browser security rules (CORS) often stop a page from reading another site's response directly.
What you send to these tools is mostly a number or a web address. Compression and conversion work on your own files runs perfectly well in browser-based tools.
How do I handle sensitive files like IDs and contracts?
The more sensitive the file, the more important it is to follow these checks in order.
- Check where the file is processed first, using methods 1 and 2. If it's a browser-based tool, your file never leaves your device.
- If you have to use a site that processes files on its servers, read its privacy policy. Check whether it states how long files are kept, when they are deleted, and which company and country process them.
- Limit what you send. Extract only the pages you need with Split PDF, and cover anything that shouldn't be visible in photos or screenshots with Pixelate before you send them.
- Remove metadata from photos. EXIF data in smartphone photos can include the device used to take the picture and GPS location, so you can remove it with Remove EXIF before uploading.
Once a file is uploaded to a server, there is no way to confirm from the outside that it is actually deleted. That makes checking where processing happens before you upload the most reliable step.
Summary
- The screen layout or the word "Upload" won't tell you where processing happens.
- If the page loads, you disconnect from the internet, and the task still finishes, it's a browser-based tool.
- In the Network tab, if a POST or PUT request the size of the file appears as soon as you add the file, it's an upload. A blob: line is not a transfer.
- Trust on-screen guidance only after you've checked it against methods 1 and 2.
Free · no install, runs in your browser · each tool explains how it processes files
Frequently asked questions
Does incognito mode keep my file from being uploaded?
No. Incognito mode keeps your browsing history and cookies from being saved on your device. A site sends your file to its server the same way it does in a normal window.
Does the lock icon (HTTPS) in the address bar mean a site is safe?
HTTPS means the content is encrypted in transit. It doesn't tell you whether your file goes to a server or how long it stays there. You still need to check where processing happens separately with methods 1 and 2.
How can I check this on a smartphone?
Method 1 works the same way. Open the tool page, turn on airplane mode, and try adding a file. Developer tools are hard to open directly in a phone browser, so for a closer look, it's easier to use method 2 on a PC.
If a tool fails the offline test, does that mean it always uploads files?
Not necessarily. A tool that has to download an AI model or conversion engine the first time you use it can fail offline even without uploading your file. You can tell the difference in the Network tab by checking whether the request is a download (GET) or an upload (POST or PUT).
Can I use the tools in other languages too?
Except for two tools made only for Korean law, the free tools page is available in English, Japanese, German, Spanish, French, Portuguese, Italian, and Indonesian as well as Korean (as of November 16, 2026, nine languages in total). The note below each tool about how files are processed is also shown in each language.
This article was adapted from our Korean original. Read the Korean original