TL;DR
Application portals cap photo uploads at an exact size — commonly 20 KB, 50 KB, 100 KB, or 200 KB — and reject anything over it without saying by how much. Guessing with a quality slider is the slow way. Instead, work backwards from the number: state your target in KB and let the tool find the highest quality that fits.
The specific frustration
You're filling in an exam registration, a visa application, or a job portal. The instructions say:
Photograph: JPG format, maximum 100 KB.
Your phone took a 4 MB photo. You upload it. Rejected. No indication of how far over you are, no suggestion of what to change. Just: too big, try again.
So you open an editor, export at 60% quality, check the size, still too big. Try 40%. Now it looks like it was faxed. Try 50%. Upload. Rejected — 104 KB. Try 45%.
This is a genuinely common problem. Indian competitive exams like NEET, SSC, and UPSC, state government exam boards, visa applications, and job portals all impose hard KB caps on photo and signature uploads. The limits exist for sensible reasons — these systems handle enormous volumes of uploads and need to stay responsive on slow mobile connections — but the interface almost never helps you meet them.
Why the quality slider is the wrong tool
A quality slider asks the wrong question. It asks "how much quality do you want to give up?" when what you actually need to answer is "what's the best this can look while staying under 100 KB?"
Those aren't the same question, and the relationship between them isn't intuitive. JPEG quality settings don't map linearly to file size. Quality 50 isn't half the size of quality 100. The curve depends on the image itself — a photo of a face against a plain background compresses very differently from a busy outdoor scene. Which is why guessing takes four or five rounds and you still end up either over the limit or uglier than necessary.
Work backwards from the number instead
The better approach inverts it. You supply the constraint — 100 KB — and the tool searches for the answer.
That's what our compress-to-KB tool does. Give it a target and it encodes, measures the actual result, adjusts, and repeats — narrowing in on the highest quality that still fits under your limit. If quality alone can't get there (which happens with very small targets like 20 KB on a large photo), it reduces the dimensions too, rather than mangling the image at quality 5.
You get one file, on the first try, and the result tells you exactly where you landed: 44 KB · ≤ 50 KB ✓.
There are direct pages for the sizes portals actually ask for — 20 KB, 50 KB, 100 KB, and 200 KB — so you can skip straight to your number.
Getting a good result, not just a small one
Hitting the size is the easy half. Making the photo still look acceptable takes a couple of decisions.
Crop before you compress. This is the single highest-leverage thing you can do and almost nobody does it. Most form photos want head and shoulders. If your source is a full-body shot, you're spending your entire byte budget on a wall and a floor. Crop to what's required first, and every remaining byte goes into the part that matters — the face.
Resize sensibly. Forms rarely need more than about 600 pixels on the long edge for a passport-style photo. A 4000-pixel-wide source squeezed into 50 KB will look far worse than the same photo resized to 600 pixels and then compressed, because the compressor isn't fighting to describe detail that will never be seen.
Use JPG unless told otherwise. Most portals require JPG, and it's the right choice for photographs anyway. PNG is lossless, which sounds better but is exactly wrong here — a lossless photo at 100 KB will look dramatically worse than a JPEG at 100 KB.
Check the other requirements while you're there. Portals frequently also specify minimum and maximum pixel dimensions, a background colour, and a separate size cap for the signature image (often much smaller — 10 to 20 KB). Meeting the KB limit and failing the dimension rule means going round again.
A worked example
Concretely, here's what the difference looks like on a typical phone photo destined for a 100 KB limit.
The starting point. A 4032 × 3024 photo straight off a phone, about 3.8 MB. That's roughly 38 times the limit.
Guessing route. Export at quality 60 → 480 KB, still nearly five times over. Quality 30 → 190 KB. Quality 15 → 95 KB, fits, but the face now has visible blocking around the eyes and mouth, because you've forced a 12-megapixel image through a budget that can't describe it. Four exports, and a poor result.
Working-backwards route. Crop to head and shoulders — this alone throws away perhaps 60% of the pixels you were never going to be judged on. Resize the crop to 600 pixels on the long edge. Now ask for 100 KB. The tool lands somewhere around quality 85, well inside the range where JPEG artefacts are invisible at normal viewing size.
Same limit, one step, and a photo that looks like a photo. The lesson generalises: spend your byte budget on the part of the image that matters, then compress. Cropping and resizing are not preliminaries to compression — they are most of the compression.
Don't forget the signature
Almost every exam and government portal that caps the photograph also asks for a separate scanned signature, with its own — usually much smaller — limit. Figures in the 10 to 20 KB range are common, and people who've just solved the photo problem walk straight into it.
Signatures compress differently from photographs. They're mostly white with a small amount of dark line work, which JPEG handles inefficiently, and JPEG artefacts around thin strokes look particularly bad. Two things help:
Crop tightly to the signature itself. White space costs bytes for nothing.
Increase contrast before compressing. A signature scanned on a phone often has a grey, slightly shadowed background. Pushing it toward clean white and solid black both improves legibility and compresses far better, because there's less noise for the encoder to describe.
If the portal accepts PNG for the signature, take it — for line art on a flat background, PNG is often smaller than JPEG as well as cleaner. Read the requirement rather than assuming JPG for both.
What the portal is checking besides size
File size is the rule people notice, because it's the one that produces an error. It's rarely the only rule, and the others fail just as silently.
Pixel dimensions. Many forms specify both a minimum and a maximum — something like "between 200×230 and 500×600 pixels". Compress-only tools don't touch dimensions, so a photo can be comfortably under 100 KB and still be rejected for being 4000 pixels wide. Resize to the stated range before you compress; it helps both problems at once.
Aspect ratio and framing. Passport-style requirements usually specify head-and-shoulders with a defined proportion of the frame taken up by the face. A correctly-sized file that's cropped wrong gets rejected at manual verification, sometimes weeks later, which is a far worse failure than an instant upload error.
Background. Plain white or light grey is the common requirement. This is worth checking before you compress, because a busy background costs you bytes and fails the rule.
Format and colour mode. JPG is usually mandated. Occasionally a portal also requires RGB rather than CMYK — rare, but it's a silent failure when it happens, since the file uploads fine and looks wrong later.
Filename rules. Some systems reject spaces or non-ASCII characters in filenames. Costless to avoid.
The pattern across all of these: the size cap gives you immediate feedback, and everything else doesn't. Read the full specification once, set the dimensions and crop to match, and then solve the KB limit — which is the only step that genuinely needs a tool.
Why we don't upload your photo
Our converter does the work inside your browser. Nothing is sent to a server.
We'll be straight about the competitive picture here: several tools in this space now advertise the same thing, and that's good — it should be the default for this kind of task. The reason it matters isn't abstract. The photos people compress for application forms are passport photographs, signatures, and identity documents, attached to a real name on a real application. Uploading that to a free tool with an unread privacy policy is a worse trade than most people realise they're making.
What we'd point at instead as the actual difference: you tell it the number and it hits the number, there's no file-count cap, and there's no sign-up.
There's a practical benefit to local processing beyond privacy, too. Application deadlines have a way of coinciding with the portal being slow and your connection being worse than usual. A tool that has to upload a 4 MB photo, process it, and send a result back is at the mercy of both. One that runs on your own machine finishes at the same speed whether the network is healthy or not — which is a small thing until it's 11pm on the closing date.
Frequently asked questions
How do I compress an image to exactly 100 KB?
Don't guess at a quality percentage — state the target instead. Our tool takes 100 KB as the input and searches for the highest image quality that lands under it, downscaling only if quality alone can't get there. The result shows what you actually got, so you can confirm before uploading. Crop the photo to the required framing first; it makes a large difference to how good the result looks.
Why does my exam form reject the photo without saying why?
Most portals validate the file size on the server and return a generic failure. They cap uploads to stay responsive under heavy load and on slow mobile connections, but rarely report how far over you are. That's why hitting the number precisely on the first attempt is worth more than it sounds — you get no feedback to iterate against.
What size should a photo be for NEET, SSC, or UPSC forms?
It varies by exam and by year, and it usually differs for the photograph and the signature — the signature limit is often much smaller. Always read the current notification for the exam you're sitting rather than trusting a number from a blog, including this one. Common caps are 20, 50, 100, and 200 KB, which is why those have dedicated pages.
Will compressing to 100 KB ruin my photo?
Not if you prepare it. Crop to the required framing and resize to roughly the dimensions the form asks for, then compress. A cropped, correctly-sized photo at 100 KB usually looks perfectly acceptable. A full-resolution, uncropped photo forced to 100 KB will not, because the compressor is trying to describe far more image than the budget allows.
Should I use JPG or PNG for form uploads?
JPG, unless the form explicitly says otherwise. PNG is lossless, which makes it excellent for logos and screenshots and a poor choice for photographs under a size cap — at the same file size a JPEG will look considerably better. Most portals specify JPG anyway.
Are my photos uploaded when I use your compressor?
No. The compression runs inside your browser, and no request carries your image anywhere. You can verify it by opening your browser's developer tools, switching to the Network tab, and compressing a file — you'll see no upload. This matters for form photos in particular, since they're usually identity documents attached to a real application.
Can I compress many photos at once?
Yes, and there's no file-count cap. Drop in as many as you like and download them together. If different images need different targets, run them in groups by target.
What if my photo still won't fit the limit?
If a very small target like 20 KB can't be met at reasonable quality, the tool reduces the dimensions as well as the quality, which is almost always the right trade — a smaller sharp image beats a large mushy one. If you're still stuck, crop tighter. Cropping removes pixels you were paying for and didn't need.