Is it safe to put your images through an online tool?

2026-08-15

You have a scan of a contract, a photo of your ID, or a folder of product shots that belong to your employer — and it needs to be smaller before something will accept it. You search for an image compressor, and just before you drop the file in, the question lands: where exactly is this file about to go?

How most online image tools work

The standard design is upload → process → download. Your file travels to the company's server, gets converted there, and comes back. There is nothing sinister about that architecture — servers are fast and it works on any device. But it does mean that, for some window of time, a copy of your image exists on a machine you don't control.

From that point, three questions decide how safe you actually are, and none of them can be answered by looking at the tool itself:

• Retention — how long does the copy live before deletion, and is deletion actually verified?
• Access — who at the company can read stored files while they exist?
• Breach — if that server is compromised, your files are part of what leaks.

Reputable services answer the first question in their privacy policy — typically promising deletion after some hours. If you are choosing an upload-based tool, that policy page is the thing to read: look for a specific retention window, not vague reassurance.

The alternative: tools that never receive your file

Browsers can resize, compress and convert images by themselves, using a built-in API called Canvas. A tool built this way runs its work inside your browser tab, on your own machine. The file is opened locally, processed locally, and saved locally. There is no upload step to worry about, because there is no upload.

The three questions above simply dissolve. Retention: nothing was received, so nothing is retained. Access: nobody can read a file that never arrived. Breach: a server can't leak what it doesn't have.

Don't take the claim on faith — test it

Any site can say "we don't upload your files". Two checks settle it, and neither needs technical skill:

• The offline test. Open the tool's page, then switch off Wi-Fi or turn on airplane mode. Drop an image in. If it still converts, your file plainly isn't travelling anywhere — there is no connection to travel over.
• The network tab. Press F12, open the Network tab, and watch while you convert. On an upload-based tool you'll see your file leave as a large POST request. On a browser-side tool you won't.

Run those checks on this site and, in the network tab, you will still see small pings: analytics events and a one-byte anonymous usage counter. Those carry which tool was opened — never the image, and never the file name. Our privacy policy spells out exactly what is in them, and the offline test works here precisely because the images don't need us.

The honest trade-offs

Browser-side processing is not magically better at everything, and it's fair to know the costs:

• Your device does the work. A hundred large photos on an old laptop will take as long as that laptop takes. There is no server farm behind it.
• The browser sets the limits. Formats the browser can't decode — iPhone HEIC in Chrome or Firefox, for instance — can't be converted this way. Upload-based tools handle those because their servers decode them.

For everyday JPG, PNG and WebP work, neither limit tends to matter. For a 600-photo archive or an obscure format, an installed program is honestly the better tool.

The short version

If an image is sensitive — a contract, an ID, anything under an NDA — prefer a tool where the file never leaves your machine, and verify the claim with the offline test rather than trusting the marketing. If you do use an upload-based tool, read the retention line in its privacy policy first.