Compress an image to 100 KB

100,000 bytes. This tool uses decimal kilobytes throughout, because that is what the forms imposing these limits almost always mean, and because mixing the two conventions is how a tool ends up producing a 102,000 byte file and calling a 100 KB limit satisfied. The result is always shown so you can check it yourself.

The tool tells you. There is a quality floor below which the picture would be visibly damaged, and rather than grinding past it to technically hit the number, the tool stops and reports the closest size it reached at acceptable quality. You can then download that result, pick a larger target, or reduce the dimensions first - which is usually far more effective than compressing harder.

By measuring rather than guessing. It encodes the image at several quality levels in a binary search, checks the actual byte count each time, and keeps the highest quality whose output fits. There is no estimation and no AI involved; the answer comes from the encoder itself, which is why it is exact.

Because JPEG is the only widely supported format whose file size can be traded against quality smoothly enough to hit a specific target. PNG is lossless, so its size is fixed by the image content and cannot be tuned down to a number. If your image needs transparency, this is the wrong tool - use the ordinary compressor instead.

Yes, as a side effect. The image is re-drawn from raw pixels and re-encoded, and that process has nowhere to carry EXIF, so camera model, timestamps and GPS coordinates do not survive into the output. If removing metadata is your actual goal rather than a bonus, the dedicated metadata remover does it without re-compressing the picture.

No. The compression search runs inside your browser, and a content security policy the browser enforces stops this page sending anything to another domain. That matters more than usual here, because the documents people compress to a size limit are often passports, certificates and application forms.