Private browser tool
The right format depends on what's in the image, not on habit. Here's the two-minute version of how each one earns its keep.
JPG throws away detail your eye is bad at noticing — fine texture, subtle color shifts. For photographs that works brilliantly: a 3MB photo often fits 100KB with no visible damage. The cost: sharp edges (text, line art) get fuzzy artifacts around them.
PNG is lossless — it finds repetition instead of discarding detail. Flat colors, screenshots, logos, and scanned signatures compress beautifully. But a photo has almost no exact repetition, so photographic PNGs are enormous — often 5–10× the JPG size.
Photo → JPG, no contest. Screenshot, logo, signature, or diagram → PNG if it fits the limit, JPG if it doesn't. TidyImage applies exactly this rule: it keeps a PNG as PNG when the target allows, and shows you before you download if it had to convert.
JPG has no transparency. When a transparent PNG must become JPG to fit a limit, transparent areas are flattened onto white — usually what forms expect, but worth knowing before you upload a logo that suddenly has a white box behind it.
WebP compresses a little better than JPG, but plenty of upload portals still refuse it. TidyImage accepts WebP in, and keeps WebP output only where your browser can encode it and it fits — when a portal lists accepted formats, JPG remains the safe answer.
If the form accepts JPG, upload JPG. It's the format every portal on earth tests against, and at the sizes forms display photos, a well-compressed JPG is indistinguishable from the lossless original.
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.