What “to 200KB” means
TargetKB treats 200KB as a maximum, not a visual guess. An upload-ready result is no larger than that limit. It never adds useless bytes just to make the number look exact.
Create a clear image below 200KB for forms, documents, and upload portals, with every trade-off shown before download. The 200KB maximum is already set—add a JPG, PNG, or WebP to begin.
JPG, PNG, or WebP · up to 60 MB
Your image never leaves this deviceQuality first · Dimensions only reduced when necessary
See whether the result passes, what changed, and how the quality looks before downloading.
TargetKB treats 200KB as a maximum, not a visual guess. An upload-ready result is no larger than that limit. It never adds useless bytes just to make the number look exact.
For JPG and WebP, TargetKB searches quality at the original dimensions first. If that cannot meet 200KB and resizing is allowed, it reduces dimensions in reported steps. Auto may use WebP when it is the more practical result.
Nowhere. Decoding, re-encoding, comparison, and download happen in this browser tab. Account and payment servers never receive the image bytes.
The receiving website may also specify dimensions or a file format. Follow those rules together with the 200KB maximum.
Check the destination site’s format and dimension rules as well as its file-size limit.
Yes. A maximum file-size rule is passed by any file at or below 200KB, provided the portal's format and dimension rules are also met.
TargetKB searches quality at the original dimensions first. It only reduces dimensions when that is necessary and allowed, and it reports the change clearly.
Yes, if the scan is JPG, PNG, or WebP. Check that small text stays readable in the comparison before downloading.
No. The browser performs the image work locally; TargetKB servers do not receive the image bytes.
Need a different limit?
Open the flexible KB and MB compressor