Compress Image to 100 KB
Drop in a photo and get it back under 100 KB. The tool searches for the highest quality that still fits, so you keep as much detail as the limit allows.
Finding the best quality that fits…
- Original
- —
- Result
- —
- Reduction
- —
- Dimensions
- —
How to use this tool
- Choose your image, drag it onto the box, or paste it from the clipboard. JPG, PNG, WebP and HEIC all go in; JPEG comes out.
- There is nothing to set. This page is already fixed at under 100.0 KB, JPEG.
- It scales the image down first — on our reference file, to 1508 × 1131 px — then searches the encoder quality. That run took 7 encodes.
- Download from the panel, which shows the original size, the final size and the output dimensions. Nothing was uploaded at any point.
A widely used web limit — large enough for a good-looking hero or product image.
Compress Image to 100 KB — the specification
| Target file size | Under 100 KB |
|---|---|
| Output format | JPEG |
| Dimensions | Unchanged unless the size target requires shrinking |
| Colour space | sRGB |
| Transparency | Flattened onto white — JPEG has no alpha channel |
Compress Image to 100 KB: why uploads get rejected
Landing under 100 KB is necessary but not sufficient. These are the reasons a file that meets the size still gets sent back:
- The file is a PNG screenshot. PNG is built for flat graphics, not photographs, and a PNG photo can be five times larger than the same image as JPEG. Converting alone often gets you under 100 KB.
- The image has very large pixel dimensions. A 4000 × 3000 phone photo squeezed to 100 KB looks soft no matter how good the encoder is — reducing dimensions first preserves far more apparent detail.
- You compressed an already-compressed file repeatedly. Each pass discards more information permanently. Always start from the original.
How it works
Hitting a size limit exactly is a search problem, not a setting. There is no quality value that means “100.0 KB” — how many bytes a given quality produces depends entirely on the picture. So this tool encodes, measures the real file, and adjusts.
It starts by capping the pixel count, because quality alone cannot rescue an image that is simply too large. On the reference file measured below that meant going from 4000 × 3000 to 1508 × 1131 before the first encode. That ordering is what keeps the search cheap: the six or seven encodes that follow all work on the smaller image.
It then binary-searches the quality parameter: encode, measure, halve the remaining range, repeat. The run below took 7 encodes to land at 99.5 KB. A tool that picks one fixed quality instead either overshoots the limit or comes in far under it and throws away detail you did not need to lose.
Every one of those encodes ran on your own device through the browser’s canvas API — including the intermediate attempts the search threw away. None of them was uploaded.
A measured run of this exact preset
Not an estimate: this page’s own code, run against a 12 MP photograph, 4:3 and an A4 scan at 200 dpi, with every encode recorded. The files and the method are published here.
| Input | Result | Change | Outcome |
|---|---|---|---|
| 12 MP photograph, 4:3 4000 × 3000 px · 3.07 MB | 99.5 KB 1508 × 1131 px | 97% smaller | Under the 100 KB limit |
| A4 scan at 200 dpi 1654 × 2339 px · 996.0 KB | 99.8 KB 1099 × 1554 px | 90% smaller | Under the 100 KB limit |
Step by step
Before touching quality at all, the tool worked out how many pixels 100.0 KB can realistically describe, and scaled the image from 4000 × 3000 down to 1508 × 1131 — 86% fewer pixels. Doing this first is what keeps the run quick: every attempt after it encodes the smaller image rather than the original.
The first probe at quality 0.96 came out at 592.7 KB, about 5.9× the 100.0 KB limit, so the search began.
It then narrowed the quality setting 6 times — quality 0.51 gave 119.2 KB, quality 0.29 gave 76.9 KB, quality 0.4 gave 99.5 KB, quality 0.45 gave 110.2 KB, and so on — settling on quality 0.4.
Final file: 99.5 KB, using 99.5% of the allowance, with 466 B to spare.
Who needs Compress Image to 100 KB
People reach this page for three reasons: an upload form rejected a photo for being too large, an email attachment would not send, or a page loaded slowly because of oversized images. All three are solved the same way — get under the limit while giving up the least quality possible.
Compress Image to 100 KB — frequently asked questions
How close to 100 KB does it get?
The tool searches seven quality levels and keeps the largest result that still fits under 100 KB. In practice you land within a few percent of the limit rather than far below it, which means more retained quality than tools using one fixed setting.
What if my image cannot reach 100 KB?
If even the lowest quality is too large, the tool reduces the pixel dimensions and searches again, up to seven times. If it still cannot get there, it tells you the smallest size it actually achieved rather than silently returning something over the limit.
Which formats can I upload?
JPG, JPEG, PNG, WebP and most formats your browser can display, including HEIC on Safari. Output is JPEG, because JPEG reaches small sizes on photographs far more efficiently than PNG.
How do I reduce image size to 100KB without losing quality?
Some quality loss is unavoidable — that is what making a file smaller means. What you can control is how much. Start from the original rather than an already-compressed copy, reduce the pixel dimensions if the image is far larger than it needs to be, and let the tool find the highest quality that fits rather than picking a fixed setting. That is what the search on this page does.
What is the difference between resizing and compressing an image?
Resizing changes the pixel dimensions — a 4000 × 3000 photo becomes 800 × 600. Compressing keeps the dimensions but stores the same pixels less precisely. Both reduce file size, and for a target as small as 100KB you usually need both. This tool compresses first and reduces dimensions only if compression alone cannot get there.
Does this work on a phone?
Yes, including photos straight from your camera roll. The work happens on the device, so a very large image is slower on a phone than on a laptop, but nothing is uploaded either way.
Is 100 KB the right target, and what you actually get
Where this limit comes from: Passport and visa photographs, PAN card applications and many document portals.
At 100 KB the quality setting alone cannot reach the target, so the image is scaled down as well — to 38% of its original width in the measured run. That is the trade-off this limit forces. If the form accepts more, the next step up keeps noticeably more detail.
The same source file put through this target and the ones either side of it, measured rather than estimated:
| Target | Result | Final size in pixels | Scaling applied |
|---|---|---|---|
| 75 KB | 74 KB | 980 × 1306 px | 32% of original width |
| 100 KB (this page) | 100 KB | 1508 × 1131 px | 38% of original width |
| 150 KB | 149 KB | 1386 × 1848 px | 46% of original width |
If the portal gives a range rather than a hard number, take the largest it allows. Every step down this ladder costs detail that cannot be recovered afterwards.
Related tools
From other categories
Background reading: Image Size Requirements for Every Major Platform
Your photo never leaves your device. Open your browser's Network tab while you use this page and you will see no upload — how that works.
Disclaimer. Published requirements change without notice. Confirm against the official source before you submit. Full disclaimer.