Compress images. They never leave your device.

MozJPEG-grade compression for JPG, PNG, WebP and HEIC, entirely in your browser. No caps, no watermarks, no uploads.

Pick the exact tool for the job

The dedicated pages fix the workflow and explain each format's behavior: what is lossy, what is lossless, and how to hit a hard size limit.

Compress JPGMozJPEG compression with a quality slider. The workhorse for photos.Compress PNGLossless oxipng optimization: identical pixels, smaller file.Compress WebPRe-encode oversized WebP exports to fit performance budgets.Compress HEICiPhone photos into smaller universal JPGs. Most compressors reject HEIC entirely.Compress to 100KBName a size limit in KB and the quality is tuned automatically to hit it.Resize imageScale the longest side down to any pixel value; often the biggest saving of all.

Common questions

Is there really no file limit?+

Correct: no daily cap, no per-file size wall, no batch ceiling below 200 files, no watermark and no account. Because your own device does the compressing, an extra file costs us nothing, so there is nothing to meter. Compare that with the typical free tier of upload-based compressors: around 20 images of 5 MB each.

Lossy or lossless: which does this use?+

It matches the format. JPGs and WebPs are compressed lossily at the quality you choose, which is where big savings come from. PNGs are optimized losslessly, so pixels stay mathematically identical. HEIC photos are re-encoded as smaller universal JPGs, since browsers can read HEIC but not write it.

How much smaller will my images get?+

Typical results: photos as JPG at quality 80 shrink by roughly 60 to 80% versus camera output; PNG screenshots lose 10 to 40% with zero visual change; HEIC to compressed JPG commonly halves the size. Each result row shows the exact before and after so you never guess.

Are my images uploaded anywhere?+

No. The compressors are WebAssembly builds of MozJPEG, oxipng and libwebp running inside your browser tab. Load this page, disconnect from the internet, and compression keeps working. There is no server-side copy, no retention window and nothing to delete.