Compress an image to under 200KB

Where the 200KB limit comes from

Unlike the tighter targets, 200KB is rarely a hard validator error. It is much more often a budget somebody chose, which means there is usually room to discuss it:

• Web performance budgets — a per-image ceiling agreed by a team so that no single asset can quietly ruin a page. This is the most common source, and it is self-imposed.
• CMS upload caps — many content systems and hosts limit uploads, and site owners often set a lower internal rule so that contributors cannot push 8MB camera files into a blog post.
• Forum and community post limits — attachment caps on discussion software, where the concern is total storage across millions of posts rather than any individual image.

The practical consequence: if you are hitting a 200KB limit, you are usually dealing with a policy rather than a validator, and the picture almost certainly does not need to suffer for it.

What 200KB actually looks like

Measured on a real 4K phone photograph (3840 × 2160, 1.52 MB), 200KB came out at 2044 × 1150 pixels at quality 65. That is larger than most web pages will ever display, at a quality setting where JPEG artefacts are not visible without pixel-peeping a comparison.

This is worth sitting with, because it reframes the whole exercise: the original file was 1.52 MB and the compressed one is 200KB. That is an 87% reduction for no visible cost. The 1.3 MB you removed was never doing anything a viewer could see.

Thinking in page budgets, not single files

200KB is where the interesting question stops being "how small can this image go" and starts being "how many images is this page carrying". A single 200KB hero is fine. Twenty 200KB images is a 4MB page, and that is slow regardless of how carefully each one was compressed.

A workable rule for a content page:

• One hero image at up to 200KB — it is the Largest Contentful Paint element and worth the bytes
• Body images at 100KB or below, lazy-loaded so they cost nothing until scrolled to
• Thumbnails and avatars under 20KB — at their display size they need nothing more, and a 200KB thumbnail is pure waste

Sizing every image to its slot rather than to a single site-wide number is what actually makes pages fast. Our image resizer handles the dimension half of that.

If 200KB is not enough

There are cases where it genuinely is not, and they are worth naming. Photography portfolios, product images with a zoom view, and anything a visitor will open full-screen all benefit from 500KB, where a full-resolution image survives compression essentially untouched. For everything else — blog images, article headers, marketing pages — 200KB is already past the point of diminishing returns, and 100KB would serve just as well.