Compress an Image to 100KB
To get a photo under 100KB, open the image compressor, choose Target Size, type 97 and press Compress. That's the short version. Below is why 97 and not 100, how many pixels you can keep at 100KB for different kinds of image, and what to do when the result doesn't look good enough.
The quick way
- Open the image compressor and add your photo.
- Switch to Target Size (KB).
- Choose JPG, unless you know the destination accepts WebP.
- Type 97 and press Compress Image.
- Check the result at the size it will be seen, then download.
The tool lowers the quality first, never below 60 percent, and only if that isn't enough does it reduce the pixel dimensions, by exactly the amount the measured file size says is needed. You end up with the largest, cleanest image that fits, not a full-size photo destroyed by low quality. Nothing is uploaded: the compression runs in your browser.

Why type 97 and not 100
There are two ways to count a kilobyte. Most software, including our compressor, counts 1 KB as 1024 bytes. Some upload forms and servers count it as 1000 bytes. For most purposes the difference doesn't matter. At a hard limit, it does.
We noticed this while testing. Asked for 100 KB, the tool returned files it reported as 98.0, 98.8 and 98.9 KB. In bytes, those were 100,393, 101,136 and 101,287. Every one of them is under 100 KB counted the 1024 way, and every one is over a limit of 100,000 bytes. A form that counts the decimal way would reject them, usually with an error message that doesn't explain why.
Typing 97 gives you a file under 99,328 bytes, which passes either way. You lose about 3 percent of the size budget, which is invisible in the image. If a form also states a minimum, check it the same way: a form asking for "at least 20 KB" counted in thousands of bytes needs a file over 20,000 bytes.
How much photo fits in 100KB
"100KB" says nothing about how large the image can stay. That depends almost entirely on what's in it. We ran five very different images through Target Size at 100 KB, in JPG and in WebP, and noted the size each one ended up at:
- A portrait on a plain background, cropped to passport proportions (2847 × 3660 pixels, 588 KB): stayed at 2235 × 2874 as JPG, and at its full size as WebP. Smooth backgrounds and skin compress extremely well.
- A product photo on white (1280 × 959, 127 KB): 1184 × 887 as JPG, full size as WebP. Clean product shots are easy at 100 KB.
- A detailed outdoor photo, a dog on a beach with sand, water and foliage (3607 × 2234, 3.9 MB): had to shrink to 1288 × 798 as JPG, 1736 × 1075 as WebP. Fine random detail like sand and leaves is the most expensive thing to keep.
- A text document, an A4 page at 200 dpi with 42 lines of text (1654 × 2339): 777 × 1099 as JPG, 875 × 1237 as WebP. That's roughly 94 pixels per inch on paper, readable on screen for normal text sizes, but small print would suffer.
- A phone screenshot full of text (1080 × 1920): 470 × 835 as JPG, 537 × 955 as WebP. The letters shrink to less than half their size.
So 100 KB is generous for portraits, ID photos and product shots, workable for typical outdoor photos shown at web size, and tight for documents and screenshots, where every letter needs to stay readable.
One surprise: we also made a clean version of the document, with a pure white background instead of off-white paper with grain. We expected it to keep more pixels. It didn't: 735 × 1039, slightly smaller. With a page full of text, the sharp edges of the letters cost far more than the paper texture. Cleaning a scan helps a lot with signatures and sparse pages (see the 20KB guide), much less with dense text.
JPG or WebP at 100KB
In every test above, WebP kept more pixels than JPG at the same limit: 35 percent more width on the beach photo, 13 percent more on the document. At 100 KB that difference is visible. WebP also keeps transparency, which JPG can't.
The catch is acceptance. Most modern websites, CMSs and social networks take WebP. Many government and exam portals, job application systems, older email clients and print services don't, and some reject the file only after you've filled in the whole form. If the upload page lists accepted formats and WebP isn't there, use JPG. If you're preparing images for your own website, use WebP.
Set a width first when you know the display size
Target Size finds the best fit automatically, but if you know how big the image will be shown, you can do better by telling it. Type a width in the compressor before the target:
- A blog or shop content image that displays about 800 pixels wide: set 1200 to stay sharp on high-density phone screens.
- An email or newsletter image: 600 to 800 pixels covers the width of almost every email layout.
- A profile picture: 400 to 600 pixels.
With a width set, the tool only has to choose the quality, and a smaller image at high quality looks better than a bigger one at low quality. A photo that would land at 1288 pixels and moderate quality on its own might come out at 800 pixels and 92 percent quality, crisper at the size people actually see it.
Where a 100KB limit usually comes from
You'll mostly meet 100 KB in three places. Upload forms set it to keep their servers and databases small; the image is usually shown small, as a thumbnail or on a profile, so you rarely need more pixels than the form allows. Older websites and forums use it for attachments and avatars. And people building websites set themselves a budget of around 100 KB per content image so pages load quickly on phones; there the limit is your own choice, and WebP plus a sensible width is the easiest way to meet it.
When the form gives both a pixel size and a file size, follow both. Set the width to the required pixel size, then use Target Size for the KB limit. And if a form asks for a minimum file size as well, our 50KB guide shows how to deal with results that come out too small, which happens surprisingly often with small ID photos.
On a phone
The compressor works the same in a phone browser. Tap the upload area, pick the photo from your library, and follow the same steps. When you pick a photo from an iPhone library in the browser, iOS usually hands the page a JPG copy, so HEIC photos aren't normally a problem there; if one won't open, setting Settings, Camera, Formats to Most Compatible makes the camera save JPG from then on.
The download goes to your Downloads folder (the Files app on iPhone, Files or My Files on Android). From there you can attach it to the form. Large photos take a few seconds longer on a phone than on a computer; setting a width first speeds things up.
When the result doesn't look good enough
If the compressed image looks soft or blocky, work through these in order:
- Crop first. Every pixel of background you remove is budget you can spend on the subject. A head-and-shoulders crop of a portrait or a tight crop around a document's text block makes a visible difference. The image cropper does this without losing quality.
- Try WebP if the destination accepts it.
- Judge it at the real size. A 100 KB image viewed at 300 percent zoom will always look rough. Look at it the way the reader will.
- Check the real limit. Some forms say "under 100 KB" in one place and accept up to 200 KB or more in their technical notes. Don't sacrifice quality you're allowed to keep.
- For documents, consider a PDF. If the form accepts PDF, a scanned page is often clearer as a PDF of the same size, because text in PDFs from scanning apps can be stored more efficiently.
And always start from the original photo, not from something that has been compressed or sent through a messaging app already. Each round of compression throws away detail that can't be brought back.
Privacy
Photos for forms are often personal: ID photos, certificates, payslips. The compressor never uploads them. The compressed file also comes out without the original's camera data, so the GPS location of a photo taken at home isn't sent along with it. If you want to remove that hidden data without compressing, the metadata remover does it without touching the image.
Frequently asked questions
Why should I type 97 instead of 100?
Our compressor counts 1 KB as 1024 bytes, but some upload forms count 1 KB as 1000 bytes. Several of our 100 KB results were between 100,000 and 101,300 bytes, which those forms would reject. A 97 KB target always lands under 100,000 bytes.
How big can a photo be at 100KB?
It depends on the photo. In our tests a portrait on a plain background stayed at 2235 x 2874 pixels as JPG, a detailed beach photo had to shrink to 1288 x 798, and a text-heavy document to about 777 x 1099.
Should I use JPG or WebP?
WebP keeps more pixels at the same size: our beach photo fitted 1736 pixels wide as WebP against 1288 as JPG. But many forms only accept JPG, so use WebP only where it is accepted.
Will my photo be uploaded?
No. The compressor runs in your browser; the photo never leaves your device.
The 100KB result looks blurry. What can I do?
Crop away anything you don't need first, try WebP if the destination accepts it, and check whether the text or face is still clear at the size it will be shown. If the form allows more than 100KB, use the larger limit.
Can I compress a PNG screenshot to 100KB?
Yes, but convert it to JPG or WebP. A PNG can only shrink by losing pixels: our text screenshot had to drop to 182 pixels wide as PNG, while the JPG version stayed readable at 470 pixels.
