← Exact80

What 80 KB looks like

Four kinds of image, each at exactly 80,000 bytes, next to the original. Drag the divider. These are the engine's own output — same code the site runs, numbers from the same run — so if the engine gets worse, this page does too.

Photograph

2.0 MB → 80,000 bytes

A 2400×3600 beach scene, 2.0 MB. Far more detail than the budget holds, so the search trades resolution for a clean image.

Original
AVIF · 80 KB
OriginalAVIF · 80 KB
Original
2400×3600
At 80 KB
683×1024
Quality
62
SSIM
0.826

Photo by Merve Kalafat Yılmaz on Unsplash

Screenshot

106 KB → 80,000 bytes

A 2560×1600 capture. Text is the hardest thing to keep legible on a budget, and the two formats disagree about how to spend the bytes.

Original
AVIF · 80 KB
OriginalAVIF · 80 KB
Original
2560×1600
At 80 KB
2560×1600
Quality
95
SSIM
1.000

Illustration

142 KB → 80,000 bytes

Flat colour and a long gradient — the case where over-compression shows up as banding across the sky.

Original
WEBP · 80 KB
OriginalWEBP · 80 KB
Original
2400×1600
At 80 KB
2400×1600
Quality
92
SSIM
0.998

Transparency

205 KB → 80,000 bytes

An alpha channel has to survive the budget too, and it is not free: both formats spend bytes on it.

Original
AVIF · 80 KB
OriginalAVIF · 80 KB
Original
2000×2000
At 80 KB
1600×1600
Quality
91
SSIM
1.000

The photograph is the interesting case: it carries far more detail than the budget holds, so the search spends the bytes on a smaller, cleaner image rather than a full-size smear. The transparent graphic is the one where the formats part company — AVIF keeps the alpha channel at full size, WebP has to give up resolution to afford it.

Generated 8 October 2026 by pnpm build:gallery.