About CompressEazy

Why this site exists

Almost every free image compressor works the same way. You pick a file, it uploads to a server you know nothing about, something happens to it there, and you download the result. For a screenshot of a meme, that is fine. For a passport scan, a signed contract, a medical form, an ID card, or a photo of your children, it is a genuine problem. You have handed a complete copy of a sensitive file to an unknown third party, and you have no way to know how long they keep it, who can read it, or what it is used to train.

CompressEazy was built in March 2026 to remove that trade-off entirely. Every tool here runs inside your own browser. There is no upload step, because there is no server to upload to. The compression, resizing, cropping, format conversion, and face blurring all happen on your machine, using processing power you already own.

How it actually works

When you drop an image onto any tool on this site, your browser reads the file directly from your disk using the FileReader API and draws it onto an HTML Canvas element. The canvas holds the raw pixel data in your device's memory. Re-encoding that canvas at a different quality level, in a different format, or at different dimensions produces a new image file — and the browser does all of it natively, with no network involved.

This is not a clever workaround. It is the intended use of a set of web standards that have been in every major browser for years. The consequence is that a compressor built this way is structurally incapable of leaking your files, because the code path that would send them somewhere simply does not exist.

A few tools need extra capability that the browser does not provide on its own — reading iPhone HEIC photos, building ZIP archives, generating PDFs, or running OCR text recognition. For those we load well-established open-source libraries from a public CDN. Those libraries are code that runs on your device, exactly like the rest of the page. They receive your image in your browser's memory and return a result there. They do not transmit it.

Don't take our word for it — verify it

A privacy claim you cannot check is just marketing. This one you can check in under a minute, in two independent ways:

Watch the network. Open your browser's developer tools, switch to the Network tab, then compress an image. You will see the page and its scripts load. You will not see your image go anywhere, because no request carries it.

Pull the plug. Load any tool page, then turn off your Wi-Fi or switch on airplane mode. Now compress, resize, or convert an image. It still works. A tool that needed a server would have failed the moment the connection dropped.

That second test works because CompressEazy is a Progressive Web App. A service worker caches every tool page on your first visit, so you can install the site to your home screen or desktop and use it permanently offline.

What we do and don't collect

We want to be precise here rather than vague. We use analytics to understand which tools people use and whether they work — page views, and anonymous counters for events like "a compression finished" or "a download was clicked." That tells us a tool is being used and is not broken.

What we never receive is anything about the images themselves. Not the file, not the filename, not the contents, not a thumbnail, not a hash. This is not a policy promise we are asking you to trust; it is a consequence of the architecture. Data that never leaves your device cannot be collected by us, and it cannot be handed to anyone else, subpoenaed, or exposed in a breach. Our privacy policy sets out the specifics.

How it stays free

Reasonable people are suspicious of free tools, and they should be. The usual answer is that you are the product. Here the answer is more boring: client-side processing costs us nothing per image.

A conventional compressor pays for CPU time, bandwidth, and storage on every single file its users process, so it has to recover that cost somewhere — subscriptions, ads, upsells, or data. Because your device does all the work here, our costs are limited to serving a few static files. That bill does not grow meaningfully as more people use the site. So there are no accounts, no usage caps, no watermarks, no paid tier, and no queue.

Who builds it

CompressEazy is an independent project, not a venture-backed company or a division of a larger business. It is maintained by a small team that works on it directly, which is why the toolset is opinionated: we add tools we and our users actually need, and we would rather do a narrow set of jobs well than list a hundred half-working features.

That also means feedback reaches the people who write the code. If a tool produces a bad result, mangles a specific file type, or behaves strangely on your device, telling us is genuinely useful — bug reports from real files are how most of the rough edges here got fixed. You can reach us through the contact page.

Where to start

If you have a specific size limit to hit, compress by quality or target an exact size such as 100KB. For the web, converting to WebP usually beats compressing a JPEG. Working through a whole folder is what the bulk compressor is for, and it returns everything as a single ZIP. If you are sharing a photo publicly and need to protect someone's identity, blur face does it without the image ever going online.