Private browser tool
Every recruitment notification publishes its own numbers, but they all follow one pattern: a KB ceiling plus exact pixel dimensions, one spec for the photo and a tighter one for the signature. Meet the pattern and any portal accepts the files.
Photos usually get a 20–100KB budget with dimensions like 200×230 or 3.5×4.5cm; signatures get a tighter 10–50KB with a wide box like 140×60. The exact numbers change between notifications and even between years — the current official notification is the only source that counts.
Three causes cover nearly every rejection: the file is over the KB cap, the pixels don't match the required box, or the format is wrong (most portals want JPG for photos). Fix them in that order and the upload goes through.
Crop to the exact required pixels first, then compress to the KB cap — done the other way around you spend your KB budget on pixels you'll throw away. The exam-form pages on this site preset the common crops and targets.
Sign with a dark pen on plain white paper, photograph or scan it straight, and crop tight to the strokes. Line art compresses extremely well — even a 10KB cap keeps a clean signature crisp, especially when the file stays PNG.
Application photos, signatures, and document scans are identity material. Everything on this site is processed in your browser — there is no upload endpoint, so the files never touch a server on the way to the portal.
Verify the downloaded file: exact size on disk, exact pixels, right format — the tool reports all three before you download. Aim a few KB under the cap, and re-read the notification's photo rules (background, recency) that no compressor can fix.
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.