How to Compress an Image to 100KB Without Ruining It
Upload forms love a size limit. "Photo must be under 100 KB" appears on visa portals, job applications, school systems and ancient government sites that haven't changed since 2009. And your phone photo is 4 MB.
The good news: getting under 100 KB is almost always possible, and you don't need to wreck the picture to do it. You just need to pull the right levers in the right order.
Three levers, and the order to pull them
File size depends on three things: how many pixels the image has, how hard it's compressed, and which format it's saved in. Most people only touch the second one. They drag a quality slider down, the image goes muddy, the file is still 300 KB, and they give up.
Pixels come first. A photo that's 4000 pixels wide is wildly oversized for something that will be displayed in a 600 pixel box on a form. Halve the width and you've cut the pixel count to a quarter. Quality comes second, because it only has to fix whatever size is left. Format comes last, and it matters mainly for screenshots, logos and anything with flat colours.
So: resize, then compress, then (only if you must) change format.
What I measured
I took one 1920 × 1920 image, resized it to a few widths and saved each as JPEG at different quality settings with a standard encoder. Sizes are in KB. This image is a smooth, clean render, so it compresses better than a typical phone photo with grass, fabric or noise in it. Treat the figures as a pattern, not a promise.
| Width (px) | Quality 90 | Quality 80 | Quality 70 | Quality 60 | Quality 50 |
|---|---|---|---|---|---|
| 1920 | 328 | 238 | 197 | 171 | 153 |
| 1600 | 261 | 187 | 154 | 133 | 119 |
| 1200 | 177 | 127 | 104 | 90 | 80 |
| 1000 | 137 | 98 | 80 | 70 | 62 |
| 800 | 99 | 71 | 59 | 51 | 45 |
Two things jump out. Dropping quality from 90 to 70 at the same size saves roughly 40%. Dropping the width from 1920 to 1200 at the same quality saves roughly 45%. They stack, and resizing is the one that does less visible damage.
Where the huge files come from
A modern phone shoots 4032 × 3024 pixels, about 12 megapixels, and stores 3 to 6 MB per shot. A document scanned at 300 DPI on A4 is 2480 × 3508 pixels. A screenshot from a high-density laptop screen can be wider than the screen you're reading this on.
None of those numbers has anything to do with what a form needs.
That gap is the whole opportunity. Because the source is so much bigger than the destination, resizing alone often does 80% of the work before you touch quality at all.
Three ways to land near 100 KB
Look at the cells close to 100. There are at least three routes there, and they're not equal.
At 1200 px and quality 70 the file is 104 KB. That keeps the picture big and accepts some softness in fine detail. At 1000 px and quality 80 it's 98 KB: smaller image, cleaner pixels. At 800 px and quality 90 it's 99 KB, and it looks the crispest of the three, but it's a small picture.
Which is right depends on where it's going. A passport-style upload that will be shown at thumbnail size wants the 800 px version. A product photo that people can zoom wants the 1200 px one. If you don't know, take the middle route.
One more thing worth knowing: is "100 KB" 100,000 bytes or 102,400? Some systems count one way, some the other. Aim for about 90 KB and the question never matters.
Other limits follow the same pattern. For 200 KB, 1600 px at quality 80 gives 187 KB in my test. For 50 KB, 800 px at quality 50 gives 45 KB, and you may prefer to go a little smaller in width rather than push quality that low.
When the file just won't shrink
Screenshots, logos and diagrams are usually PNG, and PNG doesn't have a quality slider in the same way. It's lossless, so the only real levers are fewer pixels and fewer colours. A 1500 px screenshot of a spreadsheet can easily sit at 400 KB as PNG and drop below 100 KB as JPEG, though text edges get a little fuzzy.
The counter-intuitive bit: for photos, PNG is the wrong format and converting to JPEG is the fix. For flat graphics it's the other way round, because JPEG adds blotchy artefacts around sharp edges. Match the format to the content. The Format Converter handles JPG, PNG and WebP in the browser, and WebP is often 25 to 35% smaller than JPEG at similar quality if the form accepts it.
And don't compress the same file over and over. Each lossy save throws away a bit more. Keep the original, compress a copy once, and if the result isn't right, start again from the original.
Scanned documents are a special case. A 300 DPI colour scan of an A4 page saved as PNG can run to several megabytes, but the same page as a greyscale JPEG at 150 DPI often comes out at a fraction of that size and stays perfectly legible, because text only has to be readable on a screen, not printed at poster size. If the form accepts PDF as well as images, check whether a PDF of the page ends up smaller. Whatever you pick, zoom into the result at 100% before you upload it, because a signature that turns to mush is exactly the kind of thing that gets an application bounced.
What I'd actually do
If I had one photo and a hard 100 KB limit, I'd skip the guessing:
- Resize to the width the page will really show (800 to 1200 px for most forms).
- Export at quality 75 to 80 as JPEG.
- Check the size. If it's over, lower the quality in steps of 5, never below about 60.
- If it's still over at 60, shrink the width again instead of pushing quality lower.
Below about quality 60, JPEG starts showing blocky patches in skies and skin. Shrinking the picture looks better than starving it.
Let the tool do the loop
That loop is tedious by hand, which is why UtiliKit has the Compress to a File Size tool. You enter a target such as 100 KB, 200 KB or 1 MB and it measures the actual encoded file instead of estimating, so the number you see is the number that gets uploaded. It only shrinks the dimensions if you tick the box that allows it, and if the target is impossible it says so instead of handing you a broken image.
Everything runs in your browser. Your photo isn't uploaded anywhere, which matters when it's a passport scan or a document. Up to five photos per job are free.
If you already know the exact width you need, the Image Resizer is quicker, and the Image Compressor gives you a quality slider with a live size readout. For a longer look at sizes for different platforms, the image size cheat sheet has the numbers.
Frequently asked questions
How do I compress an image to exactly 100KB?
Resize the width first, then lower JPEG quality in small steps until the file is under the limit. The Compress to a File Size tool does that loop for you and measures the real encoded size.
Will compressing to 100KB make my photo blurry?
Not if you resize first. A 1000 to 1200 pixel wide photo at quality 70 to 80 usually lands near 100 KB with only mild softness in fine detail. Dropping quality below about 60 is what produces visible blockiness.
Is 100KB the same as 100,000 bytes?
It depends on the system. Some count 1 KB as 1,024 bytes, so 100 KB is 102,400 bytes, others use 1,000. Aiming for about 90 KB avoids the problem.
Are my photos uploaded when I use the tool?
No. Compression runs in your browser, so the file stays on your device. See the privacy policy for details.