Guides · Updated 2026-07-21
Why your digital passport photo upload keeps failing
Online application portals reject photos with error messages that range from unhelpful to actively misleading. 'Photo does not meet requirements' can mean any of a dozen things. This guide works through the failure modes in the order they actually occur, so you can identify yours instead of guessing.
Failure 1: pixel dimensions outside the accepted range
This is the most common cause and the most commonly misdiagnosed, because people assume bigger is safer. It frequently is not — many portals specify a range with a hard upper bound.
The US DS-160 requires a square image between 600 x 600 and 1200 x 1200 pixels. A 3000 x 3000 pixel photo straight from a modern phone camera is rejected for being too large, even though it is objectively higher quality. China's visa system expects roughly 354–420 pixels wide by 472–560 high — a narrow window that a phone photo will never hit by chance. India's e-Visa wants at least 350 x 350. Canada's IRCC wants at least 420 x 540. Estonia's e-application wants at least 1300 x 1600. Finland's police e-service wants at least 500 x 653.
The fix is to generate the photo at a deliberate pixel size rather than resizing whatever the camera produced. That means choosing an output density that lands inside the window for that specific portal.
Failure 2: aspect ratio and the square trap
Some portals require a square image and reject anything else outright. The US and Indian systems both expect square. If you crop a 35 x 45 mm rectangle and upload it to a form expecting a square, it fails immediately regardless of pixel count.
Conversely, uploading a square photo to a portal expecting the 35 x 45 mm ratio produces either a rejection or an automatic crop that cuts off the top of your head. Check the expected shape before you crop, not after the upload fails.
Failure 3: file size limits
File size limits are usually stated in kilobytes or megabytes and are separate from pixel dimensions. India's e-Visa caps the JPEG at 1 MB. Other portals set limits as low as a few hundred kilobytes.
The instinct is to reduce quality until the file fits. Be careful: aggressive JPEG compression introduces blocky artefacts around high-contrast edges — particularly around hair and the outline of your face — and automated checkers can flag the result as low quality. If you need to reduce file size, first reduce the pixel dimensions to the minimum the portal accepts, then compress moderately. That order preserves far more visible quality than heavy compression at full resolution.
Failure 4: the automated checker disagrees with you
Several countries run an automated biometric check on upload — the UK's passport service and Ireland's Passport Online are well known for this. These systems measure head position, eye line, expression and lighting, and they are stricter than a human officer.
Common triggers: head very slightly tilted, eyes not level with each other, hair crossing the eye line, a shadow the human eye barely registers, or the head sitting a millimetre outside the band. The checker gives a generic failure and you are left guessing.
The practical response is to change one variable at a time. Retake facing the camera dead-on with your shoulders square, chin level, hair tucked clear of the eyes and brows, and light coming from in front rather than above. Then re-crop precisely to the head-height band rather than by eye.
Failure 5: format and colour mode
Almost every portal wants JPEG. PNG uploads are frequently rejected, and HEIC — the default format on recent iPhones — is rejected essentially everywhere. If your photo came off an iPhone and the portal will not accept it, converting HEIC to JPEG solves it.
Colour mode matters occasionally: images saved in CMYK rather than RGB can be rejected or rendered with wrong colours. This is rare from phones but happens with files that have passed through print-oriented software.
Greyscale is not acceptable anywhere for modern biometric documents, even though the photo may look perfectly clear.
Failure 6: metadata and the rotation problem
This one is genuinely obscure and worth knowing. Phone cameras record orientation as a metadata flag rather than rotating the actual pixels. Your photo looks upright everywhere you view it, because your phone, computer and browser all read that flag — but a portal that strips metadata sees the raw pixels, and your photo arrives rotated ninety degrees.
If a portal shows your preview sideways, or rejects a photo that looks obviously fine on your device, this is the likely cause. Re-saving the file through a tool that applies the rotation to the pixels themselves fixes it permanently.
Failure 7: quality flags on an otherwise good photo
If everything technical checks out and the photo is still refused, the remaining candidates are compression damage, upscaling, and screenshotting.
A photo that has been sent through a messaging app has usually been recompressed and downscaled, sometimes severely. A screenshot of a photo is far lower resolution than the original. And a heavily cropped photo enlarged back up to meet a minimum pixel count contains no real detail — upscaling invents pixels, and checkers increasingly detect the result.
Always start from the original camera file. If you cropped tightly, retake from closer instead of enlarging the crop.
A diagnostic order that saves time
Work through it in this sequence. Check the format is JPEG. Check the pixel dimensions against the portal's stated range, both floor and ceiling. Check the aspect ratio matches what the portal expects. Check the file size against the limit. Check the photo is not rotated when stripped of metadata. Then, and only then, start questioning the pose and lighting.
Most people do this backwards — retaking the photo repeatedly when the actual problem was that the file was 3000 pixels wide and the form capped at 1200. Ruling out the mechanical causes first usually locates the problem in under a minute.
Translating vague error messages
Portal error text is rarely precise, but the wording usually narrows things down. 'Photo does not meet requirements' with no detail is typically a dimension or format problem — check pixels, ratio and file type first.
'Face could not be detected' generally means the crop is too tight, the head is at an angle, lighting is uneven across the face, or contrast against the background is too low. It very rarely means what it literally says.
'Image quality too low' points at compression damage, upscaling or a screenshot rather than at your camera. 'File too large' is straightforwardly the byte size, not the pixel count — and the fix is to reduce dimensions first, then compress, in that order.
'Invalid file type' with a photo that looks fine on an iPhone is almost always HEIC masquerading behind a .jpg filename. Renaming the extension does not convert the file; it has to be re-saved as an actual JPEG.
One file for several portals
If you are submitting to more than one system, do not try to make a single file satisfy all of them. Their ranges frequently do not overlap — a file inside China's 354–420 pixel width window is far below the US minimum of 600.
Instead keep one high-quality master capture and export a separate file per portal at that portal's specification. Exporting is fast; the expensive part was taking a good photograph, and that is reusable.
Name the exports clearly by document so you do not upload the Canadian file to the Indian form three weeks later when you have forgotten which was which.
When the portal is the problem
Occasionally the photo is fine and the system is not. Government portals have maintenance windows, session timeouts that silently discard uploads, and browser compatibility quirks — some older systems genuinely behave differently in different browsers.
If a photo you have verified against every stated requirement fails repeatedly, try a different browser, clear the session and start the form fresh, or try outside peak hours. If it still fails, contact the issuing authority rather than continuing to modify a photo that already meets the published specification. Repeatedly degrading a compliant photo to satisfy a malfunctioning checker only makes the eventual manual review worse.
Why phone photos fail more often than they should
Modern phone cameras far exceed what any passport requirement asks for, and yet phone-sourced uploads fail constantly. The camera is almost never the problem — the pipeline after capture is.
Portrait mode is the first culprit. It applies a synthetic background blur, and a blurred background is a rejection in its own right; it can also soften the edges of your hair, which affects the face-detection pass. Shoot in standard photo mode.
Beauty and skin-smoothing filters are the second, and on some Android phones they are on by default without any obvious indication. Smoothed skin is a facial alteration, and it is exactly the kind of retouching identity documents prohibit. Check your camera settings rather than assuming they are off.
The third is the ultra-wide or selfie lens at close range, which distorts facial proportions — noses enlarge, ears recede. Use the main rear camera, stand further back, and crop in afterwards.
Keep the original, always
Whatever you end up uploading, keep the untouched original capture. Every downstream problem — wrong pixel size, wrong format, over-compression, a bad crop — is recoverable from a good original and unrecoverable without one.
If a portal rejects your file and you have only the exported, resized, compressed version to work from, each new attempt starts from a degraded source and quality falls further with every round. Starting fresh from the original each time keeps every attempt at full quality.
Fix your photo now — free preview, exact official sizes