SqueezeKB

Compress an image to 200KB

200 KB is enough for a clean photo roughly 1000–2000 px wide, depending on detail. Full-size phone photos are reduced just enough to fit at 60% quality; smaller images often keep their original size.

Drop an image here

or paste it (Ctrl/⌘ + V)

JPG or PNG

Target size

Your image is processed on this device. It is never uploaded.

Real example: a photo compressed to 200 KB

These are not mock-ups. The photos below were run through this exact tool, and the result is the file you would get. Switch photos to compare an easy case and a hard one.

Garden with a split-rail fence and white houses, compressed to 200 KB
Original
7.15 MB · 4032 × 3024 px
Result
194.7 KB · 1040 × 780 px · quality 60%
Saved
97.3%

The tool kept JPG quality at 60% and reduced the pixel dimensions just enough to fit. Below about 60% quality, JPG shows blocky artefacts, so a slightly smaller, clean image is the better trade.

Zoomed in: same area, before and after

Detail of the original photo at full resolution: house, window and leaves
Original, 100% (crop)
The same detail cut from the compressed file and enlarged to the same size
200 KB file, same area enlarged ×3.9

Download this exact file (194.7 KB)

Photo: 89Traveler, CC0 1.0, via Wikimedia Commons. Made with this tool in Chromium 156.0.8078.4. Other browsers’ JPG encoders give slightly different results.

Why 200 KB is a comfortable target

In our real examples, a detailed 12-megapixel phone photo of a garden fits 200 KB at 1040 px wide, and a simpler 20-megapixel food photo at 2031 px, both at 60% quality. That range makes 200 KB a popular limit for document portals, marketplaces and blog uploads.

Because the tool searches for the highest quality that fits, you get a file close to 200 KB rather than an unnecessarily tiny one.

Common situations

  • Upload portals that cap images at 200 KB.
  • Product photos for listings where page speed matters.
  • Sending several photos by email without hitting attachment limits.

How the target-size compression works

  1. Your browser decodes the image (EXIF orientation is applied, metadata is not carried over).
  2. For JPG output we search for the highest encoder quality between 60% and 95% that fits under your target.
  3. If even 60% quality is too large, we reduce the pixel dimensions just enough to fit at 60%. Below about 60%, JPG shows blocky artefacts, so a slightly smaller, clean image is the better trade. Only for very small targets does quality go lower, never below 30%.
  4. The search stops after a fixed number of attempts or about 20 seconds, so a phone never locks up. If the target was not reached, you get the closest result and an honest warning.

Frequently asked questions

Is my image uploaded to a server?

No. The image is read into your browser’s memory, compressed with the browser’s own canvas encoder, and handed back to you as a download. There is no upload endpoint at all. You can check this yourself in your browser’s developer tools (Network tab) — the privacy page shows how.

Will my photo lose resolution?

A full-size phone photo, yes: at 200 KB it typically ends up around 1000–2000 px on the long edge (still plenty for screens). Images that are already moderately sized, for example 1200 px wide, often fit without resizing. The result panel shows the final width and height so you can check.

What if the image can’t get under the target?

You’ll see the closest size we managed and a clear message that the target was not reached. We never label a file as “done” when it is over the limit. Larger targets, JPG output or a smaller source image usually solve it.

Will the result be accepted by the site I’m uploading to?

This tool changes file size and pixel dimensions only. It does not check whether a photo meets any organisation’s or form’s content rules (background, framing, etc.). Always check the requirements of the site you are uploading to.