How to Tell If a File Tool Actually Runs Locally

When a website offers to compress, convert, or edit your file, a fair question sits underneath it. Where does the file go? Some tools open the file in your browser and do everything on your own machine. Others quietly send it to a server, do the work there, and hand back a result. The page rarely tells you which, and the words “online” and “browser” get used loosely enough that they prove nothing on their own.

You do not have to take anyone’s word for it. Your browser already gives you everything you need to check. Below are two tests. Run either one and you will know.

TL;DR: Load the tool, turn off your internet, then try to process a file. If it still works, the file is being handled on your device, not uploaded.

Test one: the airplane-mode test

This is the simplest test and the most convincing. The idea is plain. If a tool needs to upload your file, it needs the network. Cut the network and the upload becomes impossible. So if the tool still works with no connection, the work is happening locally.

Here is the procedure.

1. Open the tool’s page and let it finish loading. Wait until you can see the upload box or the buttons you would normally use.
2. Switch off your connection. Turn on airplane mode, toggle off Wi-Fi, or unplug the cable. On a laptop, the fastest route is usually the network icon in your menu bar or system tray.
3. Confirm you are actually offline. Open a new browser tab and try to load any other website. It should fail. This step matters, because a cached page can fool you into thinking you are offline when you are not.
4. Go back to the tool’s tab and use it. Pick a file, run the conversion or compression, and wait for the result.
5. Watch what happens. If the tool produces your finished file with no connection, the processing ran on your device. If it hangs, shows a spinner that never resolves, or throws an error about the network, it was relying on a server.

One detail trips people up. You must load the page first, while you are online, and only then go offline. The page itself has to download before it can run. Once it has loaded, a locally-built tool keeps every following step on your machine. So loading the page online and processing the file offline is exactly the split you are testing for.

Reload the page while offline if you want a stricter check. A tool designed to keep working without a connection will often reload fine from your browser’s cache and still process files. That is a stronger signal again, though it is not required to trust the basic result.

Test two: the Network tab

The second test watches the traffic directly. Every browser ships with developer tools, and one panel there lists every request the page makes. You can open it, process a file, and look for your file leaving.

The keyboard shortcut to open developer tools is F12 on Windows and Linux, or Option-Command-I on a Mac. You can also right-click anywhere on the page, choose Inspect, and find the panel from there.

1. Open developer tools and click the Network tab.
2. Make sure recording is on. There is usually a round record button near the top left; it should be filled, not hollow. If the list looks frozen, click it once to start.
3. Clear the list so you start clean. There is a clear button, often a circle with a line through it.
4. Now process your file in the tool. Upload it, run the operation, and let it finish.
5. Read the list of requests that appear.

What you are looking for is an outbound request that carries your file. The clearest sign is a POST or PUT request with a large size in the Size column, roughly matching the size of the file you just fed in. Click any request to see its detail. A request that sent your file will show it in the request payload or under a tab labelled Payload or Request. A handful of small requests for fonts, scripts, or an occasional analytics ping is normal and not the same thing. You are hunting for the one big upload.

If you process a sizeable file and see no large outbound request at all, nothing was sent. The work stayed local.

What each test can and cannot prove

Neither test is magic, and it helps to know the edges.

The Network tab tells you what is being sent, but reading it takes a little practice. A busy page can list dozens of requests, and telling a harmless one from a real upload means checking sizes and payloads. It is precise but fiddly.

The offline test is blunter and harder to fool. A tool simply cannot upload a file with no connection, so a tool that keeps working offline is not uploading. That is why, if you only run one test, this is the one to run.

There is one nuance worth naming. Local processing and total silence are two different things. A tool could do all the real work on your device and still send a small, separate report, for analytics or error logging, that contains no part of your file. The offline test handles the question that matters most, which is whether your actual file leaves your machine. The Network tab is where you would go to inspect anything else the page chats about.

A quick checklist

Keep this short version handy.

1. Load the tool fully while online.
2. Go offline and confirm other sites fail to load.
3. Process a real file.
4. Works offline? The file stayed on your device.
5. Want detail? Open the Network tab, process a file, and look for one large POST or PUT carrying it.

Try it on a tool built to pass

The reason to learn these tests is that you can stop trusting claims and start checking them. Our tools at hivly.net are built to run on your device, and they keep working once the page has loaded, so the file you drop in never travels anywhere. You do not have to believe that line. Open one of the image tools at image.hivly.net, let it load, switch off your connection, and convert a photo. It finishes with no network, because the photo never left your computer. The same test works on any file tool you come across, which is the whole point. The next time a site asks for your file, you can find out exactly where it goes before you hand it over.