Compress an Image to 200 KB
Enough room that an ordinary photograph keeps most of its resolution, and a portrait keeps all of it.
Runs on your device — photos are never uploadedDrop your images here
or click to browse — as many as you like
JPG · PNG · WebP · HEIC
75% is the usual sweet spot for photographs. Below about 50 the edges start to smear.
The tool hunts for the quality that lands there. Government forms commonly cap uploads at 500 KB or 1 MB.
JPG opens absolutely everywhere. The safe choice for photos.
Resizing shrinks a file far more than quality does. A phone photo is often 4000 px wide when 1600 would do.
Every image is decoded in memory, so a hundred phone photos at once will strain a phone. Work in batches of a few dozen if it slows down.
How it works
Three steps, no account, and the photos never leave your computer.
Drop the images in
JPG, PNG, WebP or an iPhone HEIC. Several at once is fine — each one is compressed to the same limit independently.
The target is already set to 200 KB
Change it if you need a different number. The tool searches for the largest picture that fits underneath, rather than making you guess at a quality dial.
Save
One at a time, or all together as a ZIP. The result line reports the size it reached and the dimensions it settled on.
Where a 200 KB limit comes from
Uploading identity or address documents
Portals that accept a photograph of a document but cap the file, where the text still has to be readable at the other end.
Product photographs for listings
Large enough to zoom a little, small enough that a page of thirty still loads quickly.
Presentations and reports
Keeping every image near 200 KB is what stops a slide deck reaching the size where email rejects it.
Content management systems
Many enforce a per-image cap in this range, and simply refuse the upload above it.
Where photographs stop losing pixels
Two hundred kilobytes is the point at which the tool stops having to shrink most pictures.
In testing, a portrait came through at its full 4,000 by 3,000 — no resolution lost at all, only quality reduced to a level that is invisible on screen. An ordinary phone snapshot held 3,108 pixels wide. Only genuinely dense images, the ones full of foliage or fine texture, still had to give up size.
What you get back at 200 KB
| Test image (all 4000 × 3000) | Original | At 200 KB |
|---|---|---|
| A portrait on a plain background smooth skin and an even backdrop, which JPEG stores very cheaply | 1.8 MB | full 4000 × 3000 |
| A typical phone snapshot sky, buildings, ground texture — the ordinary case | 2.6 MB | 3108 × 2331 |
| A scanned page of text thousands of hard black-on-white edges, which JPEG handles badly | 1.3 MB | 2569 × 1926 |
| A dense outdoor scene foliage, fine detail everywhere, the worst case for any compressor | 3.3 MB | 1157 × 867 |
Measured by running this tool's own search against four 12-megapixel test images built to bracket the range from very compressible to barely compressible. Your photograph will land somewhere inside it.
What "quality 58" means and why you should not worry about it
JPEG quality numbers are not percentages of anything. Quality 58 does not mean the picture is 58% as good; it is a position on a dial whose effect depends entirely on the image. On a smooth portrait, quality 58 is indistinguishable from the original at normal viewing distance. On a screenshot full of text, the same setting is visibly muddy.
This is why the tool searches for the number rather than asking you to guess it. You care about the file size and about the picture still looking right; the quality figure is an implementation detail that happens to land wherever it needs to.
Scanned documents behave differently
If you are compressing a scan of a printed page, 200 KB will hold roughly 2,500 pixels across in testing — enough to read comfortably. But JPEG is not the natural format for text: it puts a faint grey halo around every hard edge. If the destination accepts PDF or PNG, either will usually be both smaller and cleaner for a document than a JPEG at the same size.
How the tool finds the size
It searches, rather than guessing. Quality is bisected to find the highest setting that still fits, and if no quality setting fits — which is normal at small targets — the picture is scaled down and the search runs again, until the largest version that fits under the limit is found.
That ordering matters. Turning quality to the floor on a full-size image produces something both ugly and, very often, still over the limit. Fewer pixels at a decent quality is the better trade almost every time, and it is the one this tool makes.
If a target genuinely cannot be reached, the result is shown in red with what it missed by, rather than handed back in green as though it had worked.
Nothing is uploaded
The compression happens in your browser, using your own processor. The photograph is never transmitted, which means there is no queue, no file-size ceiling imposed by a server, and no copy of your picture sitting on somebody else's disk afterwards.
It also means the tool works with no connection at all once the page has loaded.
Common questions
Will a 200 KB image keep its full resolution?
Often, yes. A portrait held its full 4,000 by 3,000 in testing and an ordinary snapshot held 3,108 pixels wide. Detailed images — foliage, texture, crowds — still have to shrink, because there is genuinely more information in them to store.
Is 200 KB enough to read a scanned document?
Yes for a single printed page — around 2,500 pixels across in testing, which is comfortably readable. If the destination accepts PDF or PNG, either handles text better than JPEG, which softens hard edges.
Why does the tool sometimes go under the target by a lot?
It never does by much. The search stops at the highest quality that still fits, so the result normally lands just under the limit — 197 KB for a 200 KB target is typical. A result far below usually means the original was already small.
Are my photos uploaded anywhere?
No. The compression runs in your browser on your own processor, so the image never leaves the machine. There is no queue, no server-side size ceiling, and no copy left behind afterwards.
Can I compress a batch to 200 KB at once?
Yes. Drop in as many as you like and each is compressed to the same target independently, then saved individually or together as a ZIP.
More tools
Every one of them runs on your device. No uploads, no accounts.