Why Photo Uploads Fail and How to Fix It
File too large, wrong dimensions, unsupported format, wrong colour mode. The five common upload failures and what actually fixes each.
A photo upload fails for 5 reasons: the file is too large, the pixel dimensions are wrong, the format is unsupported, the colour mode is CMYK instead of RGB, or the file is renamed rather than converted. Working through those 5 in order solves almost every rejection, because the first 2 causes account for most failures.
Upload errors are usually vague, and the same message covers several different problems. A portal that says invalid file may mean any of the 5 causes, so guessing wastes time. Checking in order of likelihood is faster than reading the error again.
The 5 usual causes
- File too large. Compress to the stated KB limit.
- Wrong dimensions. Resize to the exact pixel size requested.
- Unsupported format. HEIC and WebP are refused by many portals. Convert to JPG.
- Wrong colour mode. CMYK files from print software need converting to RGB.
- Corrupt or renamed file. Renaming a .webp to .jpg does not convert it, and the server checks the file header.
Cause 1: the file is too large
Compress the photo to a specific KB target rather than lowering a quality slider and hoping. File size is the most common cause because phone cameras now save 4 MB to 8 MB images by default, while most portals cap uploads between 50 KB and 2 MB.
Reduce the pixel dimensions before compressing. A photograph resized to the size the portal displays loses 95 percent of its weight before compression begins, which leaves quality intact. Set the KB target, and the compressor searches for the highest quality that fits rather than leaving you to guess.
Cause 2: the dimensions are wrong
Resize to the exact pixel numbers the form lists, because portals check dimensions separately from file size. A 15 KB photo at 400 by 400 pixels fails a form that requires 200 by 230, even though the file weight is well inside the limit.
Some portals also enforce a minimum, refusing images below a stated resolution because the photograph would print badly on an identity card. Where a range is given, aim for the middle of it. Use fill and crop rather than fit when resizing, since fit preserves the original shape and pads the rest, which produces dimensions that do not match what was asked for.
Cause 3: the format is unsupported
Convert to JPG, which is the only format accepted everywhere without a caveat. Format problems appear most often on iPhone uploads, because iOS saves photographs as HEIC and most portals cannot decode it.
| Format | Government portals | Job sites | Marketplaces | |
|---|---|---|---|---|
| JPG | Accepted | Accepted | Accepted | Accepted |
| PNG | Usually accepted | Accepted | Accepted | Accepted |
| WebP | Usually refused | Mixed | Usually accepted | Unreliable |
| HEIC | Refused | Refused | Refused | Refused |
| AVIF | Refused | Mixed | Mixed | Unreliable |
The table explains a common frustration: a photograph that uploads fine to a shopping site is rejected by a government form. The formats accepted by modern commerce platforms are wider than those accepted by systems written years ago and never updated.
Cause 4: the colour mode is CMYK
Convert the image from CMYK to RGB, because screens use red, green and blue while CMYK describes printing ink. Cyan, magenta, yellow and key black (CMYK) files come out of print design software and often fail silently on upload.
The symptom is distinctive. A CMYK JPEG that does upload frequently appears with washed out or inverted colours in the preview, because the browser interprets the ink values as light values. Re-exporting from the design file in RGB fixes it. Any conversion through a browser based tool also produces RGB output, since the browser decodes and re-encodes the image in screen colour.
Cause 5: the file is renamed rather than converted
Changing a file extension does not change the file, and servers read the file header rather than the name. Renaming photo.png to photo.jpg produces a PNG file wearing a JPG name, and validation catches it immediately.
The same applies to a HEIC file renamed to .jpg, which is the version of this mistake that appears most often. Every image format begins with a short signature that identifies it, and upload validation reads those first bytes. Genuine conversion decodes the image and writes it again in the new format, which is what a converter does and what renaming never does.
Diagnosing a vague error in 60 seconds
To identify the cause quickly, run these 6 checks in order and stop at the first failure.
- Right click the file and read its size. Compare against the stated cap.
- Read the pixel dimensions in the same properties panel. Compare against the required numbers.
- Check the true format by opening the file in an image viewer, not by reading the filename.
- Confirm the extension is lower case, since a few older portals reject .JPG in capitals.
- Remove spaces and special characters from the filename, which some systems refuse.
- Open the image to confirm it displays fully, which rules out a truncated or corrupt download.
Errors that are not caused by your file
Session timeouts, browser extensions and server load cause upload failures that no amount of resizing will fix. These become common in the final days of an application window.
- Session expired. The form was open too long and the upload posts to a dead session. Reload and sign in again.
- Ad blocker or privacy extension. Some extensions block the upload script. Try a private window with extensions disabled.
- Server overload. Portals slow sharply near a deadline. A small file still uploads when a large one times out.
- Unsupported browser. Older portals sometimes require a specific browser and fail silently in others.
- Mobile data interruption. A dropped connection mid upload produces a corrupt file on the server rather than an error.
When the upload succeeds but the photo is rejected later
Technical validation and human verification are separate stages, so a file can pass the upload and fail at review weeks later. The second stage checks the content of the photograph rather than the properties of the file.
Reviewers reject photographs for a shadow across the face, a cap or sunglasses, a busy background, a photograph that is visibly old, or a face too small in the frame. None of those faults can be corrected by resizing, and none of them are reported at upload time. Check the preview the portal displays after upload, since that preview is what the reviewer will see.
Fixing the file on a phone
Every fix in this article works in a mobile browser, because the processing runs on the phone rather than on a server. Applicants frequently discover a rejection while away from a computer and under a deadline.
Open the tool in Chrome or Safari, tap the drop zone, and pick the image from the gallery. An iPhone offers a HEIC file, which converts to JPG in the same step, solving the format cause and the size cause together. Because nothing is uploaded, a weak connection does not interrupt the work, and a 5 MB photograph does not have to travel over mobile data before it can be fixed.
Preventing the next rejection
Prepare files against the written specification before opening the form, rather than fixing them under a session timer. Every one of the 5 causes is easier to avoid than to diagnose.
Write down the pixel dimensions, the KB cap and the accepted format. Crop, resize, convert to JPG and compress to the target in one pass, then check the finished file against all 3 numbers before the portal does. Preparation takes 3 minutes and removes the most stressful part of an application.
Our compressor and resizer both run inside your browser, so identity photographs and document scans stay on your own device while you fix them. Nothing is uploaded to a server, which means a failed upload to a portal is the only upload that ever happens.