Compress image to 100 KB
Land on 100 KB, not “somewhere under it”. Nothing is uploaded.
- No upload
- Exact target size
- Batch ready
Drag images here, or click to choose
JPG / PNG / WebP / HEIC · up to 25MB each · batch supported
Files never leave your device — everything runs in your browser.
Progress
That file could not be processed
Why 100 KB is a hard gate, not a suggestion
A form that says “maximum 100 KB” rejects a 101 KB file. Most compressors only promise “compressed”, so people submit, get rejected, lower the quality slider, and try again. This tool searches for the best quality whose encoded byte count is still ≤ 100 KB, then reports the exact number it produced.
Why 100 KB specifically
One hundred kilobytes is the most frequently specified photo limit on the web, and it is comfortable: about 680×450 px survives at quality 75. Only one rule matters here — always compress from the original, never from a file you already compressed for some other form.
Where a 100 KB cap actually comes from
- Job boards and ATS portals with a 100 KB or 200 KB photo limit
- Visa and e-government forms that say “max 240 KB” in the small print
- University portals asking for “a photo under 100 KB”
- Corporate mail gateways that reject attachments over 150 KB
If your form states a pixel size as well (for example 600×600 px), set the target size first and check the output dimensions — the two limits sometimes conflict.
What resolution survives at 100 KB
At a typical JPEG quality of 70–80%, a byte budget converts to a pixel budget. These are the dimensions that stay clean:
| Aspect | Dimensions | Typical use |
|---|---|---|
| 1:1 | 550×550 | profile, 2×2 in photo |
| 3:2 | 670×450 | camera default, prints |
| 16:9 | 730×410 | screens, slides |
These are computed, not copied: bytes ÷ 0.34 ≈ usable pixels. Going wider than this at 100 KB starts to show blocking on skin and text.
Why one pass usually misses the target
JPEG size is not linear in quality: dropping from 90% to 80% can halve the file, then 80% to 70% only saves 15%. A single guess either overshoots the limit or wastes 40 KB of headroom. This tool encodes, measures, and narrows the range until the output sits within about 2% of the limit — and if even the lowest quality cannot reach the target, it reduces dimensions instead of shipping a broken image.
JPG, WebP or PNG at 100 KB?
At the same 100 KB, WebP keeps roughly 8–12% more quality than JPG and preserves transparency — but a handful of legacy government portals still reject .webp, so check the form’s accepted types first. JPG is the safest default for photographs: every portal accepts it, and the cost is that transparency is flattened onto white (or the background colour you pick) and thin text edges soften. PNG is lossless, so “100 KB” cannot be reached by lowering quality at all — the tool reduces pixel dimensions instead, which is the right trade for screenshots, logos and line art and usually the wrong one for photos.
Privacy: the file never leaves the tab
No upload request is made. The browser decodes the image, re-encodes it on a worker thread, and hands you a download blob. You can open DevTools → Network, drop a file, and confirm there is no request carrying it. You can also switch off your network and it still works.