Google Bought a Video Company in 2009. The Result Is Now the Web's Default Image Format.

Why VP8 Made a Better Image Format Than JPEG

JPEG divides an image into 8-by-8 pixel blocks and applies the Discrete Cosine Transform to each block independently. This approach is efficient but creates visible artifacts when compression is pushed hard, particularly the blocky distortions at sharp edges that designers and photographers recognize as JPEG artifacts. The 8-by-8 block constraint was partly a concession to the computing power available in 1992. Processing larger blocks would have been too slow on the hardware of that era.

VP8-based compression uses a different strategy called intra-frame prediction, borrowed directly from video encoding. Instead of compressing each block in isolation, the encoder predicts what nearby regions should look like based on already-decoded areas of the image and then encodes only the difference between the prediction and the actual pixel data. This difference signal is usually much smaller than the raw data, which means it compresses more efficiently. The blocks VP8 uses are also more flexible in size, allowing the encoder to choose between 4-by-4 and 16-by-16 blocks depending on which produces better results for a given image region.

Google published benchmarks in 2011 showing WebP produced images at roughly 25 to 34 percent smaller file sizes than JPEG at equivalent visual quality. These numbers have been independently verified multiple times since, with variations depending on content. Photographs with smooth gradients and continuous tones benefit more. Images with sharp, high-contrast edges and fine detail see smaller but still meaningful gains.

WebP also introduced something JPEG never had: a lossless compression mode. JPEG is always lossy. Every JPEG file permanently discards information at the moment of encoding and that information cannot be recovered. WebP can encode images completely losslessly, storing every pixel value exactly while still producing files that are on average 26 percent smaller than equivalent PNGs. This made WebP useful for logos, icons, and graphics, not just photographs.

A Decade of Browser Holdouts

Google Chrome added WebP support in version 9, released in 2011. Firefox resisted for years, citing concerns about Google's control of the format and possible patent encumbrances associated with VP8. Firefox did not ship WebP support until version 65 in January 2019. Apple's Safari resisted even longer, adding WebP support only in version 14, released with macOS Big Sur in 2020.

The timing of the holdouts mattered enormously for adoption. Before 2020, serving WebP required detecting the browser and delivering different image files to WebP-capable and non-WebP browsers. This complexity discouraged adoption among smaller websites and developers. After 2020, with Safari onboard, WebP became safe to serve to essentially everyone. Content management systems like WordPress added WebP support in 2021. Image CDNs began converting on-the-fly. The format that had existed since 2010 effectively became mainstream in 2021, when the ecosystem caught up all at once.

What JPG-to-WebP Conversion Actually Does

Converting a JPEG to WebP does exactly what Google designed WebP to do. The JPEG is fully decoded into raw pixel data first, stripping away the JPEG compression entirely. The raw pixels are then fed into the WebP encoder, which applies its VP8-derived algorithm. The output is typically 25 to 35 percent smaller than the original JPEG for photographic content.

Google's Core Web Vitals metrics, which factor into search rankings since 2021, include Largest Contentful Paint, a measure of how quickly the main visual content of a page loads. Large JPEG images are among the most common contributors to slow LCP scores. Converting those images to WebP reduces file size without reducing visual quality, which is one of the highest-return optimizations available for content-heavy websites. Google's PageSpeed Insights has flagged "serve images in next-gen formats" as an actionable recommendation for years, and that recommendation specifically means WebP and AVIF.

The caveat worth understanding is that WebP conversion is one-way in practice. Converting a JPEG to WebP and then back to JPEG introduces generation loss. Each lossy compression cycle discards information permanently. If you convert to WebP for web delivery, keep the original JPEG as your source file. The WebP serves browsers. The JPEG remains your archival copy.

Conclusion

A format built to solve Google's bandwidth problem in 2009 became the web's default image format by 2021, roughly in the time it took the browser vendors who resisted it to relent. The compression gains are real and the web performance benefits are real. When you need to convert JPG images to WebP for your website, the JPG to WebP converter at ToolHQ processes the conversion entirely in your browser. No files are uploaded. Your originals stay on your device.

Frequently Asked Questions

Try These Free Tools