Photo or signature upload rejected? Check the file in this order
A practical checklist for format, pixel dimensions, file-size limits and image-content problems, including when a resizer cannot fix the rejection.
FormAssets · Reviewed
This is technical preparation guidance, not an application authority’s approval. Your current official notice and upload screen take precedence. Numerical examples below are illustrative, not universal requirements.
Keep the error message before changing the image
Write down the exact error and which field rejected the file. “File too large” calls for a different fix from “invalid dimensions”. If the portal gives no specific reason, work through the checks below one at a time. Keep your original and use clearly named new exports so that you do not accidentally upload an old version.
This checklist separates problems you can check locally from decisions only the receiving portal can make. A file that passes local checks is not proof that an application was accepted.
1. Confirm you selected the right file and field
Open the file from your downloads folder. Is it the new photograph or signature, rather than the original scan, a screenshot, or a similarly named older file? If you downloaded a FormAssets application bundle, extract the ZIP and select the appropriate individual JPG. Do not upload the ZIP or readiness report into an image field.
Follow the instructions shown beside that specific field. A signature field and a photo field may have different limits. A separate live-photo step cannot be replaced with a prepared image upload.
2. Check the real format, not just the filename
Renaming signature.png to signature.jpg does not convert the file’s contents. Export or convert it to the required format instead. JPEG, PNG and WebP are distinct formats; MDN’s image-format guide explains their different encoding and compression properties.
FormAssets’ single-image tools read JPG, PNG and WebP inputs and produce JPG output. They do not accept PDF or HEIC. If preparation reports an unsupported image, export a supported image from your device first. If the file itself will not open, return to the original or capture it again; changing the name is not a repair.
3. Compare width and height separately
Check the downloaded image’s pixel dimensions in your image viewer’s information or properties view. Read width first, then height. A 200 × 230 image and a 230 × 200 image are not interchangeable, even though both contain 46,000 pixels.
Enter the required dimensions into the photo resizer. Do not lower them merely to reduce file size when the portal specifies exact dimensions. Use the size control for the byte ceiling, and read the pixels, KB and DPI guide if the instruction uses physical measurements or a density value.
4. Check both ends of the file-size range
“Under 50 KB” and “20–50 KB” are different requirements. A 12 KB image fits the first but not the second. The generic resizers set an upper limit only; they do not enforce the portal’s minimum or produce an exact requested size.
FormAssets uses 1,024 bytes per displayed KB, while a portal may interpret its limit differently. A rounded “50.0 KB” display is not enough to prove compliance. Check the actual byte count where available, and avoid sitting exactly on an unclear upper boundary while still respecting any minimum.
For supported applications, the bundle engine uses the preset’s configured byte range. It can add JPEG comment padding to meet a minimum; padding adds bytes, not detail. A portal may have additional checks, so do not mistake a size-range pass for an acceptance guarantee.
5. Inspect what the image actually shows
Open the exported file, not just the source. Check whether a centre crop removed part of the face or signature, whether fine handwriting remains readable, and whether the background and content match the official instructions. FormAssets does not check identity, photograph recency, background suitability or handwriting content.
For a cut-off signature, use the fit-without-cropping workflow. For a blurry source, retake or rescan it. Increasing pixel dimensions or changing DPI metadata does not recreate missing detail. Do not repeatedly compress an already damaged export.
6. If the file checks out but the portal still refuses it
Save your work using the portal’s own controls before following its documented retry or browser guidance. Check its current notice, upload help and any service-status announcement. FormAssets cannot diagnose an expired login session, a portal-side validation bug or a service outage from the image alone.
Use the authority’s official support channel if the error persists. Provide the field name, exact error, time, browser, file format, dimensions and byte size. Share personal documents only when necessary through the authority’s approved private channel, not a public forum. Do not pay someone merely because they promise guaranteed approval.
Final submission check
After a successful upload, inspect the portal preview and complete the portal’s remaining steps. Keep the acknowledgement or submission receipt if the service provides one. A FormAssets download, readiness report or local “ready” message is not that receipt.