Every online image compressor works the same way. You choose a file, it travels across the internet to a server you know nothing about, something happens to it there, and a smaller file comes back.

For most photographs that is a perfectly reasonable trade. For some of them it is the single riskiest thing you will do with the file all week.

What “upload to compress” actually involves

Your image is copied onto hardware you do not control, in a jurisdiction you probably did not check, for a retention period you did not read. It may be scanned. It may be cached by something in between. It may sit in a temporary directory for longer than the interface implies.

None of that is necessarily sinister. Most operators are running an ordinary business and deleting files on a timer. The point is narrower: you cannot verify any of it, and you gave up the ability to when you pressed upload.

Four situations where it genuinely matters

  • Client work under an NDA. Plenty of agreements prohibit sharing deliverables with third-party services. Uploading to compress is exactly that, whether or not anybody notices.
  • Unreleased product. Packaging, hardware, a design not yet announced. A leak does not need malice — a misconfigured bucket will do.
  • People. Photographs of children, medical images, anything with a face and a name attached. Consent to be photographed is not consent to be uploaded somewhere else.
  • Documents. Scans of passports, contracts, invoices, bank statements. People compress these constantly to get them under an upload limit, without registering what they have just done.

The terms you did not read

Free web tools are paid for somehow. Sometimes it is advertising, which is fine and visible. Sometimes the terms grant a broad licence to process, store or analyse what you send. That language is often boilerplate copied from a template rather than a statement of intent — but it is what you agreed to, and it is what would be enforced.

The checklist for judging free image software goes through what to look for before you commit a folder to one.

Metadata travels with the picture

An upload is not just pixels. A camera JPEG carries EXIF data — device, lens, timestamp, and on most phones the exact GPS coordinates where the shutter fired. Upload an unedited photo taken at home and you have shared your address along with it.

SqueezeImages strips location metadata on export as part of compressing, so a lighter file is also a quieter one. There is more detail in what EXIF data your photos reveal.

What offline actually guarantees

“Secure” is a word every tool uses. “Offline” is a claim you can test in ten seconds.

Turn off your Wi-Fi. Pull the cable. Then compress something. If it still works, the file never went anywhere — not because we promised, but because there was no connection for it to travel over. That is a stronger assurance than any privacy policy, because it does not depend on trusting anybody.

It also means no queue and no size cap, since nobody else is paying for the processing. The features section covers what that changes day to day.

What this website collects

The app and the site are different things, and it would be slippery to blur them. The application processes your images locally and uploads nothing. The website is an ordinary website: it serves advertising and counts downloads. What that involves is set out in our privacy policy.

If you would rather not take our word for any of it, download the app and run the network test. That is the whole argument.