Compress Image to 100KB

How to compress an image to 100KB

1. Select your photo — JPG, PNG, WebP, HEIC and AVIF all work.
2. The target is already set to 100KB. Change it if you need a different ceiling.
3. Press Compress.
4. Check the result — it will be at or just below 100KB — and download.

When you need a 100KB image

100 KB is the most requested image limit on the web, and for good reason — it is small enough to load instantly on a slow connection and large enough to still look like a real photograph.

• Online application forms. University admissions, visa portals, job applications and government e-services overwhelmingly settle on 100 KB as the maximum photo or document scan size.
• Website hero and content images. A 100 KB hero image is a good Core Web Vitals budget for LCP on mobile; anything much larger starts to hurt.
• Email attachments in bulk. Twenty photos at 100 KB is a 2 MB message that will not bounce.
• Marketplace and classified listings — many impose per-image caps around 100 KB.
• WordPress and CMS media libraries where storage is metered.

How the 100KB compressor works

Hitting a byte target precisely is a search problem, not a formula. Here is what runs when you press the button:

1. Analyse. The image is decoded and measured — dimensions, format, whether it has transparency, and its true byte size.
2. Estimate. A first quality guess is derived from the ratio of 100KB to the original size. This is only a starting point, never the answer.
3. Binary search on quality. The image is re-encoded and measured, then the quality range is halved toward the target. Eight to twelve encodes are usually enough to land within a few percent.
4. Reduce dimensions, but only if needed. If even the lowest acceptable quality overshoots, the scale factor √(target / current) is applied with a small safety margin and the quality search restarts at the new size.
5. Refine upward. If the first success lands well under 100KB, the search tries a larger scale to spend the remaining budget on pixels rather than leaving it unused.

The result is the largest, sharpest image that still fits — not the first one that happens to be small enough. Landing at 100KB minus a hair is the goal; landing at a third of 100KB is a failure, even though it technically fits.

Getting the best quality at this size

100 KB is generous enough that a well-chosen photo can look excellent. Practical notes:

• Typical output. A 4032×3024 phone photo usually lands around 1200×900 to 1600×1200 at quality 70–80. That is sharp on any phone and perfectly respectable on a laptop.
• WebP buys you real detail. If the destination accepts WebP, the same 100 KB holds noticeably more resolution. If it is a government form, stay with JPG.
• Screenshots are the hard case. Text and sharp UI edges cost far more bytes than a photo. Consider PNG with palette reduction, or crop to just the part that matters.
• Already close to 100 KB? The tool will say so rather than needlessly degrading a file that already fits.

Will the quality drop?

Some quality is always lost when a large photo is squeezed into 100KB — the question is whether you will notice. The result panel shows an honest verdict:

• Excellent — indistinguishable from the original at normal size.
• Very Good — differences visible only when pixel-peeping.
• Good — fine for web and messaging use.
• Reduced — visible softening; acceptable for thumbnails and forms.
• Low — the target is aggressive for this image; consider raising it.

If you would rather keep every original pixel and accept whatever size results, tick Keep original dimensions in Advanced Settings — the tool will then solve with quality alone, and tell you if it cannot reach the target.

Supported formats

Input: JPG, PNG, WebP, GIF, BMP, HEIC/HEIF and AVIF. Output: JPG (default and smallest for photographs), WebP (smaller still, keeps transparency), or PNG (only sensible for flat graphics).

HEIC and AVIF decoders are downloaded on demand, so pages stay light for everyone who does not need them.