Who Benefits From a 20 KB Photo Compressor (and How to Hit the Limit Without Ruining the Photo)
Reviewed by the FreeOnline.fyi team · Updated 2026-09-13
Who actually needs a photo under 20 KB
The instruction "photo must not exceed 20 KB" shows up on job application portals, exam registration forms, visa and ID uploads, university admission pages, and plenty of marketplace listings. It is almost never a design decision made recently — these caps are usually legacy, built for slow connections and fixed database columns, and they are enforced against the exact byte count of the file you upload, not against how the photo looks on screen.
That is why cropping, retaking, or picking a different photo from your camera roll rarely solves it. The number attached to the file has to move, and it has to move while the face in the picture stays recognisable. We built the Photo Size Compressor 20kb for that specific moment: you have one photo, a form just rejected it, and you need a passing file within a minute.
The people who get the most out of it tend to be job applicants and exam candidates filling forms at the last minute, students uploading ID photos, sellers adding listing images with tight caps, landlords and teachers working from a phone, and anyone on a locked-down work laptop where installing an image editor is not an option. The tool runs entirely in the browser tab — nothing is uploaded to a server, there is no account, and nothing is stored.
What compressing to 20 KB really does to a photo
Under the hood we decode the image into a canvas and re-encode it repeatedly, searching for the highest quality setting that still fits inside your target budget. If quality alone cannot get the file small enough, we step the longest edge down and try again. On the Auto setting we start from the original resolution and only reduce as far as necessary; you can also pin the long edge at 640, 1024, 1600 or 2400 pixels if you want to control the trade-off yourself.
In practice, a typical 3–5 MB phone photo that is 4000 pixels wide will usually land at roughly 640 pixels on the long edge, with JPEG quality somewhere in the middle of the scale. For a head-and-shoulders portrait that is still perfectly usable and the face reads clearly. Force the same 20 KB budget onto a 1600-pixel frame instead and the encoder has to drop quality close to the floor, which shows up as blocky patches around edges and colour banding across skin tones.
Format matters too. WebP generally holds noticeably more detail than JPEG at the same byte count, so if the form accepts it, you get a slightly cleaner result. But a large share of portals only accept .jpg, and a WebP upload will be rejected for its extension regardless of how good it looks — so when the form says JPG, keep JPEG selected.
Choosing the target size and the maximum dimension
Twenty kilobytes is the default because it is the number forms ask for most often, but there are 50, 100 and 200 KB presets and a custom field from 5 to 2000 KB. The rule we would give anyone: compress only as far as the form demands. If the cap is 100 KB, use 100 KB and keep the extra detail. There is no prize for submitting the smallest file.
Auto dimension is the sensible starting point, but pinning a value helps in two situations. If you know the display size of the form's upload box — say 300 by 400 pixels — there is no reason to ship a 1600-pixel file, and pinning 640 gives the encoder more quality headroom. Conversely, some portals enforce a minimum dimension as well as a maximum size, so if yours demands at least 600 pixels or a specific ratio, pin the dimension rather than letting Auto shrink past it.
If your subject is not a face, 20 KB is often the wrong target. Document scans, signatures, receipts and screenshots of text lose legibility fast at that budget because sharp edges are expensive to encode. For those, a 50 KB JPG compressor gives you room for type and handwriting to survive, and if the scan is already wrapped in a PDF, our 50 KB PDF image compressor handles the page content directly.
Transparency, metadata, HEIC and other quiet failures
If you bring a PNG with transparency, JPEG cannot store it, so the transparent areas are flattened onto white. That is fine for a logo designed for a white page and wrong for a cut-out that was meant to sit on a coloured background. The format toggle lets you choose WebP instead, which does keep transparency, but only if the receiving form accepts it.
The metadata checkbox is labelled the way it is on purpose. Re-encoding through a canvas always strips EXIF — camera model, timestamps, GPS coordinates — so ticking the box does not re-insert anything; there is nothing left to re-insert. That is usually good for privacy, since phone photos can carry location data. What you should still check is orientation: most modern browsers apply the EXIF rotation when they decode an image, but not every combination of browser, camera and format behaves identically, and a sideways photo is the most common way a technically flawless 20 KB file still gets rejected. Look at the before-and-after preview before you download.
Two inputs are refused with a clear message rather than a silent failure: HEIC/HEIF files straight off an iPhone, which browsers cannot decode, and SVG, which is vector artwork rather than a raster photo. For HEIC, switch the camera to "Most Compatible" in iOS settings or export the photo as JPEG first. Uploads are also limited to a single file of up to 25 MB.
Reading the result, and verifying before you submit
The result panel gives you three things you should actually look at: the image itself, a size readout of before-in-KB to after-in-KB with the percentage saved and the quality level used, and a status line. "Under 20 KB ✓" means the budget was met. A message like "best achievable: 27 KB at 640px" means we ran out of headroom — the original was small or awkward enough that even the minimum dimension could not squeeze under the cap without destroying the picture. In that case either lower the pinned dimension or switch to WebP if the form allows it.
One deliberate design choice worth knowing: we aim slightly below the target rather than landing exactly on it, because portals disagree about whether "20 KB" means 20,000 bytes or 20,480. Sitting a little under covers both readings. That is not a guarantee, though — check the downloaded file's size in your file manager, and if the portal has its own validator, run the file through it before you finalise the submission.
Size is only one of the rules these forms enforce. Also confirm the accepted extension, any minimum pixel dimensions, and whether the form expects a separate signature image or a photo with a specific background. Getting under 20 KB is usually the hardest part, but it is rarely the only requirement.
What this tool is not good for
Twenty kilobytes is a submission format, not a master copy. Do not overwrite your original, and do not use the compressed file for printing, archiving, or posting anywhere that values image quality — a 20 KB portrait has real, visible limits, and no amount of careful tuning removes them. Keep the full-resolution original and re-compress from it whenever a new form asks for a different size.
It is also not the right choice for text-heavy material where legibility matters, for HEIC or SVG inputs, or for bulk work — it processes one photo at a time, and you drop the next one in when you are done. Within those boundaries, it does one job quickly and predictably, and the photo never leaves your device.