The Wi-Fi Test: How to Know If a File Converter Is Really Private
Disconnect your Wi-Fi. Try the conversion. If it works, your files never left your device.
Try it now
Step 1
Turn off your Wi-Fi
Step 2
Convert a file below
Step 3
Did it work? Then your file never left your device.
Why this matters
Most online file converters work by uploading your file to a remote server. The server processes it, sends back the result, and (in theory) deletes the original. In practice, you have no way to verify what happens after the upload. Your file may be stored, logged, analyzed, or shared with third-party infrastructure providers.
Privacy badges, "secure" labels, and marketing copy are not verifiable from the outside. A site can claim files are deleted immediately while retaining copies for training data, analytics, or simply because the deletion policy is never enforced. Even well-intentioned services rely on cloud providers where file handling depends on configurations the end user cannot inspect.
In 2025, the FBI issued a public warning about free online file converters being used to distribute malware — tools that appear to convert your file while quietly extracting sensitive data or installing malicious code. The warning highlighted a real gap: users have no practical way to distinguish a safe converter from a dangerous one based on its appearance alone. We covered this in detail in our analysis of the FBI warning and converter privacy risks.
The Wi-Fi test cuts through all of this. It is the simplest, most accessible way for anyone — regardless of technical skill — to verify whether a file converter actually processes files on their device. If a conversion works without an internet connection, the tool cannot be uploading your file. No trust required. No policy to read. Just a practical, repeatable test.
The DevTools method
For a more thorough audit, use your browser's built-in developer tools to monitor network activity during a conversion. This method catches edge cases the Wi-Fi test might miss, such as pre-cached results or partial uploads.
- Open the converter you want to test.
- Open DevTools (F12 or Cmd+Option+I on Mac).
- Switch to the Network tab and clear any existing entries.
- Run a conversion with a sample file.
- Look for any POST request that carries file data. If none appears, the tool processed your file locally.
A genuinely client-side tool will show no outbound requests carrying file data. You may see small requests for analytics or fonts, but the file payload itself should never leave the browser.
Try it with ConvertPrivately
Every tool below works with your Wi-Fi off. Try it.
Frequently asked questions
- What if the conversion fails when I'm offline?
- That means the tool requires a server — your file was being uploaded. Look for alternatives that process locally in the browser.
- Does the Wi-Fi test work on mobile?
- Yes. Enable airplane mode and try the conversion. Same principle.
- Can a site fake client-side processing?
- Technically a site could cache the result while online and serve it offline. The DevTools network audit is more thorough — but for practical purposes, the Wi-Fi test catches 99% of upload-based converters.
- Why does ConvertPrivately work offline?
- Because our tools use WebAssembly and JavaScript libraries (pdf-lib, ffmpeg.wasm, Canvas API) that run entirely in your browser. There is no server to send your files to.
- What about ConvertPrivately's OCR tools?
- Seven tools that use Tesseract OCR do require a server connection. These are clearly labelled on our How It Works page. The Wi-Fi test will correctly identify them.
160+ privacy-first conversion tools
No upload for most formats. No account. No retention.