Need an image under 200 KB? Pixels first, then quality

2026-10-16

A form wants your photo under 200 KB — a passport-style picture for an application, a profile image, an attachment field with a small limit. Your photo is 3 MB. You open a compressor, drag the quality slider down as far as you dare, and land at 900 KB with a picture that already looks rough. The slider has run out of road.

It ran out because it was the wrong lever to start with.

Two different things make a file big

A photo's file size depends on two things:

• How many pixels it has — its width times its height.
• How much space each pixel's detail takes — which is what the quality setting controls.

The quality slider only works on the second one. On a modern phone photo with millions of pixels, even a low quality setting still has to describe every one of them. That's why compression alone stalls: you can't squeeze millions of pixels into a few hundred kilobytes without the picture falling apart.

Pixel count is the big lever, and it works on area: halve the width and height and there are a quarter as many pixels to store, so the file drops roughly in proportion. Most forms with a 200 KB limit display the image small anyway; the extra pixels were never going to be seen.

Step 1 — cut the pixel dimensions

Open the resize tool, keep Keep aspect ratio on, and set a width. If the form states dimensions, use them. If it doesn't, pick something modest for what the image is: the common-widths buttons offer 1280, 800 and 640, which are sensible starting points for a document photo or an avatar. Resizing down never blurs the way enlarging does; you're only discarding pixels nobody would see.

Step 2 — compress

Take the resized file to the compressor. It keeps the dimensions exactly as they are and re-encodes at the quality you choose: Smaller (62), Recommended (82) or High quality (94), or anywhere from 40 to 100 on the slider. Start at Recommended and look at the size it reports.

• Under the limit? Done.
• A little over? Try Smaller before you touch the dimensions again.
• Far over? Go back to step 1 and choose a smaller width. That will do more than any quality setting.

If you have several images to prepare, batch edit does both steps in one pass: switch on Resize (choose Long side so portrait and landscape photos end up the same size) and Compress, and every image is resized and then compressed on save.

Reading the number correctly

Our size readout counts a kilobyte as 1,024 bytes. If the form means 200,000 bytes — and you can't usually tell — a file we show as 195KB can already be over. Aim for 190KB or less on our readout and the question doesn't arise. (The megabyte mismatch post explains why.)

If the image is a PNG

For a PNG, the compressor keeps the PNG format and the quality setting chooses a colour palette — 256, 128 or 64 colours — instead of a JPG-style quality. That works beautifully on logos and screenshots and poorly on photographs. A photo saved as PNG should become a JPG first: convert it, then follow the two steps above. (Only do that if it doesn't need a transparent background — JPG fills transparency with white.)

Why there is no "make it 200 KB" button

Our compressor doesn't have a target-size mode, and we'd rather say so plainly than imply one. Hitting an exact size automatically means the tool choosing your quality, and often your dimensions, for you — and when the result looks worse than expected, you can't see which decision caused it. With two explicit steps, you always know what you traded for those kilobytes.

The short version

• The quality slider alone can't get a large photo under 200 KB.
• Resize first (keep the ratio), then compress at Recommended or Smaller.
• Still over? Smaller dimensions beat lower quality.
• Aim for 190KB on our readout to clear a 200 KB limit whichever way it's counted.