Why Your 20KB Photo Keeps Getting Rejected on Indian Government Forms
I run ImageFormatConverter.in. The most common message in my inbox is not "how do I compress" — it is "it is under 20KB but the form still rejects it." After thousands of those tickets, the causes cluster into a short list. Size is rarely the whole story.
Compressor: Image Compressor to 20KB
Step-by-step workflow: JPG Compress 20KB guide
Rejection reason #1 — Wrong format
Portals say "JPG/JPEG" in small text below the upload button. Applicants upload a PNG compressed to 19KB and assume size was the only gate.
Indian government upload validators often check:
- File extension (
.jpg) - Internal format header (actual JPG bytes)
- Sometimes MIME type sent by the browser
Fix: Export as JPG. If you started from PNG, use PNG to JPG, then compress. Renaming the file does nothing.
WEBP causes the same failure on older portals. Convert with WEBP to JPG when JPG is required.
Rejection reason #2 — Dimensions outside range
KB and pixels are independent checks. I have verified 17KB uploads failing because the image was 1024×768 when the form wanted 200×230.
The dimension line hides below the size line on many SSC notices. Applicants fix KB first, never scroll down, and blame the compressor.
Fix: Crop or resize to the exact pixel box before the 20KB step. Passport Size Photo Maker helps when a sample frame is shown.
Rejection reason #3 — Quality too low to pass human review
Less common than #1 and #2, but real: upload succeeds, later stage flags the photo as unusable — blurred face, merged signature strokes, unreadable thumb print.
At 20KB a signature photographed on grey paper with a faint pen becomes a smudge. The file passes the byte check but fails when someone zooms in.
Fix: Retake with darker ink, tighter crop, white background. Compression cannot invent contrast.
Rejection reason #4 — Wrong field, wrong file
Photo uploaded in signature slot or vice versa. Both files may be valid JPGs under 20KB. Preview shows swapped content. Applicant re-compresses instead of re-assigning files.
Fix: Rename downloads photo.jpg and signature.jpg before upload. Check portal preview before final submit.
Rejection reason #5 — Chain compression
Applicant compresses to 22KB, compresses again to 19KB, again to 18KB. File passes size. Face looks like a watercolor. Some portals run blur detection; others reject at document verification.
Fix: One pass from the camera original. If 20KB looks bad, check whether 50KB or 100KB is allowed on that field.
The three-line audit (do this before re-compressing)
Open the form instruction page and answer:
- Format: JPG only? → export JPG
- Pixels: width × height listed? → match exactly
- Field cap: 20KB on signature but 50KB on photo? → use the right tool per field
Only after all three pass should you touch Image Compressor to 20KB again.
Why portals still use 20KB in 2026
Not cruelty — legacy infrastructure. Forms were designed for slow connections and small database columns. A 20KB cap keeps millions of applications storable and submittable on 2G-era timeouts. Limits rarely get updated when portals get a fresh CSS skin.
Understanding that explains why the rules feel archaic but enforce strictly.
Photo field vs signature field on the same form
| Field | Typical cap | Tool |
|---|---|---|
| Signature | 20KB | Image Compressor to 20KB |
| Photo | 50KB–100KB | 50KB or 100KB |
| Thumb impression | 20KB | Same as signature — tight crop on ink |
Using 20KB on a photo when 50KB is allowed is the quality mistake I wish people caught earlier.
Deadline-night pattern
Traffic spikes 9 PM–1 AM before SSC and state exam cutoffs. Same person hits the tool three times in twenty minutes — usually changing format on attempt two and dimensions on attempt three. The fix that saves the most time is format + pixels first, compression second.
If you are in that window right now: stop re-compressing. Open the form PDF. Fix the three-line audit. One fresh pass from original.
Further reading
— Rajat Gupta