Why exam uploads fail
Application portals validate two things independently: the pixel dimensions of your image and its file size in kilobytes. Both have to be right at the same time, and they pull against each other, since shrinking a file to fit a KB ceiling usually means lowering quality, while a minimum size means you cannot compress too far.
A photo from any modern phone is roughly 2 to 6 MB. A typical exam ceiling is 50 KB. That is a reduction of around 99%, and it has to land inside a window rather than merely below a limit, at dimensions fixed to the pixel. Generic image compressors aim for “smaller”, which is a different goal, so they overshoot the minimum or miss the dimensions.
That is the actual problem this tool solves. It repeatedly encodes your image, measures the real byte size each time, and searches for the quality setting that lands inside the required range at exactly the required dimensions. The size meter shows that search happening, so you can see the file settle into the target zone instead of guessing and re-uploading.
Kilobytes are ambiguous, so we target both readings
A quiet trap: “KB” means 1,000 bytes to some systems and 1,024 to others, and exam portals do not say which they use. A file that reads as 49.9 KB under one definition can read as 51.1 KB under the other, and be rejected. Every result here is targeted at the overlap of both interpretations, so it passes whichever check the portal happens to run.
What makes this different
- Your files stay on your device. A photograph of your own face is sensitive. Here it is never transmitted, because the work happens in your browser. You can confirm it by watching your browser’s network tab, or by going offline after the page loads and using the tool anyway.
- Every document, not just the photo. Exams that also require a signature, thumb impression, or handwritten declaration are covered, each with its own requirement and its own tab. This is where most tools stop, and where applications get stuck.
- Verified requirements. Every number here is read out of the current official notification and stamped with the date it was checked. When a requirement changes, the page changes.
- It tells you when it cannot win. Some documents have a minimum file size that a small or over-compressed original genuinely cannot reach. In that case you get told so, plus the closest result achieved, rather than a file that will quietly be rejected.
Requirements change between cycles, so check the year
Exam bodies revise their upload rules, and the advice circulating online lags behind by years. A live example: the Staff Selection Commission used to accept an uploaded photograph and now captures it live inside the application form, explicitly rejecting applications built from a re-photographed image. Guides still quoting an SSC photo size are not merely out of date, they point you at the one action that causes rejection. Each exam page here carries the date its requirements were last checked against the official notification, and links to that notification so you can read it yourself.
Getting a good original
The tool can shrink almost anything, but it cannot add detail that was never captured. A few things that make the difference:
- Photograph documents in daylight, with the phone parallel to the paper rather than tilted, so the text and lines stay sharp.
- Avoid screenshots. A screenshot of a photo is lower resolution than the photo, and for documents with a minimum file size it may be too small to qualify.
- Sign large. Signatures are commonly rejected for being what notifications call “miniature”. Fill most of the paper.
- Use a plain, light background for photographs, and leave off caps and glasses, which most exams disallow outright.