Compress WEBP to 100KB
Compress WEBP to 100KB online. Reduce your WEBP file to around 100KB for email, uploads and forms, free, fast, no watermark.
Up to 50 MB per file. Sign up free to compress files up to 100 MB.
| File name | Size | Compress to |
|---|
Checking files and selected compression settings.
To reach this size, the pages were turned into images.
The text can no longer be selected, searched or filled in. If you need that, compress again with a larger target.
| File name | Compressed size | Download |
|---|
This page stops at 50 MB and one file per run. Pro compresses files up to 1 GB and a full batch in one go, with a priority queue.
What reaching 100 KB costs a WebP
Set 100 KB as the target and the engine works down to it in steps, stopping at the first result that fits rather than padding the file back out.
A lossy or lossless WebP both go in, and what comes out is always lossy, at the highest quality factor that reaches the target. An animated WebP comes back as its first frame.
Files are processed on our servers, not in your browser. The upload and the result are both permanently deleted within 1 hour, no backups and no copies kept.
No watermark, and no account needed to use it. 2 files a day at up to 50 MB each, one at a time; signing in is free and raises each file to 100 MB.
Reaching 100 KB without the quality tell
-
1
Begin with the largest version you own
The quality parameter is applied once, during this encode. Starting from a JPG that has already been squeezed means its existing artefacts are now part of the picture being encoded, and they will be preserved faithfully.
-
2
Stay in lossy mode
Lossy is correct for anything continuous tone. WebP's lossless mode exists for line art and flat graphics, and it will not bring a photograph anywhere near this target. The default is the right choice unless the image is a diagram.
-
3
Review it at display size
Judge the output in the slot it is going into rather than at full zoom. An image filling a phone screen is seen at roughly a third of the pixel width you are inspecting, and detail you can find only by magnifying is detail nobody will miss.
Why 100 KB stretches further in WebP
A hero image at 1080x720 fits inside 100 KB in WebP at a quality level most readers cannot distinguish from the original. That makes 100 KB a comfortable budget for a single image on a fast page, and WebP reaches it with more of the picture intact than either JPG or PNG manage.
The efficiency is genuine and it is also finite
In lossy mode WebP is about 25 to 35 percent smaller than JPG at matching visual quality, and its lossless mode runs around 26 percent under PNG. The practical effect is that a 50 KB WebP looks about as good as a 100 KB JPG, which is why a single format switch often resolves a Lighthouse complaint with no visible change at all.
The counterpart is that there is less slack to reclaim. The same 4000x3000 photograph measured here weighs 1.9 MB as a WebP against 3.4 MB as a JPG, so the WebP starts closer to its floor. A 1 MB target cuts the WebP by 49 percent and the JPG by 73 percent. A 100 KB request brings that same WebP to 92 KB at 1920x1440, which works, but an aggressive target bites sooner here than the format's reputation suggests.
Where a 100 KB WebP is exactly right
This is the size the managed image pipelines converge on. Cloudflare Images, Vercel Image Optimization and Netlify Image CDN all tend to serve WebP around 100 KB for common viewport widths. If you are serving your own files rather than paying for one of those, hitting this number puts you at the same efficiency they aim for.
It matters most for the one image that decides your Largest Contentful Paint. Google treats 2.5 seconds as the good threshold and the hero image is usually what settles it, so the above the fold picture is where 100 KB earns its keep. Images further down the page can be heavier if they are better for it, provided they load lazily.
The support question, answered honestly
Browsers are no longer the issue. Chrome, Edge, Firefox and Safari 14 and later decode WebP natively, iOS Safari has done so since iOS 14, and only Firefox builds before version 96 lack lossy transparency. If the file is going onto a web page, you can treat support as settled.
Everything else is where it breaks. Government and institutional upload forms frequently accept only JPG, PNG or PDF. Older desktop software, some email clients and plenty of Office installations will show a recipient nothing at all. If the destination is an attachment, a form or a colleague's laptop rather than a browser, compress to JPG instead. An efficient file that will not open is worth less than an inefficient one that will.