Compress Image

Shrink a photo to an exact size — aim for 100 KB, 200 KB, or whatever number the form asks for. It all runs in your browser; nothing is uploaded.

Drop a photo here

or choose a file · or paste a screenshot with Ctrl + V

JPG, PNG, WebP, GIF & HEIC · one image at a time · no upload · no account

Compress Image: How to Hit an Exact Size (100 KB, 200 KB) Without Wrecking It

The short answer: Every "compress to 100 KB" job comes down to two dials — quality and pixels — and the order you turn them decides whether the result looks fine or looks like a fax. The tool above turns them for you, then shows you exactly what it did: original size, final size, the quality it used, and whether it touched the dimensions. The rest of this page is the part the other compressors don't tell you: why targeting an exact KB is a trade-off, when shrinking the picture beats fuzzing it, and the 30-second check before you upload.

Why the exact number matters

Forms, portals, job applications, email attachments, forum avatars — they don't ask for "smaller", they ask for under 100 KB. That's a hard gate, and it's why "compress to 100 KB" is a different request from "make this smaller". A tool that only offers a quality slider makes you guess-and-check until the number fits. A tool that takes the number as the goal can search for the setting that hits it — which is what the one above does.

The two dials, and which one to turn

A JPEG file's size is controlled by two things:

• Quality — how aggressively the encoder throws away fine detail. Lower quality = smaller file, but at some point the damage becomes visible: text gets fuzzy halos, faces get blotchy skin, gradients get banding.
• Pixels — how many there are. Half the width and height means a quarter of the pixels, and photos compress down roughly in proportion.

Here's the part almost nobody explains: past a certain point, turning quality down buys less than you think — and shrinking the picture costs less than you fear. A big phone photo crushed to a tiny KB at full resolution often looks worse than the same photo with fewer pixels at a decent quality. That's why the tool above tries quality first, and when quality alone can't reach your target, it starts resizing — and tells you when it did.

"Without losing quality" is a slogan, not a measurement

You'll see that phrase on every compressor page, including some very big ones. Here's what's actually true:

• Compression is lossy. Some detail is gone, permanently, the moment you save. The honest question is not whether quality changed but whether you can see it at the size people will actually view it.
• There is no magic setting that reaches any size losslessly. If a tool promises 100 KB "with zero quality loss" on a 6 MB photo, it either resized the photo, softened it, or both. Ours does the same work — it just prints the receipts.

Don't recompress the same file twice

Each save of a JPEG compresses it again — artifacts compound like a photocopy of a photocopy. If your first result doesn't fit, go back to the original and compress once with a lower target, rather than compressing the compressed file. Keep the original until the upload succeeds; after that, the small copy is the one you keep.

The 30-second check before you upload

1. Look at the number the tool reports — is it at or under the limit? (The tool above won't go over.)
2. Zoom to 100% on the text. Signs, IDs, serial numbers — if the letters have halos or blur, lower the target less aggressively or start from a sharper original.
3. Check the dimensions if you care about print or detail — the result card says whether the picture was resized.
4. Note the metadata. The compressor above writes a clean file — no camera data, no location data — which is usually a feature, and worth knowing if you wanted the EXIF kept.

A worked example

Take a normal phone photo — the kind that lands in your upload form at a few megabytes and gets rejected. Set the target to 100 KB and run it. Here is a real run from this page (a 12-megapixel iPhone photo):

5.89 MB → 97.0 KB (98% smaller) · 3024×4032 → 514×685 · quality 50

That line is the whole story — a real run, receipts included. It got under the limit mostly by shrinking the picture: the long edge came down from 4032 to 685 pixels, and the encoder stopped at a middle quality instead of grinding quality to dust at full size. That is what "under 100 KB" honestly costs for a detailed phone photo — a small image, but a clean one. If your form only cares about the number, this is done; and unlike the guess-and-check routine, you did not have to run ten tries to get there. Need more pixels? Raise the target: 200 KB or 500 KB buys back a lot of picture.

Compress once, check the text, upload. That's the whole job.