Get an image down to 100 KB — web-ready in seconds
The 100 KB target is preset: the tool automatically finds the highest quality that stays below it and shows you the before/after size. Everything runs locally in your browser — no upload, no queue, works offline.
Why is 100 KB a good target for the web?
Because images are the single largest chunk of page weight and feed straight into Google's loading metrics: the Core Web Vitals rate a Largest Contentful Paint of up to 2.5 seconds as good — and the LCP element is very often the page's biggest image. A 100 KB image instead of a 1 MB photo shortens exactly that metric, especially on mobile networks. Your CMS media library and newsletter tool will thank you too.
How do I get the best quality out of 100 KB?
Two levers work together: pixel dimensions and format. First resize the image to the size it is actually displayed at (1200 px wide is often enough for content images) — the KB budget then spreads over fewer pixels and quality visibly rises. And pick WebP where possible: per Google's study it is 25–34% smaller than JPEG at equal quality.
Honest limits
A full-resolution 12-megapixel photo does not fit into a good-looking 100 KB — the tool reports unreachable targets honestly and offers the smallest achieved size instead of silently overshooting. Losslessly optimised PNG screenshots often stay above 100 KB; as JPG/WebP they make it. EXIF metadata is dropped during re-encoding.