Get an image down to 200 KB — at the best possible quality
“Upload” your photo — except it literally never leaves your device. The tool automatically finds the highest quality that still fits under 200 KB (a binary search over the compression level, at most 8 passes) and shows you the before/after size. The target is preset — nothing else to configure.
Where do 200 KB limits appear?
Mostly on application portals, government forms, club management systems and CMS uploads that want to keep their databases small — a few hundred KB per photo is a common cap there. For perspective on how small that really is: over a 16 Mbit/s DSL line, 200 KB transfers in about 0.1 seconds; an unedited 4 MB phone photo takes twenty times as long.
What if 200 KB cannot be reached?
Then the tool tells you honestly instead of silently delivering an oversized result, and offers the smallest size it achieved. The most effective lever at that point is not more compression but fewer pixels: resize the image first (say, to 1600 px on the longest edge) — after that, 200 KB is almost always easy. Switching to WebP also helps where the portal accepts it.
What exactly does 200 KB mean here?
200,000 bytes. The tool uses 1 KB = 1000 bytes, because an upload limit compares against a byte count and nobody outside knows whether its configuration says 200,000 or 204,800: the decimal reading passes both checks, the binary one fails the first. Windows Explorer divides by 1024 instead and shows the same file as roughly 195 KB — that is not a missed target, just different arithmetic on the same file.
Honest limits
Precisely because application photos and ID scans are sensitive, everything here runs locally in your browser. Re-encoding drops EXIF metadata (for application documents rather an advantage). PNG graphics with hard edges often only reach 200 KB as JPG/WebP — but the tool never forces a format change; the choice stays yours.