12 Exam Portal Photo Error Messages, Decoded

Exam portals speak in shorthand — "invalid photo," "dimension mismatch," "file too large." This guide maps twelve frequent messages to the property that actually failed and the fastest fix.

Key takeaways

Most exam photo errors reduce to four file properties: pixel dimensions, KB size, format, and filename.
Generic messages deliberately hide which property failed; measure all four before re-uploading.
Error text varies by board but repeats the same underlying validation rules season after season.
Fixing the wrong property — compressing when pixels were wrong — wastes time and can create new errors.
A common exam portal error messages decoded reference saves repeat uploads when deadlines are close.
Always compare against the current notification; error labels stay stable even when numeric limits change.

Quick reference

Error message (typical wording)	Most likely cause	First fix to try
Invalid photo / invalid image	Any property failed	Measure pixels, KB, format
Dimension mismatch	Wrong width × height	Re-crop to bulletin pixels
File size exceeds maximum	KB too high	Lower JPEG quality stepwise
File size below minimum	KB too low	Raise quality; re-export from source
Unsupported format	PNG/HEIC/BMP uploaded	Convert to JPG; re-check pixels
Upload failed / network error	Connection or portal load	Retry; different browser
Image dimensions not acceptable	Pixels or aspect ratio	Confirm exact pixel pair
Photo not as per specification	Multiple possible	Full checklist: pixels, KB, background
Signature invalid	Signature file failed	Check signature pixels and KB separately
File name not acceptable	Wrong name pattern	Rename per bulletin (photo.jpg etc.)
Corrupted file	Bad export or interrupted save	Re-export locally; avoid WhatsApp
Timeout during upload	Large file or slow network	Compress to mid-band KB; wired connection

Use this table as your first stop when decoding portal text. Detailed sections below expand each row.

Decoded error messages (1–12)

1. "Invalid photo" or "invalid image"

The broadest message. Portals use it when any validator fails and they do not surface specifics. Do not guess.

Fix order: pixels → KB → JPG format → background quality → filename.

Often confused with: browser cache showing an old error after you already fixed the file. Hard refresh or new browser session after a successful re-export.

2. "Dimension mismatch"

Pixels do not equal bulletin integers. Crop, do not stretch.

Fix: Properties → width/height → re-crop → re-export.

Link: UPSC triple signature and photo specs when preparing UPSC OTR uploads with square photo rules.

3. "File size exceeds maximum"

KB above ceiling. Lower JPEG quality in 5-point steps.

Fix: compress from source; aim for middle of KB band.

Banking candidates should confirm IBPS PO photo and signature size — ceilings differ from SSC.

4. "File size below minimum"

KB under floor. Common after over-compressing to fix message #3.

Fix: raise quality until above minimum while staying under maximum.

5. "Unsupported format" or "only JPG allowed"

PNG, HEIC, or PDF attached.

Fix: export JPG; re-measure pixels because conversion can change dimensions if done carelessly.

6. "Upload failed" without property detail

Often network or portal load, not your file.

Fix: retry; switch browser; reduce KB slightly to shorten upload; avoid peak hours if possible.

7. "Image dimensions not acceptable"

Similar to dimension mismatch; sometimes means aspect ratio wrong even when one side matches.

Fix: verify both width and height and that ratio matches bulletin.

8. "Photo not as per specification"

Catch-all used on SSC and railway portals.

Fix: full checklist against PDF — pixels, KB, background plain white, recent photo if stated.

SSC GD photo and signature size is the authoritative starting point for GD constable cycles.

9. "Signature invalid" or signature field error

Photo may be fine; signature failed pixels or KB.

Fix: measure signature file separately; confirm ink color rules if manual review follows.

10. "File name not acceptable"

Some cycles require exact names like photo.jpg.

Fix: rename to match bulletin literally; re-upload same bytes.

11. "Corrupted file"

Interrupted download, bad re-save, or extreme compression.

Fix: re-export locally from source; open file locally to confirm it renders before upload.

12. Timeout or silent failure

Spinner stops; no success message.

Fix: smaller KB export; wired network; disable VPN; try incognito without extensions.

Troubleshooting workflow under deadline pressure

Step	Action	Why it matters
1	Screenshot exact error text	Match Quick reference row
2	Measure flagged property on disk	Fixes guesswork
3	Change one property only	Isolates cause
4	Re-upload once	Confirms fix
5	Run full checklist if generic error repeats	Catches stacked failures

