SquishPixel Blog · Image optimisation · Tools · Site security

How to check whether an image compressor uploads your files to a server

According to DEV Community, most free image converters copy your file to their own server, run the compression there and send back the result. The article says that copy can end up in a temp folder, a log, an error tracker or a support ticket. Terms of use often allow the site to keep files for debugging.

A browser-based compressor works differently. It reads the file in your browser tab, runs the encoder there and saves the result to your downloads folder. The image is never sent as a web request, so no server copy exists. The article says the tool keeps working even if you go offline after the page loads. It also notes that a big batch can warm up a laptop, because your own processor does the work.

The article gives a quick test. Open the browser's DevTools (the built-in developer panel, opened with F12), go to the Network tab, clear the log and run a conversion. A POST or PUT request roughly the size of your file means it was uploaded. If the network stays quiet during the conversion, it was not. The check should be done during the conversion, not at page load, because page load always downloads code.

DEV Community also points out that some tools run their interface in the browser but still send the file to a server for the actual compression. It adds that phone photos carry EXIF data, which is hidden information such as GPS coordinates, camera model and the time of the shot. The article says a local compressor strips this by default, while a server-side tool may or may not. It suggests uploading is fine for images you would publish anyway, but not for NDA work, client files, ID photos, medical images or unreleased products.

Why it matters

If you handle client images, product shots before launch or photos of people, a free converter can quietly create copies you cannot control. A retention promise such as deletion after one hour depends on the company's own systems, and you cannot check it. The Network tab test lets you see what a tool actually does instead of trusting its privacy policy.

Metadata is a second risk. Location data in a phone photo, or client names in filenames, can leak even when the image itself seems harmless. Teams that share image-handling habits across designers, marketers and developers should agree on which files may go to online tools at all.

Source: DEV Community. This brief summarises their reporting; read the original for the full detail.