The Subtle Triumph of WebP

WebP became the default web image format for most large sites without much fanfare. Adoption happened gradually across browsers, CDNs, and site builders over about a decade, and by the time most developers thought to check, it was already the path of least resistance.

Born From Video, Built for the Web

WebP didn't originate in the world of digital photography, but from video. In 2010, Google took the VP8 video codec from WebM video, and asked if those same compression tricks could work for still images.

The logic was simple and effective. Video codecs had spent decades becoming ruthlessly efficient at compressing visual data frame by frame. Since a single still image is essentially just one frame, Google's engineers extracted the intra-frame compression from VP8. They added essential image-specific features such as alpha channel support for transparency and released it to the world.

The result was a versatile format that could do both lossy compression like JPEG and lossless compression like PNG within a single container. On paper, it was a clear step up for web performance. In practice, the industry was slow to adopt it.

A Decade Of Indifference

WebP launched in 2010 and was largely ignored by the industry for the better part of a decade. While Chrome supported it immediately because Google created both and Opera soon followed, the rest of the web remained silent. Firefox held out until 2019 and Microsoft Edge only adopted it after switching its internal engine to Chromium. Safari remained the most significant holdout of all.

The hesitation was never about technical merit. WebP was demonstrably better than JPEG in nearly every measurable way.

Instead, the format fell into the classic chicken and egg trap of web development. Developers avoided a format that browsers didn't support while browser makers saw no reason to prioritize a format that developers were not using. This stalemate gave everyone a convenient excuse to do nothing.

Apple remained the final hurdle. Because Safari on macOS and iOS represented a massive portion of global web traffic and refused to render the files, using WebP required creators to maintain fallback images. This essentially doubled the workload so most people stuck with JPEG to save time.

The solutions required during this period were notoriously tedious. Developers had to rely on complex picture elements with multiple source tags or server side scripts to negotiate content. Many teams eventually decided to simply serve JPEGs to everyone because the extra effort was not worth the trouble. This messy compromise defined the landscape for years.

Safari Adds Support, Adoption Follows

The turning point arrived in 2020 when Apple finally added WebP support to Safari 14 on macOS Big Sur with iOS Safari following shortly after. By 2022 every major browser on every platform could handle WebP natively.

Once developers could serve the format without worrying that a massive chunk of users would see broken images adoption accelerated quickly. Content Delivery Networks such as Cloudflare began auto-converting images to WebP on the fly while WordPress added native support. Squarespace, Shopify, and nearly every other website builder followed suit. Even Google's own PageSpeed Insights began penalizing sites that failed to serve WebP.

The format that had been considered too new or poorly supported for a decade suddenly became the path of least resistance.

Why WebP Actually Wins

WebP's main practical win is better lossy compression. At visually equivalent quality, a WebP file is typically 25-35% smaller than a comparable JPEG. That's marginal for a single hero image but matters on image-heavy sites, where the cumulative effect is faster pages and lower bandwidth costs.

On the lossless side, WebP produces files roughly 26% smaller than PNG by using modern spatial prediction and a color cache - techniques more sophisticated than the algorithms PNG has relied on since the mid-nineties. A bigger practical win is alpha channel support in both lossy and lossless modes. JPEG has no transparency at all, and PNG files with transparency are often very large; WebP sits in the middle, so a photo with a transparent background can ship at a fraction of a PNG's weight.

WebP also handles animation better than GIF: full 24-bit color, alpha transparency, and meaningfully smaller files at equivalent quality (commonly 30-50% smaller for typical clips). By combining the core strengths of JPEG, PNG, and GIF in one container, WebP has quietly become the default format in much of the modern web stack.

The Practical Limits of WebP

WebP has real limitations that are worth understanding before fully committing to the format:

• No CMYK color space: WebP only supports RGB and YUV color spaces, which makes it irrelevant for print production pipelines or prepress work.
• Limited HDR support: The 8-bit per channel ceiling is starting to look dated as modern displays move toward high-dynamic-range content with wider color gamuts.
• Slower encoding speed: The lossy encoder is noticeably slower than that of a JPEG. While not a dealbreaker for most, the extra processing time adds up during massive batch operations.
• Maximum dimensions: The format caps out at 16,383 x 16,383 pixels, which creates a hard wall for ultra-high-resolution photography or satellite imagery.
• Ecosystem inertia: While the web has fully embraced the format, many professional desktop tools and image viewers still treat WebP as a second-class citizen compared to legacy formats.

WebP Guidance for Developers and Designers

If you are a web developer, you should be serving WebP by default. The browser support argument evaporated years ago and the performance gains are essentially free money on the table. Most CDNs and image optimization services will now handle the conversion for you automatically.

If you are a photographer or designer, WebP is not going to replace your RAW or TIFF workflow, nor should it. However, for anything destined for a screen and especially for web delivery, there is no good reason to stick with JPEG. You should convert on export because the file size difference adds up fast.

If you are someone who saves images from the web and gets confused when they open as WebP files that your computer does not recognize, know that this is a common frustration. The situation is improving because most operating systems now handle WebP natively. If yours does not, it is likely time for an update.

Where Things Stand

Fifteen years after its launch, WebP has become the default image format for web delivery. Most people who encounter it daily have never even heard its name. It won by being consistently and measurably better than JPEG and PNG in the one context that mattered most: browser rendering. By outlasting the holdouts on browser support, it solidified its position. While AVIF will likely surpass it eventually, WebP remains the standard you should be serving today.