How to Compress a PNG to 200 KB
PNG is lossless, so there is no quality dial to turn down — the only real lever is resolution. On a 1920x1280 test image, hitting 200 KB required downscaling to 22.5% (about 432x288). If the image must stay visually sharp at full size, switch to WebP or JPEG instead.
Measured Data
| Step | Value |
|---|---|
| Source size (PNG, full resolution) | 2673.4 KB |
| Target ceiling | 200 KB |
| Encoder passes | 8 binary-search rounds |
| Scale the encoder settled on | 0.225 (approx. 432x288) |
| Final size | 196.8 KB |
| Deviation from target | -3.2 KB |
| Encode time | 84 ms |
| Codec | image/png (lossless, no quality parameter) |
The Mental Model: PNG Has No Quality Setting
Most "compress this image" advice assumes a quality slider. PNG does not have one. It is a lossless format: the encoded file decodes to exactly the pixels you put in, bit for bit. There is no trade you can make between fidelity and size inside the format.
That leaves two levers:
- Resolution — fewer pixels means fewer bytes, always.
- Content — how well the pixels compress, which you can only change by editing the image.
So when you ask for "a PNG under 200 KB", what you are really asking is "how many pixels fit in 200 KB". The answer depends entirely on the image.
What the Measurement Shows
Running a 1920×1280 photographic test image through the encoder with a 200 KB ceiling produced this:
| Lever available | Value |
|---|---|
| Source PNG at full resolution | 2673.4 KB |
| Resolution scale that fit the ceiling | 0.225 |
| Effective pixel dimensions | ~432 × 288 |
| Result | 196.8 KB, reached in 8 passes |
The encoder did exactly what it could: it halved the scale eight times over and settled on the largest size that still fit under 200 KB. Note what it did not do — it did not "compress harder". The 2673 KB PNG and the 197 KB PNG use the same algorithm at the same settings. One simply has 97% fewer pixels.
A 432×288 image is still perfectly usable for a thumbnail, a chat preview, or a form attachment. It is not usable as a print asset or anything containing small text.
When PNG Is the Wrong Answer
If the goal is "this image must be under 200 KB and must stay at full resolution and must look good", PNG cannot get you there. Nothing can, at that size cap. You need a codec that trades some fidelity for a lot of bytes:
| Codec | 1920×1280 → 100 KB | Resolution kept | What you give up |
|---|---|---|---|
| JPEG | 93.5 KB, 8 passes | full | fine detail at high zoom; no alpha |
| WebP | 84.2 KB, 8 passes | full | a few older viewers; no alpha loss |
| PNG | would need ~0.2 scale | ~1/5 of pixels | resolution itself |
For photographs, JPEG or WebP at full resolution is almost always the better answer. The practical rule: use PNG when the image has flat colour and sharp edges (logos, UI, charts, screenshots), and use JPEG or WebP when it has continuous tone (photos, gradients, scanned art).
Where PNG Does Win
PNG's lossless nature becomes an advantage when the image is already highly compressible:
- Screenshots — large uniform regions, repeated UI chrome. Often 60-80% smaller with zero change.
- Flat illustrations and logos — a handful of colours, long runs of identical pixels.
- Images that need transparency — PNG's alpha channel is exact. JPEG has none, and WebP's is lossy alongside the colour.
- Anything that will be edited again — lossless means you can re-open and re-save without generational loss.
In those cases you may not need to hit a KB target at all; a plain re-save through a lossless optimiser is enough.
If You Are Hitting a Form's 200 KB Limit
Upload forms that cap PNGs at 200 KB are usually portals accepting scans, ID documents or certificates. Two things matter more than the number:
- Check the pixel minimum first. Many portals reject anything under a stated resolution, and a downscaled 432×288 will fail that check even though the file size is perfect. Fix resolution, then compress.
- Check the format list. If the port accepts JPG, convert — you keep full resolution and meet the cap. Most of these forms accept both.
The compressor on this site lets you set the target in KB directly and does the search for you, so you are not guessing at a quality value.
Run it on your own file
This page explains the mechanism. The tool applies it — nothing is uploaded.
FAQ
Why can't I just lower the quality like I do for a JPEG?
Because PNG has no quality parameter — it is a lossless format, every pixel is reproduced exactly on decode. The bytes it occupies are decided by pixel count and how well the image compresses. So a 200 KB ceiling can only be met by removing pixels, or by changing to a codec that does allow loss.
Does downscaling make the image blurry?
It reduces detail permanently, yes. Going from 1920x1280 to roughly 432x288 keeps the image recognisable and colour-accurate but discards fine texture and text legibility. If the target image contains text or thin lines, downscaling will hurt more than the compression story suggests.
What should I use instead if quality matters?
WebP first, JPEG second. Measured on the same test image at the same 100 KB budget, JPEG landed at 93.5 KB and WebP at 84.2 KB — both at full 1920x1280 resolution, no downscale at all. That is the trade PNG cannot offer.
Which PNG images compress well on their own?
Screenshots, flat illustrations, logos, charts and anything with large uniform areas. Those often shrink by 60-80% with no change at all, because PNG's filter plus DEFLATE excels at repeated pixel runs. Photographs of real scenes are the opposite case — grain and gradients defeat it.
Is the compression done on my device or on a server?
On your device, in the browser tab. The encoder runs on a Canvas element and never sends the file anywhere, so there is no upload step, no queue and no copy of your image on someone else's disk. You can disconnect from the network after the image is loaded and it still works.