How to check whether a converter uploads your files

Where the file is processed

A server-side converter receives your file for processing. That matters for a passport scan, medical result, signed contract or rental-application ID, because the provider's access and retention practices then apply to the uploaded copy.

Server-side conversion can handle jobs beyond the software or memory available in your browser. Local and server-based tools can both have a file picker, progress indicator and download link, so the interface alone does not tell you where processing happens.

The Network panel can show requests made during conversion. An offline test answers a narrower question: can this conversion finish without a connection?

Test one: watch the Network tab

Open the converter in a desktop browser and open developer tools, usually with F12 on Windows or Linux, or Command-Option-I on a Mac. Select Network and reload once so the panel records the page loading. Clear the recorded list with the panel's Clear control, then choose your test file and start the conversion.

A script or WebAssembly download before processing can be converter code arriving on your device. To look for an upload, open each new request and check its destination, method and any payload the browser exposes. POST and PUT requests can carry files. Check the payload too, because file data can also be encoded, split across requests or sent another way. In Chrome, select a request and open Payload to see the query parameters or form data that DevTools makes available.

Select All so that no filter hides a request type. Check WebSocket connections and their messages too, since a WebSocket can carry file data. The Size column can describe a resource the browser received, so it does not measure an upload directly.

Conversion time alone does not show where the work happens. A slow connection can delay a library download before local processing begins, and both your device's speed and a remote service's workload affect the wait. Decide from the requests you see and from the offline test.

Test two: turn the network off

Load the converter and complete a conversion online so any extra components have time to download. Disconnect the device from the internet, then use a different test file without reloading the page. Check that the conversion finishes and that its output contains the expected content.

A conversion that finishes with the device disconnected ran on your device. A failure alone does not show that the converter needs a server: the page may lack a cached component, reject the input format or hit a browser problem.

Keep the loaded tab open for this check. Reloading an uncached page while offline only tests whether the page can load, which says nothing about where it converts files. If the browser clears or replaces its cache, repeat the online conversion before you test again.

To try it here, prepare the decoder with one online conversion on the HEIC-to-JPG converter, then disconnect and convert another photo.

Read the file-handling policy

Look for where processing happens, whether files are stored and who can access them. A policy is the provider's own account of its practices, and the tests above let you check it. These common phrases answer different questions.

"Files are automatically deleted after 24 hours." Read this alongside the description of where processing and storage happen. For server-processed files it describes how long the uploaded copy is kept, which means the service did receive a copy.

"Encrypted in transit" or "secure connection." TLS protects the connection to the destination. It does not stop the receiving service from accessing a file, and it does not control what happens after the file arrives.

"We do not look at your files." This describes who may open your files. It says nothing about where conversion happens, so look for a separate explanation of processing and storage.

"Processed on our secure servers." This describes server-side processing. Check the provider's storage, access and retention terms before sending a file.

Language describing local processing includes "in your browser", "client-side", "on your device" and "no server". Read any technical explanation, then compare it with the network and offline checks, letting any required code load first.

What the checks cover

The result applies to the file, browser and page version you tested. A page can behave differently online, with another file type, in another browser or after an update, so repeat the checks when those change.

A tool that converts files locally can still load analytics or advertising that records a visit. Those requests are a separate question from whether your document was sent. They appear in the same Network panel, so check them there, along with the provider's disclosures.

The checks also say nothing about conversion quality. Open the output and inspect its content, such as page order, image detail or audio, before relying on it, and keep the original file.