This workflow embodies what common exam portal error messages decoded guides are for — translation, not magic.

Fixing KB without fixing pixels can swap "dimension mismatch" for "file too large" or vice versa. That is progress: the portal tells you the next gate. Work through gates systematically instead of reverting to the first rejected file.

Mobile browsers sometimes truncate messages. Desktop Chrome or Firefox on a laptop shows fuller text. If mobile upload fails repeatedly, sync the finished JPG to desktop and upload from there before assuming the file is wrong.

Dual-upload forms may highlight only one field. Read which input failed. Preparing both files against the same bulletin but different pixel lines prevents swapping fixes between fields.

Less common messages and portal quirks

Face not detected — cropping cut off chin or forehead; retake or re-crop with head height rules.
Background not acceptable — shadows or patterns; plain white retake.
Photo too old — recency rule from bulletin, not a KB/pixel issue.

Legacy validation code bundles multiple checks behind one string. Conducting bodies rarely invest in granular UX for once-a-year photo uploads. Applicants supply the granularity by measuring locally.

After each successful upload, note exam name, pixel pair, KB result, quality setting, and browser used. Next season you still must read the new bulletin, but the measurement habit transfers.

Avoid posting your photo in public forums to decode errors. Use local file properties and trusted tools like PhotoFix instead. Error text alone is enough for this common exam portal error messages decoded guide to point you to the right property.

Extended scenario: one evening, three errors

Attempt 1: invalid photo — file was HEIC renamed to .jpg. Convert properly. Attempt 2: file too large — compress to 38 KB. Attempt 3: success. Without a decoder, the applicant might retake the physical photo after attempt 1. With a decoder, attempt 1 is format-only.

When self-service decoding is not enough

If pixels, KB, format, and filename all match the bulletin and three browsers still reject the same file, capture a screenshot of Properties plus the portal error and contact the exam helpdesk during working hours. Ask whether a known portal outage exists before retaking photos.

Persistent failures after correct measurements sometimes trace to portal-side validation bugs during peak load — rare, but real near deadlines. Escalate with evidence rather than repeatedly compressing an already compliant file.

Exam portals validate file size in kilobytes separately from pixel dimensions. A photo can look sharp on screen yet fail because the exported JPG is outside the stated minimum or maximum. Always measure the saved file on disk, not a preview thumbnail. Re-export from your original source photo when adjusting KB rather than re-compressing an already compressed export. Open the official notification beside your file manager so you compare against the current cycle numbers, not last year's coaching handout. PhotoFix helps you land inside the range without guesswork.

Guides covering common exam portal error messages decoded help you match bulletin limits before deadline night.

FAQ

Why does my exam portal say invalid photo with no details? Generic validator failure. Check pixels, KB, and JPG format in that order.

Is dimension mismatch different from invalid photo? Yes — mismatch usually means pixels specifically, while invalid photo can mean anything.

What is the most common real cause behind vague errors? Wrong pixel dimensions from reusing a passport export on an SSC-style form.

Can file name cause invalid photo errors? Yes on portals that enforce exact names.

Why did error text change after I recompressed? You fixed one property and exposed the next failing gate.

Should I call the helpline first? Measure locally first; helplines will ask for pixel and KB readings anyway.

Do mobile and desktop uploads show the same errors? Same rules; mobile may show shorter text.

Can signature errors look like photo errors? Some forms use one generic string for either field — check which upload input failed.

Where do I find numeric limits? Official recruitment notification PDF for your specific cycle.

Does PhotoFix show which property failed? PhotoFix previews pixels and KB before upload so you catch issues early.

Are these messages the same every year? Wording stays similar; numbers in the PDF may change — always reopen the current notification.

What if there is no error text at all? Treat as timeout or silent invalid — run full checklist and retry on desktop.

Fix it now

This applies across documents and exams — pick yours and we will set the exact size automatically.

Choose your document or exam

Match your portal text to the Quick reference table, measure the flagged property on your exported JPG, fix it once, and re-upload. Do not rotate through random quality settings without reading pixels first.

Keep this common exam portal error messages decoded page bookmarked during application season — the messages repeat even when the underlying bulletins change. A methodical decode beats retaking photos that were already fine.