Why upload forms reject your photo, and how to fix every error

The whole rejection map in one table

Almost every rejection falls into one of seven buckets. Find the message that matches what your form showed (or the symptom, if it showed nothing useful), read the cause, and go straight to the fix. The sections below explain the trickier ones in detail.

"File too large" and "file too small": the two KB traps

File size is the single most common cause, and it works in both directions. A portal that says "maximum 50 KB" is checking the weight of the saved file, not its pixel dimensions or how sharp it looks. A 200 × 230 px passport photo can legitimately be 15 KB or 95 KB: same image, different JPEG quality. When the form rejects yours as too large, you don't need to shrink the picture, only its file weight.

A common mistake: people crank compression so hard that the file drops below a hidden minimum. Forms that set a floor (e.g. "between 10 KB and 50 KB") reject anything under it as too small. If you've compressed and now get a too-small error, you don't redo the photo. Instead, increase the file size to add weight back without changing how it looks, until you clear the floor. Aim for the upper half of the allowed band.

• Too large: compress to a target KB, typing the exact ceiling the form shows and aiming a few KB under it.
• Too small: pad the file up until it passes the minimum; this changes file weight, not the visible image.
• Stuck oscillating between the two limits: compress to roughly 80–90% of the maximum so you sit safely inside the band with margin.

"Invalid format": usually a hidden PNG, HEIC or renamed file

When a form says it only accepts JPG and rejects your file, the problem is almost always one of three things. First, the file genuinely is a PNG or WebP — common when you downloaded an image from the web or took a screenshot. Second, it's an iPhone HEIC photo (covered next). Third, and this one is sneaky, someone renamed a photo.png to photo.jpg, so the extension lies but the actual bytes are still PNG, and a strict server reads the real format and rejects it.

Renaming never changes the format; you have to genuinely re-encode the file. Run it through the JPG converter and it writes a real JPEG with the correct internal markers and a .jpg extension. If a form specifically wants PNG instead (rare for photos, common for logos or signatures needing transparency), the PNG converter does the reverse.

Most government and exam portals expect JPG/JPEG for photos and signatures. If the notification doesn't say, default to JPG, the safest and most universally accepted choice, which avoids the invalid-format error entirely. For the deeper trade-offs between formats, the JPG vs PNG vs WebP guide explains when each one is the right pick.

The iPhone HEIC problem (why your photo "won't upload")

If you're on an iPhone and the upload button does nothing (no error, no preview, the form acts as if you picked no file), the culprit is usually HEIC. Modern iPhones save photos in HEIC (High Efficiency Image Container) to keep files small, but most Windows machines, many Android browsers, and a large share of web upload forms can't read it. To them, the file is unreadable, so the upload quietly fails or the photo shows up blank.

The fix is to convert the photo to JPG first. Run it through the HEIC to JPG converter, which decodes the HEIC in your browser and gives you a standard JPEG that every portal accepts. To stop the problem at the source, change your camera setting: on iPhone go to Settings → Camera → Formats and choose "Most Compatible", which makes the camera shoot JPG from then on. The full walkthrough lives in the convert HEIC to JPG guide.

• Symptom: upload silently fails, blank preview, or "unsupported file" only on certain devices.
• One-off fix: convert the HEIC file to JPG, then upload the JPG.
• Permanent fix: Settings → Camera → Formats → Most Compatible on the iPhone.

Wrong dimensions and wrong aspect ratio

Dimensions and aspect ratio are two separate checks, and forms can fail you on either. "Invalid dimensions" means the pixel width or height is outside an accepted range. A portal that wants 200 × 230 px will reject a 1500 × 2000 px photo straight from your camera. The fix is to resize to the exact pixels the form names, not to crop blindly.

Aspect ratio is the shape, width-to-height, independent of the actual pixel count. A signature box that demands a landscape image (say 4.0 × 2.0 cm, wider than tall) will reject a square crop even if its file size and resolution are fine. When the shape is wrong, crop to the correct ratio first, then resize to the target pixels. The order matters: crop for shape, then resize for size.

"Photo not clear" and background rejections

Some rejections aren't about the file at all. They're about the picture. "Photo not clear", "face not detected", or "background must be plain" come from portals (and increasingly automated face-checks) that inspect image content. No resize or compress tool fixes these; the image itself has to change. The usual offenders are blur, a shadow falling across the face, weak or uneven lighting, and a busy or coloured background where a plain one is required.

Background is the most fixable of these. If the photo is sharp and well-lit but the wall behind you is patterned or the wrong colour, you don't need to retake it. Instead, change the background to a plain colour or use the white-background tool for passport and exam photos. For blur or shadow, retake the photo in even, front-on light against a plain wall, then size it. The step-by-step for getting to a clean white background is in the white background guide.

• Blur or low light: retake in bright, even, front-facing light, because software can't sharpen a face the form will trust.
• Busy or coloured background: replace it with a plain colour instead of reshooting.
• Shadow behind the head: move away from the wall or add light from the front, then recapture.
• Face too small or cropped: re-frame so the head and shoulders fill the frame, then crop and resize.

Filenames, mobile quirks, and re-uploading cleanly

A handful of failures have nothing to do with the image and everything to do with how it's named or which device you're on. Some older portals choke on filenames with spaces, accents, or special characters like #, &, or %, and a few enforce a maximum filename length. If a perfectly valid file refuses to attach, rename it to something plain like photo.jpg before trying again.

Mobile vs desktop

Mobile browsers add their own wrinkles. iOS may offer to upload a HEIC (see above), some Android keyboards/file pickers attach the wrong file, and a flaky mobile connection can make a large upload time out and report as a generic failure. If a form keeps failing on your phone, the most reliable move is to fix and finalise the file on the phone (convert and compress it first) or switch to a desktop browser for the actual upload.

1. Note the exact wording or symptom of the rejection; that's your diagnosis.
2. Match it to a row in the table above and run the one matching tool.
3. Rename the file to plain ASCII (e.g. photo.jpg) if it has spaces or symbols.
4. Re-upload the fixed file; if the portal lets you preview, check it before you submit.
5. Keep the corrected original on your device in case a correction window opens later.

If you'd rather not work out which error is which, the fix image upload errors page lets you pick the message you saw and drops you onto the exact tool with the right settings ready to go.