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.
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.
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:
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.
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:
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.
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:
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.
Cloudinary’s jQuery plugin allows you to dynamically generate delivery URLs that will transform 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).
The following jQuery code will convert all image tags to dynamically generated image URLs instead of the placeholder blank image.
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 there is WebP browser support or not.
Purchasing a car online was once considered, at the very least, a risky proposition. Conventional wisdom had it that you had to go “kick the tires” in person, before committing to a big-ticket purchase that will impact one’s finances for some time to come. Like everything else, car buying has…