WebP Compressor
Trim a WebP further when it still misses the limit you were given.
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.
How to compress WebP files online
WebP is already one of the most efficient image formats. Our tool pushes it further with advanced re-encoding to hit exact file-size targets.
-
1
Upload WebP images
Select your WebP files. Lossy and lossless WebP both work. An animated WebP comes back as its first frame, so keep your original if you need the animation. One file at a time on the free plan.
-
2
Choose target size
Pick a target file size. What comes out is always lossy WebP, at the highest quality factor that reaches your target.
-
3
Download compressed WebP
Download your optimized WebP files ready for the web. The output format stays WebP, no conversion. Individual download or ZIP batch available.
What this compressor does well
Lossy WebP uses the VP8 video codec's intra-frame encoding with predictive coding and adaptive quantization, producing files 25-35% smaller than equivalent JPEGs.
A lossless WebP is accepted, and the result is re-encoded as lossy WebP. That is how the size comes down, so keep the lossless original if you need it.
Unlike JPG, WebP supports full transparency in both lossy and lossless modes. Lossy WebP with alpha is typically 3x smaller than a PNG with the same transparency.
WebP is supported by all modern browsers: Chrome, Firefox, Safari 14+, and Edge. Global browser coverage exceeds 97%, making it safe for production web use.
WebP lossy files are 25-35% smaller than JPEG at the same visual quality, and WebP also supports transparency which JPEG cannot.
The quality factor is searched rather than guessed, so the file lands at the best quality that still reaches your target. Only the first frame of an animated WebP is kept.
Already efficient, so expect less headroom
WebP is already an efficient format, so there is less to reclaim than with JPEG. In our own testing the same photo saved as WebP started at 1.9 MB against 3.4 MB as a JPEG, and a 1MB target cut the WebP by 49% versus 73% for the JPEG. It still hits the size you ask for, but expect an aggressive target to cost visible quality sooner than it would on a JPEG.
Upload limits worth knowing
The caps people most often run into, and what each one really means in practice.
| Where | Limit | In practice |
|---|---|---|
| Gmail | 25 MB | Attachments above this are converted to a Drive link instead of sending. |
| Outlook.com | 20 MB | Outlook desktop against Exchange is often capped lower, at 10 MB. |
| WordPress (default) | 2 MB | Set by PHP's upload_max_filesize; many hosts leave the default in place. |
Email attachments are Base64-encoded in transit, which inflates them by roughly 33%. A 20 MB file arrives as about 27 MB, so a 25 MB cap is really closer to 18 MB of actual payload. Leave headroom rather than compressing to exactly the published limit.
How WebP compression works
WebP is a VP8-derived format that ships in two modes: lossy (≈25-35% smaller than JPG at the same visual quality) and lossless (≈26% smaller than PNG). Whichever goes in, our compressor writes lossy WebP and tunes the quality parameter downward to hit the target. The quality-vs-size curve is smoother than JPG, going from quality 90 to 60 in WebP typically produces less visible degradation than the equivalent JPG drop. All modern browsers (Chrome, Firefox, Safari 14+, Edge) support WebP natively.
Which target size to pick for WebP
Different portals cap WebP uploads at different sizes. Pick the target that matches where you’re uploading rather than shrinking blindly, over-compressing wastes visible quality, under-compressing gets rejected.
Other targets
These have no page of their own. Pick the size in the upload box above.
- 50KB
- CDN thumbnails & og:image tags. WebP thumbnails at 400×300 for card grids, blog listings and e-commerce category pages sit comfortably under 50 KB with lossy quality around 75.
- 150KB
- Product and carousel images. A 150 KB WebP holds a detailed product or carousel image at full width.
- 200KB
- Blog featured images & newsletter headers. Blog featured images at 1200×630 (the OpenGraph standard) in WebP hit 200 KB with quality 85, a good ratio for Substack, Ghost, and Beehiiv newsletter previews.
- 500KB
- Portfolio & case-study web pages. Full-width portfolio images at 1920×1080 in WebP land around 500 KB at high quality (88-92), the sweet spot for design agency case studies, photographer portfolios, and product landing pages where visual quality matters more than shaving the last kilobyte off page weight.
- 1MB
- Progressive Web App splash & shareable graphics. PWA splash-screen assets at 2048×2048 and shareable social graphics with fine detail comfortably fit in 1 MB WebP.
- 2MB
- High-resolution web images. 2 MB fits a high-resolution WebP hero or product zoom image at full detail.