1. The file is too large
The most common cause. Portals enforce hard ceilings — 20KB, 50KB, 100KB, 200KB, 500KB, 1MB — and a modern phone photo is 3–8MB straight off the camera. Fix: compress to the stated limit, aiming slightly under it.
Private browser tool
An upload rejection almost always has one of six causes. Work through this list in order and you'll find yours.
The most common cause. Portals enforce hard ceilings — 20KB, 50KB, 100KB, 200KB, 500KB, 1MB — and a modern phone photo is 3–8MB straight off the camera. Fix: compress to the stated limit, aiming slightly under it.
Some forms require exact pixel dimensions (600×600, 413×531) or a maximum ("no larger than 1000px"). A file can be under the KB limit and still be rejected for size in pixels. Fix: crop or scale to the required dimensions first, then compress.
Plenty of government portals accept only JPG/JPEG. A perfectly good PNG or WebP gets refused with a vague error. Fix: convert to JPG — TidyImage does this automatically when needed, and the download's file extension always tells you what you got.
Passport and visa photos are usually square (1:1) or 35×45mm (7:9). Uploading a 4:3 phone photo means either the portal stretches it or rejects it. Fix: crop to the required ratio before compressing — the crop tool's presets lock the ratio for you.
Official photos have rules beyond the file: neutral background, face position and size, no glasses or shadows, taken recently. No compressor can fix these — check the portal's photo specification before you take or pick the photo.
Rarely, uploads fail on EXIF orientation flags, embedded color profiles, or sheer metadata bulk. Re-encoding through TidyImage produces a clean file with no EXIF, no GPS, and default orientation — which fixes this class of rejection as a side effect.
Your image is processed in your browser using its built-in image engine. It is not uploaded to TidyImage, stored on a server, or shared with anyone — the network tab will back us up on this.
TidyImage searches for the highest quality that fits your KB target instead of guessing with a slider. PNG stays PNG when it fits; conversion to JPG happens only when that's the only way in.
Re-encoding produces a clean file: no EXIF, no GPS coordinates, no device fingerprint. For JPGs, the tool shows you what the original was carrying before it strips it.
No. Processing happens in your browser — the image never leaves your device. That's not a policy, it's the architecture: there is no upload endpoint.
The same format you gave when it fits the target — a PNG that fits stays PNG. When only JPG can reach the limit, the tool converts and clearly labels the output. The download's file extension always tells you what you got.
It's removed — re-encoding writes a fresh file with no metadata block at all. For JPG inputs the tool shows a report of what the original contained, so you can see what's being stripped.
No. TidyImage handles file size, dimensions, and format; official portals may also enforce composition, background, and photo-age rules. Check the official specification for anything identity-related.
The tool automatically scales dimensions down when quality alone isn't enough — that resolves almost every case. If a page requires exact dimensions, it will tell you honestly when the target can't be met instead of quietly shipping an oversized file.