Compress WebP Images Online

WebP is already an efficient format, but efficient is not the same as small. Exporters routinely emit WebP at quality 90 or higher, image CDNs pass through whatever they were given, and design tools default to settings tuned for safety rather than size. Recompressing keeps the format and the dimensions and simply re-encodes at a lower quality.

The usual driver is page weight. A media library of a few thousand images at 250 KB each is most of a megabyte of payload on any page that shows a handful of them. Dropping to quality 80 typically halves each file with no difference visible at normal viewing sizes — which shows up directly in Largest Contentful Paint and Core Web Vitals.

The second driver is upload caps. Plenty of forms, marketplaces and job portals enforce a hard per-file limit. Target-size mode binary-searches for the highest quality that fits under a figure you set in KB, so you get the best-looking file that will actually upload. WebP is lossy, so compress copies and keep your originals.

WebP was released by Google in September 2010, built on the intra-frame compression of the VP8 video codec Google acquired with On2 Technologies. Lossless mode (VP8L) and alpha transparency arrived in 2011, animation in 2012. Adoption stalled for most of a decade because Safari refused to ship it, so sites had to serve fallbacks anyway. That ended in September 2020 when Apple enabled WebP in Safari 14, macOS Big Sur and iOS 14 — overnight the format became genuinely universal in browsers. Today Next.js, Cloudflare, Cloudinary, imgix, WordPress and Shopify all emit WebP by default, which is why so many images saved from the web now land on disk as a .webp file.

WebP is already an efficient format, but efficient is not the same as small. Export presets in Figma, Photoshop and most CMS plugins default to quality 90 or higher, image CDNs pass through whatever they were handed, and nobody revisits the setting afterwards. Recompressing keeps the format, the dimensions and the alpha channel and simply re-encodes at a quality that matches how the image is actually used.

Page weight is the usual driver. A media library of 2,000 images averaging 250 KB is half a megabyte of payload on any page showing a couple of them, and images are almost always the largest single contributor to Largest Contentful Paint. Dropping to quality 80 typically halves each file with no difference visible at normal viewing sizes, which shows up immediately in Core Web Vitals and in CDN bills.

The second driver is upload caps. Marketplaces, job portals, ticketing systems and forums all enforce hard per-file limits, and a photo exported at full quality will sail past them. Target-size mode binary-searches for the highest quality that fits under a figure you set in KB, so you upload the best-looking file that will actually go through. WebP is lossy, so compress copies and keep your originals.