cropshrinkIMAGE STUDIOImages stay on your device
CANVAS No image selected

A little less.
A lot better.

Crop, resize & compress JPG, PNG, WebP and AVIF. Every pixel, in your control — and nothing leaves your device.

or drop an image anywhere · paste with ⌘ / Ctrl + V

No upload. Your images never leave this device.

JPG · PNG · WebP · AVIF input
Your next great image starts here.LOCAL PROCESSING

Compress an image to 100 KB

The editor above is already set to a 100 KB limit. Drop in a photo and CropShrink searches the quality range for the best-looking export that still fits — you do not have to nudge a slider and keep checking.

Why 100 KB, specifically

Almost nobody wants a 100 KB image for its own sake. They want it because a form will not accept anything larger. The limit turns up in the same handful of places:

If your form states a minimum as well as a maximum — 20 KB to 100 KB is a common pair — check the output size readout after the search finishes. If it lands too low, raise the target a little; the search always takes the largest quality that fits, so it will use the headroom you give it.

How the editor finds the setting

Quality settings are not calibrated in kilobytes, and the relationship between the two depends entirely on the picture. A flat studio backdrop at quality 90 may be smaller than a forest at quality 40. So rather than guessing, CropShrink measures.

It encodes your image at quality 50, checks the size, and then halves the remaining range in whichever direction it needs to go — seven encodes to search a hundred settings. Every candidate is measured, not predicted, so the export you get always fits the limit. The panel tells you which quality it settled on, so you can see how much headroom the picture had.

One quirk worth knowing: at quality 100 the browser writes lossless WebP, which can be larger than quality 99. The search checks the size of every candidate rather than assuming bigger quality means bigger file, so this does not trip it up.

100 KB looks different at different sizes

A file size limit is really a budget of bytes per pixel. Spread the same 100 KB over more pixels and each one gets less. We measured it: the editor’s own resize and size search, run on our sample photograph — a detailed lakeside landscape, close to the hardest case a real photo presents — at seven widths:

PixelsMegapixelsWebP qualityJPEG qualityResult
400 × 2670.119999No visible loss
600 × 4000.249695No visible loss
800 × 5330.438785No visible loss
1000 × 6670.677670Clean, slightly soft
1200 × 8000.965451Clean, slightly soft
1600 × 10671.712423Smeared; not usable
1920 × 12802.461215Smeared; not usable

The pattern is the point: if 100 KB is hard to hit, the image is too big, not too detailed. A portrait against a plain background or a screenshot compresses far better than this landscape, so it can keep more pixels at the same quality.

When 100 KB cannot be reached

If even the lowest quality overshoots, CropShrink says so and tells you the smallest size your current dimensions can reach, rather than quietly missing the target or resizing your image without being asked.

The fix is almost always to reduce the dimensions. Switch on Resize, set the width to 1000 px — or 1200 px for a simpler picture — and run the search again. In the measurements above, a detailed photo that only fits at quality 12 at full width fits at quality 76 once it is 1000 px wide. If the form specifies exact pixel dimensions, use those; there is a page about resizing with more on choosing a width.

Cropping helps too, for a different reason: removing the parts of the frame you do not need removes their pixels from the budget entirely.

Other limits you may be given

The same control handles any target. Type the number the form asks for:

More image tools

Every one of these is the same editor, opened for a different job — and all of them run on your device.

Or start from the full editor, which does all of it at once.