How to Compress an Image to 200KB
At 200KB a form-sized picture keeps all its pixels and loses almost nothing; a full phone photo still has to give some up. The aim is to shed bytes without throwing away more pixels than necessary.
200KB is roomy for a form photo, tight for a phone photo
200 KB is 1.6 million bits. A 1080 × 1350 picture (about 1.46 million pixels) then has roughly 1.1 bits per pixel, a comfortable budget for an ordinary photo. A 12 MP phone photo has about 0.13 bits per pixel, which is not.
So the goal at 200KB is different from the 20 or 50 KB limits: you are no longer forced to make the picture tiny, and the job is to hit the size without shrinking it more than needed. In Compress Image that is the default behaviour of Target size mode: it keeps the highest quality that fits and shrinks pixels only when quality alone can’t do it.
Steps
- Add your picture and choose Target size, with a maximum of 200 KB.
- If you need the dimensions to stay exactly as they are, open Advanced and turn on Keep the pixel size. The tool then lowers quality only, and tells you if 200 KB can’t be reached that way.
- Compare the original and result sizes, the compression quality, and (for same-shape results) the visual similarity score.
If the file is a photo from a recent phone, expect the biggest saving. Those files are often several MB because of the pixel count, not because the picture needs that much detail.
A measured example
We ran a generated 3000 × 4000 test image (2.1 MB) through Target size mode with a 200 KB maximum and the default settings. Chromium gave 176 KB at 2550 × 3400 pixels; Safari’s engine gave 174 KB at the same pixel size. So even at 200 KB, a 12 MP photo gave up about 15% of its width and height, and the tool flagged the compression as heavy. A smoother picture, or a smaller original, would keep all its pixels. This is a generated image; a real photo will land differently.
The PNG screenshot trap
Screenshots and graphics saved as PNG can be small already, so don’t convert them. A real example from WillItUpload’s own testing: a 103 KB PNG screenshot was turned into a 177 KB JPG by an earlier version, even though it already met a 200 KB limit. The tool now returns any file that is already within the limit untouched, whatever its format.
Conversely, a photo saved as PNG is usually far over 200 KB. PNG keeps every pixel, so only fewer pixels make it smaller. For photos, save as JPG. See PNG vs JPG for online forms.
The Safari difference
The same JPEG quality number is not the same thing in every browser. In WillItUpload’s real-photo tests, portrait photos aimed at 200 KB landed at 367 KB in Safari at the default quality floor, because Safari’s JPEG encoder maps the quality number to file size differently from Chrome’s.
The tool handles this: if the default floor can’t reach the limit, it tries a stronger setting, and keeps that result only if the measured visual similarity to the original stays at 90% or more. The practical lesson: don’t copy a quality number from someone else’s screenshot. Target the size and read what quality it needed in your browser.
If you still can’t reach it
- Check whether the portal also fixes dimensions. If so, KB + Dimensions handles both together.
- If the file is HEIC from an iPhone, Convert to JPG accepts it directly, with an optional KB limit.
- If the tool reports that the target was too aggressive, raise the limit or allow lower quality and inspect the picture before using it.