Private browser tool
Getting under 100KB is easy for some photos and genuinely hard for others. Here is what actually determines the outcome, and what to do when a file refuses to shrink.
Read the portal's error message or help text and note the exact number: "under 100KB" and "100KB maximum" are usually the same, but some forms measure in kilobytes of 1000 bytes and reject a 100.2KB file. When in doubt, aim a few KB under — 95KB instead of 100KB costs almost no visible quality.
Three things decide how big an image is: pixel dimensions, visual complexity, and format. A 4000×3000 phone photo has 12 million pixels — no quality setting makes that tiny. A 1200×900 version of the same scene fits 100KB with room to spare. Dimensions are the lever that matters most.
TidyImage runs a binary search across JPG quality levels and keeps the highest one that fits your target. That beats guessing with a quality slider: you get the best image the budget allows, not the first one that happens to fit.
When even the lowest reasonable quality is over budget, the tool scales the image down and tries again. You can also set a max width or height yourself — most portals display photos small anyway, so 800–1200px on the long edge is usually plenty.
Photos compress dramatically better as JPG. Screenshots, logos, and scanned signatures with sharp edges often stay cleaner as PNG — TidyImage keeps PNG as PNG when it fits the target, and only converts to JPG when that's the only way to hit the limit.
Many portals enforce a KB limit and exact pixel dimensions at once (600×600 photos, 35×45mm at specific pixels). Handle dimensions first — crop to the required size — then compress. Doing it in the other order wastes your KB budget on pixels you'll throw away.
After downloading, check the file's actual size on disk. TidyImage tells you the exact output size and whether the target was met — if a portal still rejects the file, the reason is usually dimensions or format, not size. See our guide on why 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.