Google WebP - Creating Smaller Images for Faster Pages

| by Abel Avram Follow 12 Followers on Oct 01, 2010. Estimated reading time: 1 minute |

Google wants to shrink images transferred over the Internet by proposing a new lossy format called WebP. They claim they have achieved 39% reduction in image byte size leading to speedier page load.

WebP (pronounced "weppy" /(wĕpˈē)/) is an image lossy compression format developed by Google and meant to shrink the size of image files. Google claims that images and photos represent around 65% of the total bytes sent over the Internet these days, which is quite a significant share of all traffic. It is understandable that lowering the number of bytes per picture will have an impact on the average page size, speeding up page loads.

WebP uses a compression algorithm borrowed from the VP8 codec used by Google in WebM, the open source media file format for encoding and compressing video. The overall effect of using WebP is an average of 39% reduction in image byte size after converting 1,000,000 randomly chosen pictures, mostly JPEGs and some PNG and GIFs. Google affirms the image quality has not significantly degraded after the conversion.

WebP is meant to replace JPEG as a better lossy compression format. WebP images are delivered into a lightweight RIFF container, adding a small number of bytes per picture (minimum 20 bytes) but having the ability to contain more in case the picture should be accompanied by more meta-data.

Currently Google is providing a free open source decoder and a conversion tool for Linux x86 64-bit. A Windows version is due in the near future. Google is also working on a WebKit patch enabling Chrome to display WebP images.

An image gallery has been set up to allow anyone to compare the quality of WebP images against their JPEG originals. WebP images have been encapsulated into a PNG container so they can be seen with actual browsers.

Google plans to add support for a transparency layer in the future. WebP belongs to Google’s initiative "Let's make the web faster" including projects like Page Speed, Speed Tracer, and SPDY.

Rate this Article

Adoption Stage

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Don't forget it also saves money by peter lin

Reducing the data sent by 25% can mean a lot of savings for everyone. Not just people paying for bandwidth/hosting. For those with metered internet accounts, reducing file size lowers your monthly usage.

Ahem... by Werner Schuster

Alternative take on webP:

Whatever the technical arguments: a 39% improvement doesn't sound like much of an argument for introducing a whole new image format.

Re: Ahem... by Joe Helfrich

Now, whatever the quality of Google's new format (I haven't even looked at any example images yet) I am absolutely boggled that anyone could say a potential 40% performance improvement wasn't worth at least trying.

Patents etc. by Mike Gale

It would be good if the article had a section about the patent issues.

Web engineers need to reduce the payload size of their pages as well. by Richard L. Burton III

Most HTML in web pages is bloated with tons of noisy HTML due to the lack of CSS knowledge. Going a step further, most applications don't pay attention to acceptance of compressed pages.

Richard L. Burton III
Co-Founder of SmartCode LLC

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

5 Discuss