Compress an Image to 200 KB

The target below is already set to 200 KB. Drop an image in and the highest quality that still fits is chosen for you — in your browser, with no upload.

Target 200 KB about 1,740 × 1,310 pixels, usually with no resizing needed at all Nothing uploaded

Drop an image here, or click to browse

JPG, PNG or WebP · processed locally · no size limit

Compressed image preview
Set a size and the quality is chosen for you — the highest that still fits.
80–85 is the sweet spot for photographs. Ignored while a target size is set.
Original—
Compressed—
—
Compression happens in a canvas element on your device. The file is never transmitted, so there is no upload wait and no size cap.

Why people compress to 200 KB

Two hundred kilobytes is where compression stops costing you anything you can see.

  • Full-width hero and banner images
  • Photographs where detail genuinely matters
  • Portfolio and gallery pages
  • Print-adjacent uses at small physical sizes

When do you actually need 200 KB?

At this size a typical photograph usually needs no downscaling at all — the quality search alone gets there, often landing above quality 80. That makes 200 KB the sensible target for the one image on a page that has to look good at full width. It is worth knowing the trade though: a 200 KB hero is two 100 KB in-article images, and on a slow connection the hero is what delays the page.

Quality 85 is the industry reference point

Two hundred kilobytes usually lands a full-size photograph in the quality range that tooling treats as correct. Google's own page-auditing tool uses that range as its yardstick: Lighthouse re-encodes JPEG images at quality level 85, compares the result with the original, and reports the image only when "the potential savings are 4KiB or greater".

The useful reading of that is a ceiling on effort. If an audit tool considers a 4 KiB saving the threshold worth mentioning, chasing the last few kilobytes out of a 200 KB image is not where the win is. Getting a 2 MB original down to 200 KB matters; getting 200 KB down to 190 KB does not.

Source: Chrome for Developers — Efficiently encode images

One 200 KB image, not four

The case for this size is that it is spent on a single image — the one at the top of the page that a reader looks at deliberately. The case against spending it repeatedly is arithmetic: four images at 200 KB is 800 KB, which on a slow connection is the difference between a page that feels immediate and one that does not. A sensible page mixes the two targets, with one image at 200 KB and the rest near 100.

What 200 KB will not do

It will not make a photograph suitable for print. Print is measured in dots per inch rather than total pixels, and at 300 dpi an image of roughly 1,740 pixels across covers about six inches of paper — fine for a postcard, not for a poster. It also will not recover detail that is not in the original: a blurred or badly lit photograph compressed to 200 KB is simply a smaller blurred photograph.

How the target is reached

Quality is searched before resolution, because losing a little quality is far less noticeable than losing pixels. The tool encodes your image repeatedly, halving the range each time, until it finds the highest quality setting that still lands under 200 KB. Only if even the lowest quality is too large does it begin scaling the image down, and it re-searches quality at every smaller size rather than simply shrinking until it fits.

One format note worth knowing: PNG is lossless, so a quality setting does nothing to it. Hitting a size target with PNG is possible only by reducing dimensions. For photographs, WebP or JPEG will always get you further.

Frequently asked questions

Drop the file into the box above. The target is already set to 200 KB, so the tool searches for the highest quality that still fits and applies it. Nothing is uploaded — the whole thing runs in your browser.

At this size a typical photograph usually needs no downscaling at all — the quality search alone gets there, often landing above quality 80. That makes 200 KB the sensible target for the one image on a page that has to look good at full width. It is worth knowing the trade though: a 200 KB hero is two 100 KB in-article images, and on a slow connection the hero is what delays the page.

At 200 KB you can expect about 1,740 × 1,310 pixels, usually with no resizing needed at all. The tool always exhausts the quality range before it reduces resolution, so it gives up as little as the target allows.

WebP produces the smallest file at a given quality and is supported by every current browser. Choose JPEG if something specifically requires it, such as an older upload form. PNG is lossless, so a size target can only be met by reducing dimensions — avoid it for photographs.

No. Compression happens in a canvas element on your own device, so the file never leaves your computer. That also means there is no upload wait and no size cap.