Compress an Image to 20 KB

What 20 KB honestly means for your picture

Set expectations before you compress: a 20 KB file holds roughly one percent of the data of an average phone photo. Something must go, and the question is only what. At this budget, fine texture disappears first — hair detail, fabric weave, foliage — then subtle colour gradations flatten into visible banding, and sharp edges acquire the blocky softness of heavy JPEG or WebP quantisation. A photograph compressed this far looks like a photograph of a photograph. None of this is a defect of the tool; it is arithmetic that no compressor on earth can dodge.

What the tool can do is control where the loss lands. Instead of crushing quality while keeping 4000 pixels of width — which produces a huge, mushy image — it first brings the resolution down to a size the budget can actually support, then finds the best quality level for those pixels. Fewer, better-fed pixels always beat more, starved ones. The result card and preview show you the outcome before you commit to the download.

Why WebP is the right choice at this size

This page defaults to WebP deliberately. At extreme compression ratios the encoder matters enormously: WebP's design holds onto perceptible detail at quality levels where JPEG has already collapsed into visible blocking and colour smearing. For the same 20 KB, WebP typically delivers a recognisably better picture — cleaner edges, more accurate skin tones, less noise texture turned into mush. Modern browsers and most current upload systems accept it, and the acceptance list grows every year.

JPEG remains the fallback for the handful of systems that still refuse WebP, and the tool will hit 20 KB with it too — the picture simply carries more damage at the same size. PNG is not offered here for good reason: it is a lossless format, and lossless encoding of a photographic image at 20 KB is essentially impossible for anything larger than a small icon. Where the choice exists, let WebP do the work.

Cut resolution before you cut quality

The single most effective trick for extreme targets is deciding what the image is for. A 20 KB avatar displayed at 150 pixels looks acceptable; a 20 KB poster sized for a monitor does not. Compress the smallest sensible version: crop to the essential subject, let the tool reduce dimensions, and the quality that remains concentrates where viewers actually look. The automatic pipeline here pre-shrinks the longest side before the quality search begins, precisely so the encoder spends its tiny budget on real detail rather than stretching it across millions of pixels.

If the result is too rough for your purpose, the honest options are the same everywhere: a somewhat larger target, a smaller display size, or a simpler image — flat graphics, clean diagrams and text on plain backgrounds survive extreme compression far better than photographs. The preview shows which category your image falls into before you download it.

Will my photo look bad at 20 KB?

Honest answer: usually yes, by the standards of normal viewing. Fine detail vanishes, flat areas band, and edges soften — that is the physics of fitting a photograph into two percent of its natural size. The picture stays recognisable and usable for its actual job, like passing a form check or loading on a 2G connection, but nobody will mistake it for quality. The live preview lets you see exactly what survives before downloading, and if the result is unacceptable the realistic fixes are a larger target or a smaller display size.

Why does the tool recommend WebP for 20 KB targets?

Because encoder efficiency dominates at extreme ratios. WebP preserves recognisable detail at quality settings where JPEG already produces heavy blocking and colour wash-out, so the same 20 KB buys a visibly cleaner image. This page defaults to WebP output for that reason. Choose JPEG only when the system you are uploading to explicitly rejects WebP — the tool will still reach the target, the picture just carries more compression damage.

What resolution can a 20 KB image realistically have?

Roughly 600 to 800 pixels on the long side for photographic content in WebP, somewhat less for JPEG, and comfortably more for flat graphics or simple diagrams with large uniform areas. The tool decides automatically: it pre-shrinks oversized images before searching for quality, which is why the output stays coherent instead of turning into a smeared full-resolution mess. Forcing a 4000-pixel photo into 20 KB produces a worse result at every resolution, which is exactly what the pre-shrink step prevents.

Which kinds of images survive 20 KB best?

Simple, high-contrast content: logos, icons, text on plain backgrounds, diagrams with few colours. Photographic subjects rank roughly in this order — faces cropped tightly, then general scenes with clear subjects, then detailed textures like foliage, crowds or fabric, which degrade fastest. If your source image sits in the last group and the destination truly requires 20 KB, crop to the essential region first; removing background pixels is the one edit that always improves an extreme-compression result.

Can I go even lower than 20 KB?

Yes — type any value from 5 KB upward into the custom size box. Below 20 KB the same trade-offs accelerate: resolution drops further, and WebP becomes even more clearly the right format. There is a floor where every format gives up, and the tool will tell you honestly if your image cannot fit the value you asked for, instead of returning something broken. When you need smaller, think smaller dimensions first — a 400-pixel image can look fine at sizes a 1200-pixel one never will.