TryImager

Reduce Image to 200KB

200 KB is the target to pick when nothing is forcing your hand. It is small enough to load in well under a second on a middling mobile connection, and large enough that a well-shot photograph keeps its texture at full screen width. Content management systems, forums and marketplaces that set a limit at all tend to set it here.

Processed in your browser

Drop your image here

or choose an image from your device

Accepts JPG, PNG or WEBP · No fixed size limit — we adapt to what your device can handle. Very large files may take longer or show a warning.

Need a different file size?

Reduce Image to 50KBStay under 50 KB, quality and size tuned automaticallyReduce Image to 100KBStay under 100 KB, quality and size tuned automaticallyReduce Image to 500KBStay under 500 KB, quality and size tuned automatically

When you need this

  • A content management system that rejects media above 200 KB
  • Hero and banner images that must stay quick without looking degraded
  • Forms asking for a photo somewhere between 100 KB and 200 KB
  • Web pages with a per-image performance budget of 200 KB
  • Forums and marketplaces that cap uploads at 200 KB but display them large
  • Sending a set of photos by email without the client re-compressing them

The quality headroom you get at 200 KB

Doubling the budget from 100 KB to 200 KB does not double the quality, but it buys back most of what the tighter target costs. In practice a full-resolution phone photo that needed quality 0.5 for 100 KB usually fits 200 KB somewhere around 0.7–0.8, and that is the range where JPEG artefacts stop being findable without pixel-peeping.

That headroom matters most on three subjects: skies with smooth gradients, where low quality produces visible banding; text overlaid on an image, where edges smear early; and anything with fine repeating texture such as knitwear, brick or leaves.

Using 200 KB as a performance budget

If you are choosing the number yourself rather than obeying a form, think in page weight rather than per-image size. A page with one hero at 200 KB and six thumbnails at 20 KB each is around 320 KB of imagery, which is a reasonable total on mobile data. A page with six 200 KB images is not.

  • Hero or full-width photo: 200 KB is a sensible ceiling at up to about 1600 px wide.
  • In-article photo: aim lower, around 80–120 KB, and reserve 200 KB for the one image that carries the page.
  • Thumbnail or card image: anything above 40 KB usually means the source is larger than the slot it fills.

What the result panel is telling you

Original, Result and Saved are all measured from real byte counts — Result is the size of the exact file the Download button writes, not an estimate produced before encoding. If Saved shows a small percentage, the source was already well compressed and there is little left to take; forcing it lower will cost visible quality rather than wasted bytes.

Dimensions first, ceiling second

The order matters because the two settings interact. Choose 1600 px wide and the encoder has to spend 200 KB on 1.9 million pixels, roughly 0.1 bytes each, which is workable but tight on a detailed subject. Choose 1200 px and the same budget covers 1.1 million pixels at nearly double the density, so the quality search stops higher and the picture holds up better under zoom.

If you are unsure, start at the smaller width. It is easy to run it again at a larger size; it is not possible to recover detail after the fact.

Where 200 KB and dimensions collide

Certain subjects blow the budget at any reasonable width. Aerial photographs, dense foliage, textured fabric and anything with visible film grain all carry high-frequency detail that lossy compression cannot summarise cheaply.

  • If the result looks blotchy rather than soft, reduce the width by about a third and try again.
  • If the subject is a screenshot with text, keep the original dimensions and raise the target instead — text degrades faster than photographs.
  • If the image is a flat graphic, try PNG or WEBP output; lossless can beat 200 KB outright on images with few colours.

What you download is what was measured

The result is encoded once, measured as a real blob, and that same object is what the Download button writes. The size you read is therefore the size that arrives on disk — there is no second encode between the preview and the file, which is where most online tools quietly disagree with your file manager.

How to use it

  1. 1Add the image — it is read locally, so nothing is transmitted.
  2. 2The target is preset to 200 KB; change it if your destination specifies otherwise.
  3. 3Run the compressor and let the quality search settle.
  4. 4Check Result against your limit, view the preview at full size, then download.

Frequently asked questions

Is 200 KB small enough for a fast web page?

For one prominent image, yes. For every image on the page, no. Budget per page rather than per file: a single 200 KB hero plus small thumbnails loads quickly, while six 200 KB photos on one page do not.

My photo is already under 200 KB. Will compressing help?

Rarely, and it can hurt. Re-encoding an already-compressed JPEG discards more detail for a small saving. The result panel will show you the saving before you download — if it is only a few percent, keep the original.

Why does one photo hit 200 KB easily and another struggle?

Subject matter. Smooth areas such as skin, walls and skies compress extremely well; fine random texture such as foliage, gravel and water does not. Two images with identical dimensions can differ threefold in compressed size for that reason alone.

Can I use this for screenshots?

You can, but screenshots of text are better served by the Document Scan Compressor or by keeping them as PNG. Lossy compression smears the edges of small characters before it touches anything else in the frame.

Is my image uploaded to a server?

No. The file is decoded and re-encoded by your own browser using the Canvas API. It never leaves the device, there is no account, and closing the tab discards everything.

Which should I set first, width or target size?

Width. The pixel count decides how hard the encoder has to work; setting it first means the quality search starts from a realistic position and usually stops higher.

My resized image still will not fit 200 KB. What now?

The subject is probably high in fine detail — foliage, grain, fabric. Reduce the width by roughly a third and run it again. That removes about half the pixels and almost always clears the ceiling with quality to spare.

Is 200 KB at 1600 px better than 200 KB at 1200 px?

Not usually. The larger version spreads the same data over more pixels, so it shows more compression artefacts. Unless the image will be viewed at full resolution, the smaller dimensions look better at the same file size.

Does the tool sharpen after resizing?

No. Downscaling is done by the browser's own image pipeline with no added sharpening, so the output is a faithful reduction rather than a processed version of your photo.

Related guides

Related tools