Compress an image to 100 KB
Drop your photo in. The target is already set to 100 KB. Your browser searches for the highest quality that still fits under it, and nothing is uploaded anywhere.
click to choose · paste from the clipboard · add a whole batch
Nothing here is uploaded. See how the page enforces it.
Who needs 100 KB
The general-purpose ceiling for images on a web page. Page-speed guidance has settled on 100 KB as the point past which a photograph starts measurably delaying a page, and it is also the cap a lot of content management systems and job-application portals impose on uploads.
What an image looks like at 100 KB
At 100 KB and 1000 px you are into territory where most people cannot tell the compressed file from the original without flicking between the two. Photographs with heavy texture (foliage, gravel, crowds) are the exception and will soften first.
Try WebP before JPEG here. At the same visual quality WebP is typically 25-35% smaller, which means it reaches 100 KB with a higher quality setting and therefore a cleaner image. Every current browser supports it.
How the target is hit
Guessing a quality percentage and checking the result is the slow way to do this. Instead your browser encodes the image, measures the actual byte count, and narrows the quality range from both ends over seven passes, each one halving the remaining uncertainty. It stops at the highest quality whose output is still under 100 KB.
If even the lowest acceptable quality is still too heavy, it starts reducing the dimensions instead, because losing pixels is a better trade than reducing a photograph to mush. If it genuinely cannot reach 100 KB, the row says so rather than handing you a file that quietly missed the target.
Questions
+ Is the result exactly 100 KB?
It is at or just under 102,400 bytes, the largest file that still satisfies the limit. Landing on the number precisely would mean padding the file with junk, which no upload form wants.
+ Is 100 KB actually small enough for a fast page?
For one hero image, yes. The number that matters is the total weight of everything above the fold, so ten images at 100 KB is a slow page even though each one passed. If you are optimising a whole page, run the batch and watch the total on the scale.
+ Are my images uploaded?
No. The whole thing runs in your browser through the Canvas API. Open devtools, watch the Network tab while you compress, and you will see no request carrying your file. The page keeps working with your connection switched off.
+ Can I do a whole batch at once?
Yes, and each file gets its own quality search. A simple graphic and a detailed photograph need very different settings to land on the same byte budget. There is no cap on how many, because there is no server to pay for it.
+ Does it work on a phone?
Yes, on iOS and Android. Photographs taken on the phone can be picked straight from the camera roll.