The form says photo must be under 50 KB. Your phone photo is 3.8 MB, about 76 times too big. To reduce image size in KB that far without ending up with a blurry smudge, do three things in a fixed order: crop, resize, then compress. Most people jump straight to the compression slider and wonder why the face comes out as blocks. This guide covers why the order matters, how much each step saves, and the one unit mismatch that gets correctly sized files rejected anyway.
Why file size in KB depends on pixels first
A JPEG's size is driven by how much detail it has to describe, and detail scales with pixel count. A 12-megapixel phone photo (4000 × 3000) holds twelve million pixels. A typical application photo needs perhaps 200,000 (for example 400 × 500). Throwing away 98% of the pixels you will never display costs nothing visible. Squeezing all twelve million into 50 KB forces the encoder to discard detail everywhere, which is where the blocky, smeared look comes from.
So the quality slider is the last tool you reach for, not the first. Here is what each step typically buys on a phone photo:
- Crop to the subject. Removing background around a portrait or the desk around a document often cuts 30–60% of the pixels.
- Resize to the dimensions the form actually displays. Going from 4000 px to 800 px wide removes 96% of the pixels, and file size falls roughly in step.
- Compress with JPEG quality. Moving from 92% to 70% typically halves the file again with little visible change.
How to reduce image size to 20 KB, 50 KB, or 100 KB
- Crop first. Open the photo in the image cropper and cut it down to what the form wants to see: head and shoulders for an ID photo, just the ink for a signature. If the portal gives an aspect ratio, crop to that now, so it is not squashed later.
- Set a target size, not a quality number. In the image compressor, click the preset that matches the form (20, 50, 100, or 200 KB) or type any limit into the custom KB box. The compressor then finds the size for you rather than making you guess a quality setting (see below for how).
- Check the exact byte count. With a target set, the compressor shows the result in bytes, and it counts a kilobyte as 1,000 bytes, so a "20 KB" result is under 20,000 bytes. The next section explains why that matters: it is the most common cause of a "file too large" error on a file that looks correctly sized.
- Check the result before downloading. The tool shows the final size and pixel dimensions. If the portal also demands specific dimensions (for example 200 × 230 pixels), confirm those match too. A size limit and a dimension limit are separate checks.
The KB trap: 20 KB is not always 20 KB
"Kilobyte" means two different numbers depending on who is counting. Windows File Explorer, and many upload scripts, count a kilobyte as 1,024 bytes. macOS Finder, phone file managers, and plenty of web forms count it as 1,000 bytes. So a limit of "20 KB" might mean 20,480 bytes or 20,000 bytes, and a file of 20,300 bytes passes one check and fails the other.
The difference is only 2.4%, but upload limits are hard cut-offs, and target-size compressors deliberately land just under the number you give them. A compressor that counts 1,024 bytes per kilobyte can hand you a 20,400-byte file labelled "under 20 KB" that a stricter form then rejects. WebToolNook's compressor targets the smaller, 1,000-byte definition, so its output passes both. With any other tool, ask for a little under the limit, such as 19 KB for a 20 KB cap, which satisfies both definitions and costs nothing you would notice.
How a target-size compressor actually finds the number
JPEG has no "make this 50 KB" setting. File size is a side effect of the quality value, and the relationship is not a straight line: dropping quality from 90% to 80% saves far more than dropping it from 50% to 40%, and the exact curve depends on the photo. A smooth sky compresses effortlessly, while gravel or foliage fights back at every quality level.
So WebToolNook's compressor searches. It encodes the image, checks the size, and narrows the quality range by halves, keeping the highest quality that still fits under the target. Seven rounds pin the quality within about half a percent. If even the lowest quality it is willing to use (35%) is still too big, it shrinks the pixel dimensions by an amount estimated from how far over the target it landed, and searches again, for up to five rounds. That second stage is how a 4 MB photo can reach 20 KB without you resizing it by hand.
It also explains a behavior that surprises people: PNG cannot be tuned this way. PNG is lossless, so it has no quality setting to search. For a PNG, the only lever is fewer pixels, so a target-size PNG comes out much smaller in dimensions than the same image as JPEG. If the form accepts JPG, use JPG. Everything happens in your browser, so the ID photo or signature you are shrinking never leaves your device.
What to do when it still won't fit
Scanned signatures (usually 10–20 KB limits)
A signature should be the easiest file to shrink: dark ink, white paper, almost no detail. In practice a phone photo of a signature carries grey paper texture, shadows, and noise, all of which JPEG spends bytes describing. Crop tightly to the ink, then compress. If the paper looks grey or textured, retake the photo in even daylight with the page flat. A cleaner source will compress far better than any setting you can choose afterwards.
Passport and ID-style photos (often 50 KB or under)
Here the face has to survive, so do not let the compressor reach the target by crushing quality. Crop to head and shoulders and resize to the portal's stated dimensions first. At around 400 × 500 pixels, 50 KB is generous, and the compressor can stay at a high quality. If a result looks blotchy around the eyes, the pixel dimensions are still larger than they need to be.
Photos from an iPhone
iPhones save HEIC by default, which many portals reject outright whatever its size. The compressor accepts HEIC and can save the result as JPG. You can also convert separately with the HEIC to JPG converter and then compress.
Documents photographed for upload
Multi-page documents are usually better as a PDF. Put the photos into a document with JPG to PDF, then shrink it with the PDF compressor, which handles photographed pages well because each one is just an image.
A quick reference
- Under 20 KB: crop hard, aim for 200–300 px on the long side, JPG only. The 20 KB compressor has the target preset.
- Under 50 KB: about 400–600 px on the long side, and quality usually stays above 70%. Use the 50 KB compressor.
- Under 100 KB: about 800–1000 px on the long side for photos; documents stay readable at around 1200 px. Use the 100 KB compressor.
- Always: check the portal's dimension rules separately from its size rule.
If you want the background behind the format choice (when WebP beats JPG, and why resizing beats every quality setting), read compressing images without visible quality loss.