The pictures that need the extra room
Encoders spend their budget on change. A photograph of a lawn, a forest, a crowd or a knitted jumper is change in every direction at once, and at a tight budget the encoder gives up and averages large areas into flat patches. Doubling the allowance is often the difference between grass and a green smear.
Wide landscape photographs benefit for the same reason. Sixteen hundred pixels across is enough to fill most laptop displays, and two hundred kilobytes covers that width without the sky banding into visible steps.
Judge it, do not assume it
The comparison slider matters more at this level than anywhere else, because the differences are subtle and localised. Drag it slowly over the busiest part of the frame rather than the sky. If nothing changes there, you have room to lower the target further and should take it.
Two hundred kilobytes on a real page
One such image at the top of an article is unnoticeable. Ten of them, and a reader on a slow connection waits several seconds before anything appears. Reserve this budget for images that genuinely reward it, and compress the supporting pictures far harder.
Questions
- When is 200KB actually necessary rather than wasteful?
- When the subject is texturally busy or the image is displayed large. Landscapes, group photographs, textiles and anything with foliage hold up much better here than at a hundred kilobytes. A portrait against a plain background or a flat graphic gains almost nothing from the extra allowance.
- Should I use AVIF instead of WebP at this size?
- AVIF encodes detailed photographs more efficiently than WebP and would reach this quality in a smaller file. The catch is browser support for creating AVIF, which is still missing in many browsers, so DropKB only offers it where yours can actually produce it. WebP is the dependable choice.
- My image is already under 200KB. Is there any point compressing it?
- Possibly not. If re-encoding produces a larger file than you started with, DropKB says so plainly and tells you to keep the original, which happens routinely with files that have already been optimised once. Compressing an already compressed image also discards detail a second time.
- How do I tell whether a picture actually needs this much room?
- Run it at the tighter budget first and inspect the busiest region with the comparison slider — a leafy background, a patterned shirt, a wall of brick. If detail there survives, the tighter budget was sufficient and the larger allowance would have been wasted bandwidth. If that region has flattened into patches while the sky still looks perfect, texture is what your picture is spending its budget on, and raising the ceiling is justified.