Compress Images to 100KB

Where 100KB sits

A hundred kilobytes is small but not extreme. It is enough for an avatar, a small profile image, a card component on a web page, and many email inline images, comfortably. It is not enough for a full width blog image or a gallery thumbnail that is displayed large, where a detailed photograph starts to soften. Understanding which of those two categories you are in is the first useful step, because it determines whether you should resize.

Dimensions decide quality at this budget

The same principle as every tight limit applies here. Compression removes detail; resizing removes pixels. At 100KB on a large image, the encoder has to strip a lot of detail and the result is soft. Resize to a sensible width first, and each remaining pixel gets a larger share of the budget, so the image looks sharper at exactly the same file size. This single change does more for a small file than any quality setting.

• For an email or card image, resize to 400 to 600 pixels wide before compressing.
• For a blog image displayed at a known width, resize to that width and roughly double it for density.
• Compress a full resolution image to 100KB only when full resolution is genuinely required.
• Compare the two results at 100 percent before deciding which to use.

NoteAn image resized to 500 pixels and compressed to 100KB usually looks better than the same image at 3,000 pixels compressed to 100KB.

Format and quality together

At 100KB the format matters as much as the slider, because it determines how much detail survives the same budget. WebP and AVIF hold noticeably more detail than JPG at an identical byte count, and they support smooth transparency, which JPG cannot do at all. PNG keeps flat graphics and hard edges perfectly clean but is a poor choice for a photograph, where it would be far too large. The right combination depends on what the image contains rather than on the number.

• Photograph: WebP gives the best detail at this budget, where the destination accepts it.
• Graphic, logo, or flat colour: PNG or WebP lossless keeps edges exact.
• Transparent image: WebP or PNG. JPG discards the alpha channel entirely.
• JPG only when the destination requires it, and then at the highest quality that fits.
• Look for banding in smooth areas if you use JPG at a low setting.

Hitting the target reliably

The tool works to an explicit byte count of 100,000, which satisfies a limit stated as either 100KB decimal or a binary equivalent, and the output size is displayed so you can check it. A file already inside the target is passed through unchanged rather than degraded for no benefit. If the target genuinely cannot be met at an acceptable quality, that is reported rather than disguised, and the fix is a smaller canvas or a different format.

• Targets 100,000 bytes exactly, so it fits either convention.
• Files already within the limit are copied through unchanged.
• A target that cannot be met acceptably is reported, not disguised as success.
• Aim slightly under the limit rather than exactly at it.
• Check the reported byte count before uploading to a form that enforces it.