A job portal wants your photo under 100 KB. A visa form caps uploads at 200 KB. An email signature tool refuses anything over 50 KB. The photo on your phone is 3 MB, and every tool you try either blurs it into mush or stops one step short of the limit.
This guide explains what makes an image file large, how to hit an exact target in 2026 without trial and error, and what "without losing quality" realistically means for a photo that has to shrink by 95%.
What decides an image's file size?
Three things, in order of impact:
Pixels matter most. A 4032 × 3024 px phone photo has 12 million pixels. A 1200 × 900 px version has 1 million, about one twelfth of the data before any compression. If an image will be shown at 400 px wide, storing 4000 px of width is pure waste.
Format comes next. JPG and WebP are lossy: they throw away detail your eye does not notice, so photos compress 10 to 20 times smaller than raw pixels. PNG is lossless, which is perfect for logos and screenshots and terrible for photos, where it is often five to ten times larger than a JPG of the same picture.
Quality is the dial on lossy formats. Quality 90 keeps almost everything; quality 40 starts to show blocky edges and banding in skies. The file size curve is steep at the top: going from 100 to 80 often halves the file while looking identical, going from 40 to 20 saves little and looks bad.
How to compress an image to 100 KB with ImageSizeTool
ImageSizeTool has a compress mode that does the search for you. Instead of moving a quality slider and re-exporting until the number looks right, you set the limit and the tool tries qualities until it finds the highest one that fits.
- Open compress mode and pick a target: 100 KB, 200 KB, 500 KB, or type any number after upload.
- Drop your image, paste it, or choose a file. JPG, PNG, WebP and iPhone HEIC all work.
- Read the result line. It says exactly what happened: "87 KB at quality 62", or "96 KB at quality 10, resized to 1440 × 1080" when quality alone was not enough.
- Download. The file you get is the file that was measured, byte for byte.
Everything runs in your browser. No upload to a server, no account required.
What the search does behind the scenes
The tool encodes your image at your chosen quality (90 by default) and measures the real file. If it is over the target, it checks quality 10 to see whether the target is reachable at all, then binary-searches the qualities in between and keeps the highest one that fits. That takes five or six encodes, usually well under a second.
If even quality 10 is too large, it reduces the dimensions in 10% steps (90%, 80%, and so on) and repeats, because at that point pixels are the only lever left. If nothing fits, it shows the smallest result it could make and still lets you download it.
Does compressing to 100 KB lose quality?
Honestly: yes, some. The question is whether anyone can see it.
For a photo viewed on a screen, quality 70 and above is visually indistinguishable from the original to almost everyone. Between 50 and 70 you may notice slightly softer fine textures (hair, grass, fabric) if you compare side by side. Below 40, blocky 8 × 8 pixel artifacts and colour banding in smooth gradients become visible without comparison.
So "without losing quality" really means "without losing quality anyone will notice". Two habits keep you in that zone:
Shrink pixels before you shrink quality. A 1600 px wide photo at quality 75 looks far better than a 4000 px wide photo at quality 15, and both land near 100 KB. If the form only shows your photo at 300 px, there is no reason to keep 4000.
Crop out what nobody needs. A tighter crop removes pixels without touching the subject. Compress mode keeps the full crop tool one click away for exactly this reason.
JPG, WebP or PNG: which gets smallest?
Pick WebP when the destination accepts it (websites, most modern apps, email clients from the last few years). Pick JPG when the form says JPG, or when you cannot check. Avoid PNG for photos with a size limit: with no quality dial, the only way down is fewer pixels.
One exception: screenshots, logos and text-heavy graphics compress better as PNG than as a low-quality JPG, and JPG artifacts around text are ugly. For those, reduce dimensions and stay in PNG, or use WebP.
Why can an image not always reach 100 KB?
Detailed photos hold a lot of genuine information: foliage, crowds, fabric, noise from a dim room. At quality 10 a 12-megapixel version of such a photo can still weigh 300 KB. When that happens the tool reduces the dimensions, and the result line tells you the new size.
If you would rather control that yourself, open "Crop and resize" in compress mode, set a smaller output size or a tighter crop, and let the search run again at a higher quality. A 1200 px photo at quality 60 almost always beats a 4000 px photo at quality 10.
Typical upload limits
| Where | Common limit | What usually works |
|---|---|---|
| Job and application portals | 100 KB to 500 KB | 600 to 1000 px on the long side, JPG, quality 60 to 80 |
| Government and visa forms | 50 KB to 300 KB | 400 to 600 px, JPG, the form's exact pixel size if given |
| Email signatures | 20 KB to 50 KB | 300 to 400 px wide, PNG for logos, WebP or JPG for photos |
| Website images | 100 KB to 300 KB | 1200 to 1600 px wide, WebP, quality 75 to 85 |
| Social media posts | 1 MB to 8 MB | Platform preset size, quality 85 to 90 (see the platform guides) |
Limits vary, so check the form. When it names both a pixel size and a file size, set the pixel size first in the editor, then the target.
Common compression mistakes
Re-saving a JPG over and over. Every save of a lossy format discards a little more. Compress from the original once, at the final size, rather than shrinking in several passes.
Lowering quality on a huge image. Quality 15 on a 4000 px photo gives a blocky file that is still large. Reduce the pixels first, then the quality has room to stay high.
Exporting photos as PNG to a size limit. PNG cannot trade detail for size, so a photo under 100 KB in PNG ends up tiny. Switch to JPG or WebP.
Trusting an estimate instead of a measurement. Tools that predict file size from a formula miss by 30% or more on real photos. Measure the actual encoded file; ImageSizeTool does, and the readout is the download.
Compressing before cropping. Cropping after compression means re-encoding the already compressed image. Crop to the final frame first, then compress once.