Pre-set target · 100 KB
Compress JPEG to 100 KB
A 100 KB file is the sweet spot for web publishing and sharing — small enough for slow connections and strict forms, large enough that nobody notices it was compressed. This editor lands under the ceiling automatically, searching quality locally on your device.
Drop images to compress
or click to pick from your device. Paste withCtrl + V works too.
JPG · PNG · WebP · GIF up to 50 images stays on your device
Recommended for web pages and sharing
Perfect for upload portals and ID documents — we probe encoding quality automatically until each file fits.
Aspect ratio is always preserved — leave a box empty to ignore that axis. We never upscale.
Saved as a new .min file — the original is never modified.
What 100 KB buys you
100 KB fits a lot more than people expect when the encoder is efficient:
| Use | What it looks like |
|---|---|
| Web/blog image | ≈ 1600 px at quality 70 — sharp on retina screens |
| Documentation & SOPs | Screenshots stay readable well under the cap |
| Commerce galleries | 1–2 MB of gallery weight becomes kilobytes |
Who hits this exact limit
- CMS and theme file-size limits for uploaded images
- Forum avatars, signatures and profile photos
- Product photos on marketplace or shop platforms
- Any gallery where ten images must not cost ten megabytes
Why the limit exists
For a page, every picture is a download cost. At 100 KB a modern MozJPEG progressive JPEG passes a visual A/B next to a 1 MB original at web resolutions — the page loads faster and the picture loses nothing viewers can name. That combination is why tech builders set 100 KB as their ceiling.
Three steps, about a minute
- 01
Drop your image
The editor arrives pre-set to 100 KB. One file or fifty — they stay on your device.
- 02
Press Run
The engine searches encoding quality until the file first fits under the limit, then locks in the best-safe option.
- 03
Save the result
Download the .min copy or the whole batch as one ZIP — with the guaranteed ceiling intact.
100 KB, answered
What resolution can a 100 KB JPEG hold?
With MozJPEG’s trellis-optimized encoding, a decent 1600 px-wide photograph sails in at quality 65–75. Busy textures (forests, confetti, crowd shots) will land a notch smaller in pixels at the same size — the engine searches rather than guesses, and shows you what it chose.
Does the 100 KB output keep EXIF data?
By default it is stripped — metadata parked in JPEGs is typically 10–40 KB straight off your budget before the picture even starts compressing, and carrying GPS coordinates around is needlessly leaky. If you specifically need the metadata, toggle "Keep EXIF & color profile" — the size search accounts for the extra overhead.
My photo is still over 100 KB — what gives?
Some impossible corners exist: a 12000 px panorama behind a 100 KB cap would need violence, not compression. The editor is honest about it — it applies a rescue downscale automatically and reports the trade. You are never handed a file that will be rejected at an upload gate.
Is 100 KB enough quality, or should I aim higher?
For pages and sharing, 100 KB at sensible dimensions is basically indistinguishable from larger files. If a picture is billboard-grade or archival, use the plain quality slider and ignore the target — quality-first is the better call there.
Need a different ceiling?
Need smaller dimensions too? The resize tool trims pixels without touching bytes.