Your files never leave your device. All processing happens locally in your browser.

Reducing image size without losing quality

Most people reach for the quality slider first. That is usually the wrong lever — resolution and format matter more, and they cost you far less visible quality. This guide explains the order to do things in.

Fix size in this order

Each step below gives a bigger saving than the one after it, and does less visual damage. Work top to bottom and stop when the file is small enough.

  • Crop to what you actually need. Removing a third of the frame removes a third of the bytes, losslessly.
  • Resize to the dimensions it will be displayed at — roughly twice the CSS width for high-density screens.
  • Convert to a modern format: WebP is typically 25–35% smaller than JPEG at the same visual quality.
  • Only then lower the quality setting, in steps, checking the result at 100% zoom.

Where quality loss becomes visible

JPEG artifacts appear in a predictable order as quality drops. First blockiness in smooth gradients, like skies and studio backdrops. Then colour bleeding around saturated reds. Then ringing — faint halos — along sharp edges against flat backgrounds, such as text on a poster. Finally the blocking becomes visible everywhere.

That means the safe quality setting depends on the image, not on a universal number. A photo of foliage hides compression extremely well; a screenshot of white text on black shows it immediately. Judge at 100% zoom on the areas above, not on a thumbnail.

Choosing the format

JPEG remains the universal choice for photographs, and the only safe option when the file is headed into a document, an email or another application. PNG is correct for screenshots, diagrams, line art and anything needing transparency — but it is a poor fit for photos, where it can be several times larger than JPEG.

WebP is the right default for anything served on a website: smaller than JPEG at equal quality, with alpha support, and supported by every current browser. Keep the JPEG original for print or archival use, and publish the WebP.

Doing this without uploading your photos

Photo libraries are personal, and bulk-uploading them to an unknown service is a real privacy cost. Every operation described here runs inside your browser on CompressKit: resizing uses the browser’s own image decoder, and compression uses WebAssembly encoders shipped with the page. Your images are never transmitted.

Do it now, with no upload

Everything described here runs inside your browser. Your file is never transmitted.

Frequently asked questions

What is the lowest quality setting I can use safely?
There is no universal answer, because it depends on the image content. Start at 80, open the result at 100% zoom, and look at smooth gradients and sharp edges. If both are clean, step down by 10 and re-check. Stop at the first setting where you can see artifacts.
Does converting to WebP lose quality?
WebP can encode losslessly, or lossily at a chosen quality. Converting to WebP at a comparable quality setting is generally visually identical to the JPEG but noticeably smaller — which is why it is the better publishing format.
Why did my PNG get larger when I compressed it?
PNG is lossless, so "compression" can only re-pack the same pixel data; photos stored as PNG are already far larger than they need to be. Converting such a file to JPEG or WebP is what actually reduces size.