Private browser tool
Every photo from a phone carries an invisible dossier: where it was taken, when, and on what device. Before you upload a photo anywhere, it's worth knowing what you're attaching to it.
JPG files carry an EXIF block written by the camera: GPS latitude and longitude (often precise to a few meters), the exact date and time, device make and model, and sometimes editing-software history. None of it is visible in the image — all of it travels with the file.
A photo posted or uploaded with GPS data can reveal your home address. A "taken yesterday" photo with a three-year-old timestamp can undermine an application. Metadata is the part of the file you can't see and rarely think to check.
The tool re-draws your image onto a fresh canvas and encodes a brand-new file. The new file has no EXIF block at all — no GPS, no device info, no timestamps. This isn't an extra option to enable; it's how the compression works, every time.
When you drop a JPG into TidyImage, the metadata report shows what the original contains — flagging GPS coordinates specifically — so you can see exactly what's being removed. The report runs in your browser like everything else; the photo is never uploaded.
The metadata report reads JPG EXIF, which is where GPS data lives in practice. PNG and WebP inputs get the same clean re-encode (their metadata is discarded too), but the before-report is JPG-only for now. And remember: stripping metadata doesn't anonymize what's visible in the image itself.
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.