Image Compressor

Compression is a tradeoff

Lossy compression stores an approximation of an image. Lower quality generally means fewer bytes, but it can introduce blocks, halos around edges, and smeared fine textures. Inspect small text and faces before sharing.

Encoding runs locally, using the browser codec or a WebP fallback when needed. Quality values are encoder settings, not universal quality scores or guaranteed file sizes. Results can differ between browsers.

When compression does not help

PNG encoding is lossless here, so the quality slider does not affect PNG output. An already optimized image can grow after re-encoding. The result panel reports this instead of presenting a negative saving as success.

If the file is still too large, use Image Resizer to reduce dimensions. A lower pixel count often saves more than repeatedly lowering quality.

Start with the destination

A 1 MB cap is a byte limit, not a pixel size. Use the guide below to work toward a target with a margin. Keep an original copy so you can try again without stacking lossy edits.

Read the comparison before downloading

If the original is 2,000,000 bytes and the output is 800,000 bytes, the reduction is 60%. If the output is 2,200,000 bytes, it is a 10% increase, not a saving. The result panel shows the actual direction.

Changing quality or format clears the old result. Run compression again to create a copy with the new settings. PNG ignores quality in this browser encoder; JPG and WebP quality settings are lossy and can affect edges and text.