Compress WebP to 180KB
Set the ceiling at 180KB, drop your WebP files in, and each one comes back at the highest quality that still fits underneath. Nothing is uploaded.
What happens when you compress WebP to 180KB
WebP typically reaches the same visual quality as JPG at roughly 25 to 30 percent fewer bytes, which makes it the easiest format to hit an aggressive target with. Every current browser displays it, but a few older desktop applications still do not.
WebP is at its best with web images where you control the delivery and know WebP is acceptable. Starting from that kind of source, 180KB is a comfortable target that leaves detail intact. The tool measures the actual encoded bytes on every pass rather than predicting them, so the answer it gives is true for your specific file rather than for an average one.
Who asks for 180KB
An unusual but real cap that appears on a handful of national ID and licensing systems.
Resolution you can keep at 180KB
A useful rule of thumb: a typical photograph at moderate quality costs roughly an eighth of a byte per pixel. Working backwards from 180KB, the practical ceiling is around 1,536,000 pixels — approximately 1520 by 1010. Stay at or below that and the encoder has enough budget to look clean. Push well past it and you are spreading a fixed budget over more pixels, which is where blocking and smeared detail come from.
This is an order-of-magnitude guide, not a promise, because content matters enormously. A flat product shot, a screenshot or a scanned signature compresses several times better than the estimate. A noisy night scene or dense foliage compresses considerably worse, since noise is incompressible by design. When you compress webp to 180kb here the tool measures the real encoded file rather than estimating, so the answer is honest for your specific image.
If the estimate says your photograph is well past that pixel budget, the better move is to reduce the dimensions deliberately before you compress webp to 180kb, choosing what to lose rather than letting the encoder decide. A half-resolution image at a generous quality setting almost always looks better than a full-resolution one squeezed to the same number of bytes.
The method
Most compressors give you a quality slider and let you find out afterwards how big the file turned out. That is the wrong way round when you have a hard ceiling. This tool works backwards from the number: you ask it to compress webp to 180kb, and it searches for the encoder setting that lands just underneath.
The search is a binary search over the JPEG or WebP quality parameter. It encodes at the midpoint of the remaining range, checks the byte count against 180KB, and moves the range accordingly. Nine passes narrow the setting far finer than the eye can resolve, and every pass keeps the best result that fit — so what comes back is the highest quality version that still fits, not the first one that happened to work. Nine passes is also fast enough that you can compress webp to 180kb, look at the result, change the number and run it again without ever waiting on a progress bar.
When quality alone cannot get there, the tool reduces pixel dimensions in steps and searches again. That order matters: dropping quality first preserves your framing, while shrinking first throws away detail no quality setting can recover. Final dimensions are listed next to the file whenever a resize was needed, so an attempt to compress webp to 180kb never quietly returns something smaller than you asked for without saying what it gave up to get there.
Processed locally, never uploaded
Nothing you drop onto this page leaves your device. The image is decoded, re-encoded and handed back entirely inside the browser tab. There is no upload, no queue, and no temporary copy sitting on someone else's disk waiting for a retention policy to delete it.
That matters more than it sounds. The files people most often need to shrink are the ones they should be most careful with: passport scans, signatures, identity documents, medical forms. Handing those to an unknown server in exchange for a smaller file is a poor trade. Because the work is local, you can compress webp to 180kb with the network disconnected and get the same result.
It also means there is no queue to wait in and no daily allowance to run out of. Server-side compressors have to ration free use because every file costs them CPU time; here the CPU is yours, so you can compress webp to 180kb as many times as you like, on as many files as you like, without an account.