Compress a Photo to 50 KB

• Works the quality of a JPEG or WebP down as far as 50, which is where the blocking starts to show around eyes and lettering.
• Takes a fifth off each side once that floor is reached, so an untouched phone frame gets under 51,200 bytes by giving up pixels.
• Reports the pixel size it finished on beside the byte figure, so you can check it against the box an application form asked for.

• Cannot land on an exact width a portal demands, because the steps are fixed — type those pixels in first when one is named.
• Never moves the width or height under Keep the dimensions; quality becomes the only lever, at the size the picture arrived at.
• Applies no lossy pass to a PNG scan: the PNG encoder here is lossless, so a certificate gives up pixels rather than fidelity.

1. Start from the numbers the form gives you. Note the byte ceiling, and note any width and height beside it. If exact pixels are named, set those before you compress anything; if only the ceiling is stated, this page can pick the dimensions for you.
2. Add the photo or the scan. Drag a JPEG, PNG or WebP into the panel above, or pick one from your files. It is read where it already sits, so there is no waiting for a transfer.
3. Run it with fit under the target. The target already reads 50 KB and the policy already reads fit, so press the Compress image button. Quality is searched first, and the picture is only stepped down if the search runs out of room.
4. Read the dimensions, not only the size. The result gives you three figures: how many pixels the picture ended up with, how many bytes it weighs, and the quality that got it there. Check the pixel size is still big enough for whatever you are filling in, then download it.

50 KB is 51,200 bytes, and eight bits to the byte makes 409,600 bits for the whole picture — every pixel of it, colour included. Share that out across the pixels you plan to keep and you have the real answer to whether 50 KB is generous or absurd, long before any encoder is involved.

Those sizes are illustrations, not rules — read whatever you are filling in for the figures it actually wants. What the arithmetic settles is the direction of travel: below roughly half a bit per pixel a photographed face starts to smear, and no compressor invents its way out of that. Fewer pixels, described properly, beat a lot of pixels described badly.

Plenty of application forms name two numbers rather than one: a ceiling in kilobytes and a photo size in pixels, sometimes with a minimum as well as a maximum. Some portals show the pixel figure only in a help sheet beside the field, or in a note under the file picker, so it is worth a look before anything is compressed.

Where an exact width and height are asked for, dial them in with the resizer first and bring the finished file back here. The shrinking on this page moves in fixed steps and aims only at the byte figure, so it has no way of stopping on somebody else’s number — when a portal is checking the pixels too, type them in yourself rather than hoping the automatic steps land on them.

Where only a byte ceiling is given, there is nothing to look up and nothing to set. Add the picture and let the policy choose the dimensions; the figures it settles on are printed with the result, so you can still see what you are about to attach.

Two policies sit above the target. Fit under the target, which is the one selected here, is allowed to make the picture smaller. Keep dimensions is one tap away and refuses to touch the width and height at all.

Under the fit policy the quality dial of a JPEG or WebP is searched first, and it stops at 50: below that the tell-tale squares appear around eyes and lettering, and a portrait that has gone mottled is no more use to a form than one that is too big. If quality 50 at the original size still overshoots, a fifth is taken off each side, the search runs again at the new size, and that repeats — eight steps at most, and never past 32 pixels on the short side.

Nothing about that happens quietly. The policy is a control you can see and change, and the result states in plain words when the dimensions came down, alongside the pixel figures, the byte figure and the quality that produced them. Switch to keep dimensions and the width and height are guaranteed instead: quality alone moves, and if 50 KB genuinely cannot be reached that way you are given the smallest size the picture managed rather than a file that misses the ceiling.

An encoder spends its bits where neighbouring pixels disagree with each other. A face lit evenly against a blank wall is mostly gentle gradient, which costs almost nothing to describe, so nearly the whole budget goes on the eyes, the hairline and the mouth — the parts anyone looking at the photo will actually judge.

Put a bookcase, a patterned curtain or a busy street behind the same head and every one of those edges competes for the same 51,200 bytes. That is why two portraits at identical dimensions can come out at very different sizes, and why moving a step in front of a plain wall does more for a tight target than any setting on this page. Even lighting helps for the same reason: a hard shadow across the background is detail too.

A scan usually arrives with things around the document that nobody asked for: the lid of the scanner, a strip of desk, the shadow down one edge, the corner of whatever was underneath. All of it is texture, all of it is charged for, and none of it is the certificate. Trim it to the document before compressing and the same 50 KB is spent entirely on the part that has to stay readable.

A PNG has no quality dial in this build — the encoder is lossless, so there is no knob to turn down and a search would hand back the same file every time. Under the fit policy a PNG is therefore stepped down in size instead, losslessly, until it fits, which suits flat black-on-white lettering better than it suits a face. Choose keep dimensions and WebP is offered instead, which reaches the number at the full pixel size.

If what you have is really a photograph that happens to be saved as a PNG, it is worth changing it over first: make it a JPEG and the quality search becomes available again, which usually means keeping more pixels than the lossless route can.

• The automatic shrink moves in fixed steps, so it cannot land on an exact width and height a form has asked for.
• JPEG and WebP quality is held at 50 or above under this policy, so a very large photograph gets under 50 KB by giving up pixels rather than by turning blocky; a PNG has no quality dial and is shrunk losslessly.
• The stepping stops after eight goes, or once the short side reaches 32 pixels, and you are told plainly if the target was still missed.