Why 100 KB is a target, not a promise
An encoded image is the result of dimensions, format, visual complexity, transparency, noise and quality. Two images with identical dimensions can require very different amounts of data. The compressor iterates toward 0.1 MB, but it may stop above or below that point to protect a usable result or because the browser encoder cannot reach it.
How to get closer to 100 KB
- Add the image and keep the preset target at 0.10 MB.
- Choose a maximum dimension appropriate for the destination. An 800 px web copy is easier to reduce than a full-resolution camera photo.
- Begin near the default quality and process the image.
- If the result remains too large, lower dimensions before making a severe quality reduction.
- Inspect small text, faces, sharp edges and gradients before accepting the result.
Format affects the result
JPEG is often suitable for photographs. PNG may remain comparatively large when it preserves transparency or lossless detail. WebP can be efficient for many web images, but browser support and the actual encoded result still matter. Compress mode preserves the source format; choose Compress & Convert when a format change is appropriate.
A file displayed as “100 KB” by one interface may differ slightly because some software uses decimal units while this site formats sizes with base-1024 calculations. The 0.1 MB control is therefore best treated as an approximate workflow aid, not a compliance certificate.
100 KB image FAQ
Can I force exactly 100 KB?
No. Browser encoders do not expose a reliable control for an exact byte count across every image and format.
Should I reduce quality or dimensions first?
If the image is larger than its display need, reducing dimensions usually provides a strong saving while keeping a sensible quality value.
Will the original file be overwritten?
No. A new result is created in browser memory and downloaded with a new filename.
For format-specific guidance, use Compress JPG, Compress PNG or Compress WebP.