Unlike the tighter limits, 200KB is rarely imposed by a form. People choose it — as a self-imposed budget for web images, because it is roughly where a full-width photograph stops hurting page load times while still looking good on a large screen.
The performance case
Images are usually the heaviest thing on a web page, and the largest one is very often the element that determines your Largest Contentful Paint — the Core Web Vitals metric that measures when the main content actually appears. A 2MB hero photograph on a mobile connection can take seconds to arrive. The same photograph at 200KB arrives in a fraction of that, and on most screens nobody can tell the difference.
That last point is what makes 200KB a comfortable target rather than a painful one. At this budget most photographs compress at quality 80 or above, which is the range where JPEG artifacts are genuinely hard to see at normal viewing distance.
What this budget supports
- A 1920-pixel-wide hero image: usually fits without any dimension reduction, at a quality most people would call untouched.
- Blog and article photographs at 1200 pixels: very comfortable, often landing above quality 85.
- Product photography on plain backgrounds: extremely comfortable — you may find these come out well under the limit.
- Full-resolution camera files at 6000 pixels wide: too many pixels. These get scaled down, which is what you wanted for the web anyway.
Consider whether you need JPEG at all
Worth saying plainly, since this is a performance-motivated conversion: if the destination is a modern website, WebP reaches the same visual quality as JPEG in roughly 25–35% fewer bytes, and AVIF does better still. Converting to one of those may get you under 200KB with quality to spare, or let you serve a sharper image at the same weight.
JPEG remains the right answer when the image is going somewhere that will not accept anything newer — an email, an older content system, a print service, or a form that specifies a size cap in the first place.
How the target is hit
No fixed quality setting produces a predictable file size, because the cost of a setting depends on the picture. The tool encodes, measures and narrows the range about a dozen times to find the highest quality that fits under 200KB. Only if that fails does it reduce dimensions, which at this budget is uncommon unless the source is very large. Everything runs in this tab, with nothing uploaded.