Cloudinary Blog

How to support WebP images, save bandwidth and improve user experience

Check for WebP Browser Support to Dynamically Deliver Images
Modern image compression techniques have had a large impact on our lifestyle. Digital cameras can save thousands of high-quality photos on a single memory card, smartphones can quickly share high resolution images on-the-fly, and websites and mobile apps can show rich media quickly. All of this just couldn,t have worked if image data was stored at its original, raw form. 
 
Through our apps, browsers and devices, we all use the JPEG lossy format to manage photos efficiently and the PNG lossless format to deliver graphics, icons and drawings.
 
However, while video formats have gone a long way these past few years, image formats have stayed somewhat behind. 
 
This changed at 2010 when Google first introduced the new WebP (pronounced "Weppy") format, an open sourced image format that supports both lossy and lossless image compressions.
 
WebP generates files significantly smaller than the popular JPEG and PNG formats. WebP also supports many advanced features, such as transparencies in its lossy mode, and more eye pleasing degradation in image quality on its lower quality, higher compression settings.
 
Smaller files mean less bandwidth consumption and reduced traffic costs for your online services and better user experience with faster delivery & image sharing times for users of your web sites and mobile apps.
 
In this blog post we wanted to introduce Cloudinary's new cloud-based support for on-the-fly generation of WebP images.
 

Generating smaller images of equal (or better) quality

If you are already familiar with Cloudinary, you probably know that you can tell Cloudinary to do image format conversions on-the-fly simply by changing the file extension of your CDN delivered URLs.
 
Consider for example, a JPG image that was uploaded to the cloud with the public ID 'sample'. Now we want to embed a 300x200px thumbnail of this image on our website. 
 
The left image below is generated by Cloudinary using the JPG format while the right image is generated using the WebP format. Note that you need a Google Chrome browser to view the WebP image correctly.
 
 
   
                           27.9KB JPG                                                              12.4KB WebP
  
If you check the network stats, you will notice that the JPG file is 27.9 KB while the WebP file is just 12.4 KB in size and looks almost the same. This means that we've just saved 56% in bandwidth. If your website includes many images, you can save half of your traffic, get your site to load twice as fast and make your visitors happy.
 
If you use our client libraries, either concatenate '.webp' to the public ID or set the 'format' parameter to 'webp'. For example, in Ruby on Rails and PHP:
<%= cl_image_tag("sample.webp", :crop => :scale, :width => 300) %>
<?php echo cl_image_tag("sample", array("format" => "webp", "width" => 300, 
                        "crop" => "scale")); ?>

 

Lower image quality equals smaller file size

JPG and WebP are lossy formats, allowing you to control the quality of the target image. 
 
There's a clear tradeoff between the target image's quality and its generated file size. In many cases, you will be able to considerably reduce the quality and size of your images while your users will barely notice the difference. 
 
The JPEG format has noticeable artifacts in lower quality levels, especially if fine details or texts are involved. The WebP format has less noticeable artifacts but tends to generate a slightly blurry image in its lower quality settings.
 
You can test that yourself by setting Cloudinary's 'quality' parameter (or 'q' for URLs) to any value between 1 to 99 (the default is 90). 
 
The following example reduces the quality of the sample image to 30%. On the left there's a JPG of 30% quality and on the right a WebP of 30% quality.
 
 
     
                              10.6KB JPG                                                          7.1KB WebP
 
The sharp-eyed will notice the difference. On the other hand, the drastic quality reduction still resulted in an image that can be considered decent, especially when using the WebP format. 
 
The JPG of 30% quality is 10.6KB while the WebP of 30% quality is just 7.1KB in size.
 
In this comparison, the WebP format saved 33% in size, which is very nice. It's interesting to notice that this low quality WebP is just 25% the size of the original JPG while delivering a comparable result, quality-wise.
 
The following Node.js and Django examples generate delivery URLs similar to the example above:
cloudinary.image("sample.webp", { width: 300, crop: 'scale', quality: 30 });
cloudinary.CloudinaryImage("sample.webp").image(width = 300, 
                                                crop = 'scale', quality = 30)

 

Semi-transparent images

Recently, Facebook, Google+ and many other websites, have started to display user profile pictures with a completely circular crop. In order to display such circular images on a non-solid or changing background, the images need to be semi-transparent. The JPG format doesn't support transparent pixels, so you might be forced to use PNG which is far from optimal for this purpose.
 
The following example uses Cloudinary to generate a circular face-detection based thumbnail in the JPG format. The JPG format is effective for this image and takes just 13.6KB. However, as you can see, you cannot place it on a non-white background.
 
 
 
               
 
In order to make the edges transparent, we convert the image to the PNG format. As you can see below, it looks great. But the resulting image is 63.6KB in size which is almost x5 bigger than the JPG version. This will waste bandwidth & money and will harm the user experience.
 

 
The example below generates the same image with the WebP format. The image looks great, the edges are transparent and the file is just 9.8KB in size, which is even smaller than the non-transparent JPG version.
 

 

Lossless WebP images

All WebP examples above were using the lossy WebP format with a 90% quality, or lower. 
 
