How to Reduce Image Size Under 100KB

A 100KB image budget is strict but realistic for thumbnails, inline blog images, small ecommerce cards, and lightweight landing pages. The goal is to reduce dimensions and encode efficiently before quality gets ugly.

The 100KB recipe

1. Start from the original, not a recompressed copy.
2. Resize to the real display size.
3. Strip metadata.
4. Try WebP at quality 78.
5. If still too large, try AVIF at quality 50–58.
6. If still too large, reduce dimensions by 10–20%.
7. Compare against the original at the final rendered size.

The batch image compressor can run this as a repeatable local workflow. For photos, the AVIF compressor is often the best path to a hard byte target.

Dimension targets

Trying to force a 2400px photo under 100KB will usually damage quality. Resize first.

Format targets

When 100KB is the wrong target

Do not force every LCP hero under 100KB if it makes the brand image look broken. A crisp 180KB AVIF hero can be better than a visibly damaged 95KB file. Use 100KB where it helps: content images, thumbnails, and repeated assets.

What usually gets you under the line

If you are stuck at 140–180KB, the solution is rarely “drag the quality slider lower forever.” Try these in order:

1. Reduce the long edge by 10%.
2. Strip metadata.
3. Switch JPEG to WebP.
4. Switch WebP to AVIF for photos.
5. Crop empty background if the composition allows it.
6. Remove unnecessary transparency.
7. Use fewer responsive candidates for tiny placements.

Dimensions are the quiet hero here. A 1400px image may need too much quality loss to fit under 100KB, while a 1000px version can look nearly identical in the page and fit comfortably.

Realistic examples

The harder cases are noisy photos, detailed food shots, fabric textures, and screenshots with lots of text. Those images contain real detail, and real detail costs bytes.

How to keep quality acceptable

Review the final image in context. A thumbnail should be judged at thumbnail size. A product detail image should be judged at the zoom level shoppers will use. A social preview should be tested in an actual preview card, not only as a standalone file.

If the image needs to persuade someone, do not chase 100KB blindly. Use the target as a prompt to optimize, then stop before the image stops doing its job.

Size-budget workflow

A good size-budget workflow searches for the highest quality that fits your target. That is better than manually exporting ten files and guessing. In Asset Melt, set your target, keep resizing reasonable, and compare the output before publishing.

For repeated work, save the settings as a preset: “Article image under 100KB,” “Product grid under 100KB,” or “Social preview under 200KB.” Named presets turn a stressful one-off into a repeatable publishing habit.

For social previews, see best image sizes for Open Graph and social media. For general settings, read best image compression settings for web.