Why Does My Photo Upload Keep Getting Rejected?
Short answer
Four separate checks produce the same generic error: format, pixel dimensions, file size and occasionally colour mode. Start with format — an iPhone HEIC file fails most validators before any other rule is tested. Convert to JPG, then check the dimensions and size against what the form actually states.
On this page
An upload form that says “invalid image” and nothing else is testing at least four things and telling you about none of them. The photo you are uploading might be failing on any one of them, and the fixes have nothing in common.
The efficient approach is to check them in order of how often they are the culprit, rather than guessing.
The four checks, in likelihood order
| Check | Typical symptom | Fix |
|---|---|---|
| Format | Rejected instantly, before any upload progress | Convert to JPG |
| Pixel dimensions | “Incorrect dimensions”, “too small” | Crop and resize |
| File size in KB | “File too large” or a size shown on the form | Compress |
| Colour mode or profile | Accepted then rejected later by a human | Re-save as sRGB |
Work down the list. The first two account for the overwhelming majority.
Format: the most common cause by far
If you are uploading from an iPhone, start here.
iPhones save photos as HEIC by default. It is a good format that compresses better than JPG, and a great deal of software does not accept it — including most government portals, many job application systems and a good number of ordinary web forms. Your phone shows the photo perfectly, which makes the rejection baffling.
Three ways out:
Convert the file. Our HEIC to JPG converter does it in your browser, so an ID photo or a passport scan never leaves your machine. The longer form of this, including the Windows and Mac routes, is in converting HEIC to JPG.
Change the camera setting. Settings → Camera → Formats → Most Compatible makes the phone save JPG from then on. Stopping the iPhone saving as HEIC covers the side effects.
Change the share setting. Settings → Photos → Transfer to Mac or PC → Automatic converts on export, which handles existing photos without converting your whole library.
Do not rename the file. Changing .heic to .jpg relabels it without changing
a single byte inside, and anything that reads the file properly will still
reject it — sometimes as a corrupt file, which is a worse error to debug.
Other format traps: screenshots on Android are sometimes WebP, which some forms refuse; scans arriving as PDF when the form wants an image; and photos saved from messaging apps that retain unexpected extensions.
Dimensions: the arithmetic forms hide
A form asking for “3.5 × 4.5 cm at 300 DPI” is describing a pixel count in a roundabout way. Centimetres and DPI are not stored in your image in any meaningful sense — only pixels are real.
The conversion is two steps: divide centimetres by 2.54 to get inches, then multiply by the DPI. The full worked version, with a table of the common requirements, is in photo rejected for wrong dimensions.
Two things go wrong at this stage.
Aspect ratio. Your phone shoots 4:3 or 3:2. An ID requirement is usually something else. Resizing straight to the target dimensions squashes the image, and a stretched face is obvious to a reviewer. Crop to the target ratio first, then resize.
Minimum dimensions. If the form wants 600 × 600 and your source is 400 × 400, there is no honest fix. Enlarging adds interpolated pixels, not detail, and it looks exactly like what it is. Find the original rather than a copy that a messaging app downscaled.
That last point catches people constantly. Photos sent over messaging apps are routinely reduced to around 1600 pixels on the long edge. The version in your chat history is often too small while the original in your camera roll is fine.
File size: both directions
Maximum limits are the familiar problem. Our image compressor resizes and compresses in one pass, and compressing a photo to an exact size in KB covers hitting a specific number rather than overshooting.
Minimum limits surprise people. Some forms set a floor to reject blank or corrupt uploads, and a well-compressed photo can land underneath it. Increasing an image file size to meet a minimum covers the honest ways to do that — mainly re-exporting at higher quality rather than padding the file.
The order matters: crop, resize, then compress. Compressing first and resizing afterwards re-encodes an already-degraded image and gives a worse result for the same size.
Colour profile: the quiet one
This fails rarely, and when it does it is maddening because the upload succeeds and the rejection arrives later from a person.
Images carry a colour profile describing how their numbers map to actual colours. sRGB is the web standard. A photo edited in a wider space like Adobe RGB or Display P3, or one carrying a CMYK profile from a print workflow, can render with shifted colours in systems that ignore the profile — and a passport photo that arrives looking slightly green gets rejected by a human reviewer who has no idea why it looks wrong.
Fixing it:
- macOS Preview: Tools → Assign Profile → sRGB IEC61966-2.1.
- Windows: no built-in profile conversion in Photos. Re-saving through most editors converts to sRGB by default.
- Phones: photos shot in a wide gamut can usually be exported as sRGB by sharing them at a reduced size, which normalises the output.
This is also why a photo looks correct on your screen and wrong on the form’s preview. Your display is honouring the profile; the form is not.
ID photos have rules beyond the file
If you are uploading a passport or visa photograph, the automated checks go further than file properties. Common requirements include a plain light background, the head occupying a specified proportion of the frame, a neutral expression, both eyes visible and open, no shadows on the face or behind the head, and no heavy glasses glare.
None of those are fixed by resizing. If the rejection mentions the photograph rather than the file, re-take it against a plain wall in even, indirect light. Making a passport photo the right size covers the composition method.
What to expect
Converting from HEIC to JPG resolves most unexplained rejections on the first attempt, particularly from iPhone users, because the format check runs before everything else and fails silently.
The limit worth stating plainly: some portals are simply badly built. They reject valid files, give no reason, and behave differently in different browsers. If a file meets every stated requirement and still fails, try a different browser, try the desktop site rather than mobile, and then contact the department. An afternoon of re-compressing will not fix a server-side bug.