piapia123
en

Image Compressor

Images

Everything runs locally in your browser — nothing is uploaded

Drop an image here, or click to choose

Or press Ctrl/⌘ + V to paste a screenshot

PNG / JPEG / WebP / GIF / BMP / AVIF · up to 30 MB each

Make an image smaller. The difference from the format converter is that you can specify a target size — enter a KB figure (200, say) and the tool binary-searches for the highest quality that stays under it, instead of leaving you to guess a quality step. That matters because quality and size are not linearly related: 0.9 to 0.8 may save 10%, while 0.5 to 0.4 can halve the file. When the target is unreachable it says so, and suggests limiting the dimensions — rather than quietly handing back a file that is larger than you asked for. PNG sources are converted to WebP, since quality does nothing for a lossless format.

Features

  • A target size in KB, with binary search for the highest quality that fits
  • A clear notice when the target cannot be reached, plus a suggestion to limit size
  • Quality steps (92%, 80%, 65%, 50%) when you prefer to pick
  • Limit the longest edge to 2560, 1920, 1280 or 800 pixels
  • Shows before and after (12.3 MB → 2.1 MB, −83%)
  • PNG sources become WebP, with the reason stated
  • Nothing is uploaded — compression happens in the browser

How to use

  1. Drop an image in
  2. Enter a target size in KB, or pick a quality step
  3. If it will not go small enough, set a max edge as well
  4. The result shows the before/after; click Download to save

FAQ

Lowering the quality barely changed the size. Why?
Two cases. The source may be PNG, where quality does nothing at all — that is why it is converted to WebP here. Or the quality is already low (below 0.5), where each further step saves less and less while visibly softening the image. The effective lever then is size: going to 1280 or 800 pixels cuts the file several-fold and usually looks better than crushing the quality.
How is the target size computed?
Binary search. The tool encodes at the midpoint between the lowest quality (0.3) and 0.95, measures the result, and narrows the range — about seven attempts reach the highest quality under the target. Each attempt is a real encode, which is why it takes a few hundred milliseconds: there is no way to know the size without producing it.
It hit the target — can it look better?
The binary search already returns the highest quality that fits, so within that limit it is as sharp as it gets. For a sharper image, either allow a larger size or shrink the dimensions first — smaller dimensions fit a higher quality into the same budget.
Is the image uploaded?
No. Compression uses the browser's own canvas, entirely in local memory, and works offline.

Related tools