Compress an image to under 200KB
Bring an image under 200KB without uploading it. Comfortable room for a full-size photograph at a quality nobody will question.
KB here means 1,000 bytes, so a file under the number you set is under it whichever convention the form on the other end uses.
Drop JPG, PNG, WebP, HEIC, AVIF, GIF, BMP files here or paste from the clipboard.
Your files are processed on this device. Nothing is uploaded.
Where this limit comes from
Two hundred kilobytes is a web performance budget more often than a hard limit. It is the figure performance guides settle on for a hero image, the default cap in several content management systems and the point at which an image stops meaningfully affecting how fast a page feels on a mobile connection. Some marketplaces and classified-ad sites enforce it per photo, which is where most people meet it as a rule rather than a target.
What fits in 200 KB
Most of a real photograph. Two hundred thousand bytes usually holds 1,600 to 2,000 pixels on the long edge at a quality indistinguishable from the original at normal viewing distance, which covers full-width display on almost any screen. This is the first target on this list where a typical phone photo keeps its dimensions and only loses compression headroom.
A budget rather than a limit
Most people arriving at 200KB aren’t being told to by a form; they have read that images should be small and picked a round number. That is a reasonable instinct and the more useful version of it is to think per page rather than per image.
An image displayed at 800 pixels wide on a phone doesn’t need to be 2,400 pixels wide in the file. Capping the width is usually a bigger saving than any amount of quality adjustment and it costs nothing visible because the extra pixels were never displayed.
Where the remaining weight goes
Once each image is around 200KB, the next wins aren’t in compression at all. They’re in serving WebP instead of JPG, in sizing images to the space they occupy and in not loading images below the fold until they’re needed. Those are build and markup decisions rather than things a compressor can do.
Check the result at full size
At this target the compressed file is usually indistinguishable from the original in normal use, but it is worth one look at full zoom on any image with a large area of smooth gradient, such as a sky. Banding is the first artefact to appear and the easiest to miss on a small preview.
Common questions
Is 200KB a good budget for images on my site?
For a large hero image, yes and for images further down a page you can usually go lower. What matters more than any single figure is the total weight of images on the page, since a page with fifteen images at 200KB each is three megabytes of images however reasonable each one looks on its own.
Will my image keep its full dimensions?
Usually. At this target a normal photograph reaches the size through quality alone, so the dimensions survive. The tool only reduces dimensions when quality has bottomed out and it reports when it has done so.
Should I use WebP instead of JPG for this?
On a website, yes. WebP reaches the same visual quality in roughly a quarter to a third fewer bytes, which either gets you a smaller file or a higher quality one at 200KB. Keep JPG for anything leaving the browser, such as an upload to a marketplace that hasn’t caught up.
My image is already under 200KB. What happens?
The tool hands it straight back untouched and says so. Re-encoding a file that already fits would only degrade it, so the check happens before any compression does.
Guides
Compress to a specific size
Each of these opens the tool with the target already set.