Read almost any Indian exam notification and the photograph requirement looks like this:
Most people read only the second number. They compress until the file is comfortably under 50 KB, end up at 9 KB, upload it, and get an error.
The first number is a requirement too.
Why a minimum exists at all
A maximum file size protects the portal's storage and bandwidth. A minimum protects something else: legibility.
A 4 KB JPEG of a face is not a usable photograph. It is a smear of compression blocks. When that photo is printed on an admit card, or displayed to an invigilator comparing it against the person in front of them, it has to actually resemble you. The floor is a blunt instrument for enforcing that the image carries enough detail to be worth having.
It is blunt because file size is only a rough proxy for detail. But it is trivial to check automatically, which is why it is what portals check.
Why compressing harder makes it worse
This is the trap. The file is rejected, so you compress it again, more aggressively, and it gets smaller — further below the floor, not closer to it.
If you are already under the minimum, more compression is exactly the wrong direction.
What actually raises the size
Three things, in ascending order of sense.
Raise the JPEG quality. This is the obvious move and it often works. Going from quality 40 to quality 90 can take a 9 KB file to 25 KB. If the ceiling gives you room, do this first.
Increase the pixel dimensions. Only if your notification gives a range rather than exact numbers. If it says 350 x 350 to 1000 x 1000, exporting at 700 x 700 instead of 350 x 350 raises the file size honestly, by carrying more real detail.
If the notification gives exact dimensions — as IBPS and SBI do — this is not available to you. You cannot change the pixel count.
Pad the file. When quality is already at maximum and the dimensions are fixed, there is nothing left to add to the image. But you can add bytes to the file without touching the image.
Padding, and the wrong way to do it
The JPEG format has a comment segment — marker FF FE — designed to carry text that decoders ignore completely. PNG has an equivalent in ancillary chunks. You can append blank comment data until the file clears the floor. Every decoder skips it. The image is byte-for-byte identical to what it was.
This is the correct fix, and it is what our resizer does. When the compressed file lands under the minimum, it tells you exactly how much comment data it added.
Some tools do something else. They loop over the image adding random pixel noise until the byte count rises, because noise is incompressible and inflates a JPEG efficiently. It works, in the sense that the number goes up. It also visibly degrades your photograph — you are deliberately damaging the image so a byte counter reads higher.
We checked one popular resizer's code and found exactly this: up to twelve passes of random noise injection. If your photo comes back looking grainier than it went in, that is likely why.
Bands worth knowing
| Exam | Photo | Signature |
|---|---|---|
| SSC CGL | 20 to 50 KB | 10 to 20 KB |
| IBPS and SBI | 20 to 50 KB | 10 to 20 KB |
| UPSC | 20 to 300 KB | 20 to 100 KB |
| NEET UG | 10 to 200 KB | 4 to 30 KB |
| JEE Main | 10 to 200 KB | 10 to 50 KB |
These are the sizes we currently list and they are not verified against notifications — see how we check sizes. Confirm yours before uploading.
Signatures are where the floor bites hardest. A clean scan of a thin signature on white paper compresses extremely well, because most of the image is a single flat colour. Landing under 4 KB is completely normal, and it is why signature uploads fail more often than photographs.