WebP Compressor

How to Compress WebP Online

1. Upload Your WebP Files: Drag and drop, or click "+ Add Files" to load one or many .webp images. Static and animated WebP are both accepted.
2. Pick Target File Size (%) or Specific File Size: Choose a percentage of the original (50% halves the file), or enter an exact KB/MB target (e.g. 100 KB). For finer control, switch to Image Quality (%) and set a value between 1 and 100 — 75-85 is the usual sweet spot for photos.
3. Auto Scale (Optional): Leave Auto Scale on so dimensions are nudged down only when needed to hit your size target without crushing quality. Turn it off when you must keep the original pixel dimensions.
4. Compress and Download: Click "Compress". Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after one hour — no sign-up, no watermark, never shared. Download individually or as a single ZIP.

Why Compress WebP?

WebP is already a modern format — Google announced it on September 30, 2010 as a smaller-file alternative to JPEG, PNG, and GIF, with lossy compression derived from the VP8 video codec. But "already compressed" does not mean "as small as it could be". Photographers exporting at quality 95, designers saving lossless WebP from Figma, and CMS plugins that re-encode at conservative defaults all leave significant headroom on the table. Re-encoding at a lower quality factor, switching from lossless to lossy where appropriate, or scaling oversized images to the actual display dimensions often cuts 40-70% with no visible difference.

• Core Web Vitals & SEO — Largest Contentful Paint (LCP) is one of Google's ranking signals; the LCP image is usually the page's hero, and shaving 200-500 KB off it directly improves the score on slower mobile connections.
• CDN and storage bills — A site that serves 10 million WebP impressions a month at an average 150 KB instead of 400 KB saves 2.4 TB of egress every month. At typical CDN rates that is real money.
• Email and chat attachments — Discord caps free-tier uploads at 10 MB per file (lowered from 25 MB in September 2024), Gmail at 25 MB. Multi-megapixel WebP exports often need a trim before they go through.
• Marketplace and form uploads — eBay accepts up to 12 MB per photo, Shopify product images cap at 20 MB, and many government and school portals enforce 1-5 MB caps. Re-encoding to fit the cap is faster than re-shooting.
• Animated WebP shrinkage — Animated WebP from screen-recorders or Lottie exports can balloon past 5 MB. Lowering quality or pruning frames brings them back into "fits on a tweet" territory.
• Faster Git, faster builds — Static-site generators (Next.js, Astro, Hugo) and design repos balloon when committed WebP assets are oversized. Compressing them keeps repo clones and CI builds snappy.

WebP vs JPEG vs PNG vs AVIF — Format Comparison

WebP figures cite Google's WebP compression study, which measured lossy WebP at 0.66-0.75× the file size of JPEG at matching SSIM. The 16,383 px side limit is inherited from the underlying VP8 keyframe bitstream that lossy WebP is built on; see the WebP container specification for the full byte layout.

Lossy vs Lossless WebP — Which to Use

Frequently Asked Questions

How much smaller can a WebP file actually get?

It depends entirely on the source. A WebP already exported at quality 80 from Photoshop typically loses another 20-40% when re-encoded at quality 70-75. A lossless WebP of a photo can drop 60-80% by switching to lossy at quality 80. Animated WebP from a screen-recorder often shrinks 40-60% by lowering quality from 100 to 75 and trimming the frame rate.

Will compressing a WebP that's already compressed make it look worse?

Each lossy re-encode introduces some loss, the same way it does with JPEG. In practice, a single re-encode from quality 90 to quality 75 is almost always visually imperceptible, but repeating that 5-10 times will produce visible artefacts. If you anticipate further editing later, keep an uncompressed master (PNG, TIFF, or lossless WebP) and only ship the lossy version.

Should I pick lossy or lossless WebP?

Photographs, screenshots of GUIs, and any image with smooth gradients should be lossy at 75-85 — the savings are huge and the loss is invisible. Icons, logos, line drawings, and anything with sharp 1-pixel edges should be lossless, because lossy WebP smears those edges. The cheat sheet table above maps common source types to the right mode.

Does every browser support WebP in 2026?

Roughly 96% of global traffic according to caniuse.com. Chrome added partial lossy WebP support in version 17 (2012) and reached full WebP support (including lossless) in version 32 (2014). Firefox added support in version 65 (January 2019). iOS Safari has supported WebP since version 14 (September 2020) and desktop Safari reached full support in version 16 (September 2022); Edge (Chromium) inherited it from January 2020. The remaining ~4% is mostly legacy IE and ancient Android WebView builds — usually safe to ignore, but serve a JPEG fallback via <picture> if you need to cover them.

Why is my animated WebP still huge after compressing?

Animated WebP encodes each frame against the previous one, but if frames change drastically (a screen recording with a cursor flying around, for example) most of the file is irreducible motion. Two reliable levers: lower the quality to 60-70, and drop the effective frame rate by removing every second frame. For very long animations, converting to a real video codec via WebP to MP4 usually shrinks it by another 5-10×.

What's the maximum WebP dimension XConvert can handle?

Lossy WebP inherits a 16,383 px per-side cap from the underlying VP8 keyframe format, and in practice every major encoder (libwebp, browsers, design tools) enforces it. That is a format-level limit, not a tool-level limit. XConvert accepts anything inside that envelope (so up to a ~268-megapixel single image). If your source PNG or TIFF exceeds 16,383 px on either side, scale it down first with Resize WebP or export at lower resolution before compressing.

Are my files uploaded to your server?

files are processed on our servers and deleted automatically after one hour and are not stored long-term. There is no account or sign-up, no watermark added to the output, and your files are not indexed or shared. For the same compression on other formats see Compress PNG, Compress JPG, and Compress GIF.

Should I switch from WebP to AVIF instead?

AVIF (based on the AV1 codec, 2019) typically beats WebP by another 20-30% at the same visual quality, and browser support reached ~95% in 2026. If your audience is on current Chrome, Edge, Firefox, and Safari 16.4+, WebP to AVIF is worth testing. For older Safari and embedded browsers, WebP is still the safer default.

Can I convert WebP back to JPG or PNG after compressing?

Yes. After compressing here, run the output through WebP to JPG for photos or WebP to PNG when you need transparency or lossless. Going the other way — JPG to WebP and PNG to WebP — re-encodes the original and is the cleanest path if you started in those formats.