What “to 100KB” means
TargetKB treats 100KB 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.
Compress a photo below a common 100KB portal limit while keeping the highest quality TargetKB can fit. The 100KB 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 100KB 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 100KB 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 100KB maximum.
Check the destination site’s format and dimension rules as well as its file-size limit.
It will be no larger than 100KB. Adding meaningless bytes to hit an exact number does not improve quality and can make a portal reject the file.
Yes. Add the image and TargetKB will search for the highest-quality result that fits under 100KB, reporting any format or dimension change.
JPG usually suits photographs, PNG suits graphics that need transparency, and WebP often gives a smaller file. Follow the destination site's accepted-format rule first.
No. The image remains on your device and is processed locally in your browser.
Need a different limit?
Open the flexible KB and MB compressor