Compress an Image to 100 KB

The target below is already set to 100 KB. Drop an image in and the highest quality that still fits is chosen for you — in your browser, with no upload.

Target 100 KB about 1,230 × 925 pixels — wide enough for most in-article images Nothing uploaded

Drop an image here, or click to browse

JPG, PNG or WebP · processed locally · no size limit

Compressed image preview
Set a size and the quality is chosen for you — the highest that still fits.
80–85 is the sweet spot for photographs. Ignored while a target size is set.
Original—
Compressed—
—
Compression happens in a canvas element on your device. The file is never transmitted, so there is no upload wait and no size cap.

Why people compress to 100 KB

For most images on most web pages, 100 KB is the right answer and the one worth defaulting to.

  • In-article and blog images
  • Product photographs on a listing page
  • Anything that has to load quickly on a phone connection
  • Content management systems that warn above 100 KB

Is 100 KB enough for a web image?

A hundred kilobytes holds roughly 1,230 pixels across, which covers the width of nearly every in-article image on a normal layout. It is also the point where the compression stops being visible to a reader who is not comparing files side by side. If you are compressing for a website rather than for a form, this is the target to reach for — small enough to load quickly on a phone, large enough that nobody notices the saving.

Where 100 KB sits in a performance budget

On the web the number that matters is not the image's size but what it does to the moment the page looks ready. That moment is measured as Largest Contentful Paint, and Google's guidance is that "sites should strive to have Largest Contentful Paint of 2.5 seconds or less", assessed at the "75th percentile of page loads" — meaning the slowest quarter of real visits still counts against you.

On the kind of mobile connection that 75th percentile represents, every 100 KB is a meaningful fraction of that budget, and the largest image above the fold is very often the element LCP is actually measuring. Holding in-article images near 100 KB is what makes the number achievable without redesigning anything.

Source: web.dev — Largest Contentful Paint (LCP)

Compress once, at the size you will actually display

The most common waste on a web page is not weak compression — it is an image served far larger than the box it is drawn into, then scaled down by the browser. A 3,000-pixel photograph displayed in an 800-pixel column costs the visitor every one of those bytes and shows them none of the extra detail. Resize to the display width first and the file will very often fall under 100 KB on its own, before any quality setting is touched.

It follows that the target on this page is a consequence, not a goal. Decide the width you need, compress to it, and check the result against 100 KB rather than the other way round.

Repeated compression is not free

JPEG is lossy every time it is saved. Compressing an image, editing it, and compressing it again applies the loss twice, and the artefacts from the first pass become detail the second pass tries faithfully to preserve. Always go back to the original file when you need a different size, rather than re-compressing a copy that has already been through this tool — or any other.

How the target is reached

Quality is searched before resolution, because losing a little quality is far less noticeable than losing pixels. The tool encodes your image repeatedly, halving the range each time, until it finds the highest quality setting that still lands under 100 KB. Only if even the lowest quality is too large does it begin scaling the image down, and it re-searches quality at every smaller size rather than simply shrinking until it fits.

One format note worth knowing: PNG is lossless, so a quality setting does nothing to it. Hitting a size target with PNG is possible only by reducing dimensions. For photographs, WebP or JPEG will always get you further.

Frequently asked questions

Drop the file into the box above. The target is already set to 100 KB, so the tool searches for the highest quality that still fits and applies it. Nothing is uploaded — the whole thing runs in your browser.

A hundred kilobytes holds roughly 1,230 pixels across, which covers the width of nearly every in-article image on a normal layout. It is also the point where the compression stops being visible to a reader who is not comparing files side by side. If you are compressing for a website rather than for a form, this is the target to reach for — small enough to load quickly on a phone, large enough that nobody notices the saving.

At 100 KB you can expect about 1,230 × 925 pixels — wide enough for most in-article images. The tool always exhausts the quality range before it reduces resolution, so it gives up as little as the target allows.

WebP produces the smallest file at a given quality and is supported by every current browser. Choose JPEG if something specifically requires it, such as an older upload form. PNG is lossless, so a size target can only be met by reducing dimensions — avoid it for photographs.

No. Compression happens in a canvas element on your own device, so the file never leaves your computer. That also means there is no upload wait and no size cap.