WebP also supports a lossless format similar to the PNG format. This lossless format is useful for rasterized vector graphics (e.g., logos), that might be visibly degraded in quality using the lossy format.
 
In order to generate a lossless WebP file, simply set Cloudinary's 'quality' parameter to 100:
 

 
Same example in Ruby on Rails:
<%= cl_image_tag("sample.webp", :quality => 100) %>

 

Format adoption

As mentioned above, not all browsers support the WebP format yet. 
 
At present, WebP is supported by Google Chrome, Android 4.0+, and Opera. This is a serious disadvantage, as you'll need to selectively decide when to to utilize it.
 
On the other hand, Chrome is quite popular, especially if you have an application targeted on early adopters and techies. Even if you improve the user experience only for your Chrome users and save only the part of your bandwidth that is consumed by Chrome, it might still be worth the hassle of using WebP. 
 
For example, below you can see the statistics of Cloudinary's web site for the last 30 days. Chrome is responsible for 62% of our traffic.
 
 

Dynamic WebP generation based on visitor's browser

To support serving webp only to Chrome/Android4/Opera visitors, you can use Javascript code to lazy load images according to your visitors’ browsers.
 
Cloudinary's jQuery plugin allows you to dynamically generate delivery URLs that will manipulate your images on the fly and deliver the result through a fast CDN with advanced caching.
 
For example, you can define image tags in your HTML page by setting the 'src' attribute to a blank image and set the 'data-src' attribute to the public ID of the actual image uploaded to Cloudinary ('sample' in this example).
<img src="blank.png" width="150" height="100" data-crop="fill" data-src="sample.jpg"/>
The following jQuery code will convert all image tags to dynamically generated image URLs instead of the placeholder blank image.
$('img').webpify();
The page is loaded quickly without waiting for the images to load. Afterward, the jQuery code above will dynamically update the image tags to display either a WebP image or a JPG image, depending on whether the user’s browser supports WebP or not.
 
Chrome result:
<img src="https://res.cloudinary.com/demo/image/upload/c_fill,h_100,w_150/sample.webp"
         width="150" height="100" data-crop="fill" data-src="sample.jpg">
 
Other browsers result:
<img src="https://res.cloudinary.com/demo/image/upload/c_fill,h_100,w_150/sample.jpg"
         width="150" height="100" data-crop="fill" data-src="sample.jpg">
See our documentation for more details about the jQuery plugin.
 

Summary

Web sites and apps are becoming more and more media-rich. It's important to keep track of our bandwidth utilization, optimize downloads and uploads time and improve our users' experience.
 
The WebP format is another great tool to achieve our goals. With Cloudinary's on-the-fly, cloud-based WebP image format conversion, this becomes much simpler.
 
The WebP format support is available for all our free and paid plans. Sign up now for a free account if you haven't done so already.
 

Recent Blog Posts

Cloudinary Product Gallery Enables Dynamic Buyer Experience

We live in a world where we spend increasingly more time online. As our routines change and adapt to new trends and technologies, we perform more and more of our daily activities in virtual environments. A key example of this is shopping. There are many reasons why online shopping has become so attractive for many buyers. A near endless variety of products is accessible from the palm of your hand. Customer reviews give buyers more confidence in their decisions. It's increasingly easy to search for attractive prices. And the list goes on. But a customer's desire to "touch" or "feel" the product is an interactive experience that can be hard to overcome when shopping online.

Read more
A Guide to Website Image Optimization and Performance

Part 1 of this series delves into the background for this guide. Here in part 2 are the ins and outs.

Wait, hear me out. I know, we just talked about this: Nobody is sheepishly pleading you, “Please, might we have just one more image on the page?” No, I’m not telling you to pick that particular fight. Instead, use a little smoke and mirrors to avoid requests for images that your audience needn’t render right away and might never need at all while loading them asynchronously—only as needed.

Read more
A Guide to Image Optimization for Website Performance

I’ve spent a lot of time thinking about the rules of putting images on the web.

For such a flexible medium as the web, software development can feel like a painstaking, rules-oriented game—an errant comma might break a build, a missing semicolon might wipe out an entire page. For a long time, the laws of image rendering seemed similarly cut-and-dry: For example, if your markups contained an img element , the singular content of its src attribute would be foisted on the audience regardless of their browsing context, period.

Read more
Digital Asset Management Platform: Meeting Customer Expectations

Consumers today expect media-rich experiences. No longer a novelty, it’s second nature to swipe through multiple photos on mobile apps, zoom in on product images for a closer look, visualize online travel reviews, socialize cool video clips while browsing, and encounter brand messages when walking into brick-and-mortar stores. These experiences weave together visual cues and clues with relevant content to create meaning and more authentic connections for customers.

Read more
How to Customize Cloudinary's eCommerce Android App

Recently we added the Cloudinary Demo - eCommerce App to the Google Play Store. This app demonstrates the best practices for optimal delivery of images on a storefront, including category pages, product pages, and a shopping cart. At the time, we published Introducing the Cloudinary Demo Android App, Part 1, which provided an under-the-hood tour of how the eCommerce Android App was designed and how Cloudinary was integrated throughout.

Read more