Private browser tool
A photo straight off an iPhone is usually 2–8MB; upload forms want a fraction of that, often an exact number. Here is what actually works, without installing anything.
Modern iPhones shoot at 12–48 megapixels, and file size follows pixel count. HEIC (Apple's default format) compresses better than JPG, but many portals don't accept it — and a converted JPG of the same shot is even bigger.
Mail offers Small/Medium/Large when you attach a photo, and Messages compresses automatically — fine for sharing, useless for a form that says "maximum 100KB", because you never control the exact output size. The Shortcuts app can resize by dimensions, but it still won't target a KB number.
Open the compressor on this site in Safari, tap the drop zone, and pick the photo. Set the exact KB target the form demands and download the result. When a page only accepts JPG or PNG, iOS converts your HEIC automatically as you pick it — no separate conversion step.
Compression here produces a new downloaded file (in the Files app, Downloads folder); the full-quality original stays in your photo library. And because processing happens in the browser itself, the photo is never uploaded to a server on the way.
Passport-style uploads often pair a KB cap with fixed pixels (600×600, 413×531). Crop to the required dimensions first, then compress — the crop presets on the passport and visa pages handle the common ones.
The tool reports the exact output size and format before you download, and the Files app shows the size on disk. If a portal still refuses the file, the cause is almost always dimensions or format — see our guide on why upload portals reject images.
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.