Cloudinary Blog

JPEG-XR conversion with auto browser detection, optimize images for IE users

JPEG-XR converter with auto browser detection

Sites and apps are including more and more high-quality images. The more you can compress images to reduce their size in bytes, the smaller your bandwidth, the faster your site will load and the happier your users will be. But when compressing images, you need to make sure you maintain high visual quality.

Most web sites and mobile apps use the popular JPEG format to display their images and user uploaded photos. The JPEG format has efficient built-in compression that reduces image size while maintaining a reasonable visual quality. But you can reach much better results using more modern image file formats.

A few years ago Google introduced the WebP image format, which is supported mainly by the popular Chrome browser. Cloudinary, a cloud-based image management platform, has supported automatic conversion to the WebP format for some time, and this has proved to be extremely useful in reducing image file size while ensuring the resulting images look great.

In 2009, Microsoft introduced its own modern image format. It is called JPEG-XR, and has been supported by Internet Explorer since version 9. The JPEG-XR format allows saving and delivering high quality photos using significantly less bytes. This format supports both lossy and lossless compression, and includes an alpha channel for supporting semi-transparent pixels.

In this blog post we show how Cloudinary’s cloud service can convert images on-the-fly to the JPEG-XR format, with automatic delivery of JPEG-XR images to users of supported browsers.

On-the-fly JPEG-XR conversion

The following photo was uploaded to Cloudinary, and assigned the identifier seagull. The original image is a 1,000x667 JPEG photo, and it weighs 107KB. Note that in the sample images below we show 500x334 scaled-down versions so they fit better in this post.

Ruby:
cl_image_tag("seagull.jpg")
PHP:
cl_image_tag("seagull.jpg")
Python:
CloudinaryImage("seagull.jpg").image()
Node.js:
cloudinary.image("seagull.jpg")
Java:
cloudinary.url().imageTag("seagull.jpg");
JS:
cloudinary.imageTag('seagull.jpg').toHtml();
jQuery:
$.cloudinary.image("seagull.jpg")
React:
<Image publicId="seagull.jpg" >

</Image>
Angular:
<cl-image public-id="seagull.jpg" >

</cl-image>
.Net:
cloudinary.Api.UrlImgUp.BuildImageTag("seagull.jpg")
Android:
MediaManager.get().url().generate("seagull.jpg");
iOS:
imageView.cldSetImage(cloudinary.createUrl().generate("seagull.jpg")!, cloudinary: cloudinary)
Seagull JPEG
107KB JPEG

Cloudinary makes it possible to modify images on-the-fly using dynamic URLs with parameters that define image manipulations. Simply setting the format parameter in the URL to the desired file type, or changing the file extension to the image URL, instructs Cloudinary to convert the image and display it to users in the target format.

The JPEG-XR format has multiple possible file extensions: .jxr, .hdp and .wdp. The latter is the commonly used one. Setting the format parameter or the URL's file extension to wdp tells Cloudinary to convert the original image to the JPEG-XR format.

Ruby:
cl_image_tag("seagull.wdp")
PHP:
cl_image_tag("seagull.wdp")
Python:
CloudinaryImage("seagull.wdp").image()
Node.js:
cloudinary.image("seagull.wdp")
Java:
cloudinary.url().imageTag("seagull.wdp");
JS:
cloudinary.imageTag('seagull.wdp').toHtml();
jQuery:
$.cloudinary.image("seagull.wdp")
React:
<Image publicId="seagull.wdp" >

</Image>
Angular:
<cl-image public-id="seagull.wdp" >

</cl-image>
.Net:
cloudinary.Api.UrlImgUp.BuildImageTag("seagull.wdp")
Android:
MediaManager.get().url().generate("seagull.wdp");
iOS:
imageView.cldSetImage(cloudinary.createUrl().generate("seagull.wdp")!, cloudinary: cloudinary)
Seagull JPEG-XR
71KB JPEG-XR - Viewable only in IE 9+

The resulting WDP looks great and weighs only 71KB. This means that we saved 34% of the original file size.

Note that to see our sample JPEG-XR images, you should open this blog post in Internet Explorer.

Cropping, resizing and manipulating JPEG-XR images

Cloudinary supports a rich set of image manipulation capabilities that allow you to dynamically adapt your images to your site’s graphic design, and any desktop or mobile device. The following dynamic manipulation URL and sample code generates a 250x300 cropped version of the original seagull while increasing color saturation by 150%

Ruby:
cl_image_tag("seagull.jpg", :width=>250, :height=>300, :effect=>"saturation:150", :crop=>"fill")
PHP:
cl_image_tag("seagull.jpg", array("width"=>250, "height"=>300, "effect"=>"saturation:150", "crop"=>"fill"))
Python:
CloudinaryImage("seagull.jpg").image(width=250, height=300, effect="saturation:150", crop="fill")
Node.js:
cloudinary.image("seagull.jpg", {width: 250, height: 300, effect: "saturation:150", crop: "fill"})
Java:
cloudinary.url().transformation(new Transformation().width(250).height(300).effect("saturation:150").crop("fill")).imageTag("seagull.jpg");
JS:
cloudinary.imageTag('seagull.jpg', {width: 250, height: 300, effect: "saturation:150", crop: "fill"}).toHtml();
jQuery:
$.cloudinary.image("seagull.jpg", {width: 250, height: 300, effect: "saturation:150", crop: "fill"})
React:
<Image publicId="seagull.jpg" >
  <Transformation width="250" height="300" effect="saturation:150" crop="fill" />
</Image>
Angular:
<cl-image public-id="seagull.jpg" >
  <cl-transformation width="250" height="300" effect="saturation:150" crop="fill">
  </cl-transformation>
</cl-image>
.Net:
cloudinary.Api.UrlImgUp.Transform(new Transformation().Width(250).Height(300).Effect("saturation:150").Crop("fill")).BuildImageTag("seagull.jpg")
Android:
MediaManager.get().url().transformation(new Transformation().width(250).height(300).effect("saturation:150").crop("fill")).generate("seagull.jpg");
iOS:
imageView.cldSetImage(cloudinary.createUrl().setTransformation(CLDTransformation().setWidth(250).setHeight(300).setEffect("saturation:150").setCrop("fill")).generate("seagull.jpg")!, cloudinary: cloudinary)
Seagull thumbnail JPEG
19.6KB JPEG

Setting the file format to wdp generates a JPEG-XR version of the same file. The resulting image looks almost identical to the original JPEG but weighs less.

Ruby:
cl_image_tag("seagull.wdp", :width=>250, :height=>300, :effect=>"saturation:150", :crop=>"fill")
PHP:
cl_image_tag("seagull.wdp", array("width"=>250, "height"=>300, "effect"=>"saturation:150", "crop"=>"fill"))
Python:
CloudinaryImage("seagull.wdp").image(width=250, height=300, effect="saturation:150", crop="fill")
Node.js:
cloudinary.image("seagull.wdp", {width: 250, height: 300, effect: "saturation:150", crop: "fill"})
Java:
cloudinary.url().transformation(new Transformation().width(250).height(300).effect("saturation:150").crop("fill")).imageTag("seagull.wdp");
JS:
cloudinary.imageTag('seagull.wdp', {width: 250, height: 300, effect: "saturation:150", crop: "fill"}).toHtml();
jQuery:
$.cloudinary.image("seagull.wdp", {width: 250, height: 300, effect: "saturation:150", crop: "fill"})
React:
<Image publicId="seagull.wdp" >
  <Transformation width="250" height="300" effect="saturation:150" crop="fill" />
</Image>
Angular:
<cl-image public-id="seagull.wdp" >
  <cl-transformation width="250" height="300" effect="saturation:150" crop="fill">
  </cl-transformation>
</cl-image>
.Net:
cloudinary.Api.UrlImgUp.Transform(new Transformation().Width(250).Height(300).Effect("saturation:150").Crop("fill")).BuildImageTag("seagull.wdp")
Android:
MediaManager.get().url().transformation(new Transformation().width(250).height(300).effect("saturation:150").crop("fill")).generate("seagull.wdp");
iOS:
imageView.cldSetImage(cloudinary.createUrl().setTransformation(CLDTransformation().setWidth(250).setHeight(300).setEffect("saturation:150").setCrop("fill")).generate("seagull.wdp")!, cloudinary: cloudinary)
Seagull thumbnail JPEG-XR
16.9KB JPEG-XR - Viewable only in IE 9+

Similar to JPEG, the JPEG-XR has a quality level you can control. While the default quality level is 70, you can set a custom quality level using the quality parameter (when constructing an image URL using Cloudinary’s client libraries), or q when constructing a URL directly. The following URL and sample code sets the JPEG-XR quality to 50:

Ruby:
cl_image_tag("seagull.wdp", :width=>250, :height=>300, :effect=>"saturation:150", :quality=>50, :crop=>"fill")
PHP:
cl_image_tag("seagull.wdp", array("width"=>250, "height"=>300, "effect"=>"saturation:150", "quality"=>50, "crop"=>"fill"))
Python:
CloudinaryImage("seagull.wdp").image(width=250, height=300, effect="saturation:150", quality=50, crop="fill")
Node.js:
cloudinary.image("seagull.wdp", {width: 250, height: 300, effect: "saturation:150", quality: 50, crop: "fill"})
Java:
cloudinary.url().transformation(new Transformation().width(250).height(300).effect("saturation:150").quality(50).crop("fill")).imageTag("seagull.wdp");
JS:
cloudinary.imageTag('seagull.wdp', {width: 250, height: 300, effect: "saturation:150", quality: 50, crop: "fill"}).toHtml();
jQuery:
$.cloudinary.image("seagull.wdp", {width: 250, height: 300, effect: "saturation:150", quality: 50, crop: "fill"})
React:
<Image publicId="seagull.wdp" >
  <Transformation width="250" height="300" effect="saturation:150" quality="50" crop="fill" />
</Image>
Angular:
<cl-image public-id="seagull.wdp" >
  <cl-transformation width="250" height="300" effect="saturation:150" quality="50" crop="fill">
  </cl-transformation>
</cl-image>
.Net:
cloudinary.Api.UrlImgUp.Transform(new Transformation().Width(250).Height(300).Effect("saturation:150").Quality(50).Crop("fill")).BuildImageTag("seagull.wdp")
Android:
MediaManager.get().url().transformation(new Transformation().width(250).height(300).effect("saturation:150").quality(50).crop("fill")).generate("seagull.wdp");
iOS:
imageView.cldSetImage(cloudinary.createUrl().setTransformation(CLDTransformation().setWidth(250).setHeight(300).setEffect("saturation:150").setQuality(50).setCrop("fill")).generate("seagull.wdp")!, cloudinary: cloudinary)
Seagull JPEG-XR quality 50
10.9KB JPEG-XR 50% Quality - Viewable only in IE 9+

It's hard to tell the difference between the 50%-quality JPEG-XR and the higher quality image. This new file weighs only 10.9KB, saving 44% of the original JPEG file.

As mentioned above, the JPEG-XR format includes an alpha channel and supports semi-transparent pixels. This means you can use JPEG-XR to generate semi-transparent images and place them on non-white background. This will save image size and bandwidth because the image contains less pixels.

The following URL creates a circular shape around the same image, by setting the radius parameter to max. As you can see below, the JPEG result on the left has a white background, while the JPEG-XR image on the right has a transparent background. On Firefox, you’d be forced to use PNG for this semi-transparent image, which would have been approximately 10 times the size of this JPEG-XR.

Ruby:
cl_image_tag("seagull.wdp", :width=>250, :height=>300, :effect=>"saturation:150", :radius=>"max", :crop=>"fill")
PHP:
cl_image_tag("seagull.wdp", array("width"=>250, "height"=>300, "effect"=>"saturation:150", "radius"=>"max", "crop"=>"fill"))
Python:
CloudinaryImage("seagull.wdp").image(width=250, height=300, effect="saturation:150", radius="max", crop="fill")
Node.js:
cloudinary.image("seagull.wdp", {width: 250, height: 300, effect: "saturation:150", radius: "max", crop: "fill"})
Java:
cloudinary.url().transformation(new Transformation().width(250).height(300).effect("saturation:150").radius("max").crop("fill")).imageTag("seagull.wdp");
JS:
cloudinary.imageTag('seagull.wdp', {width: 250, height: 300, effect: "saturation:150", radius: "max", crop: "fill"}).toHtml();
jQuery:
$.cloudinary.image("seagull.wdp", {width: 250, height: 300, effect: "saturation:150", radius: "max", crop: "fill"})
React:
<Image publicId="seagull.wdp" >
  <Transformation width="250" height="300" effect="saturation:150" radius="max" crop="fill" />
</Image>
Angular:
<cl-image public-id="seagull.wdp" >
  <cl-transformation width="250" height="300" effect="saturation:150" radius="max" crop="fill">
  </cl-transformation>
</cl-image>
.Net:
cloudinary.Api.UrlImgUp.Transform(new Transformation().Width(250).Height(300).Effect("saturation:150").Radius("max").Crop("fill")).BuildImageTag("seagull.wdp")
Android:
MediaManager.get().url().transformation(new Transformation().width(250).height(300).effect("saturation:150").radius("max").crop("fill")).generate("seagull.wdp");
iOS:
imageView.cldSetImage(cloudinary.createUrl().setTransformation(CLDTransformation().setWidth(250).setHeight(300).setEffect("saturation:150").setRadius("max").setCrop("fill")).generate("seagull.wdp")!, cloudinary: cloudinary)

Seagull non-transparent JPEG Seagull semi-transparent JPEG-XR - Viewable only in IE 9+

                                                  JPEG                                                                       JPEG-XR (IE 9+ only)

Automatic delivery of JPEG-XR and WebP according to user browsers

Users are visiting your site or application using various browsers, but it’s likely that most of them are using either Chrome or Internet Explorer. Optimally, you would want every user to get the image that best matches the capabilities of their current browser. Cloudinary takes care of that automatically.

By setting the format parameter to auto, or f_auto for delivery URLs, Cloudinary dynamically delivers the best matching format: WebP for Chrome and supported Android browsers, JPEG-XR for supported Internet Explorer browsers, and JPEG for all other browsers. The relevant image format is delivered to users via fast CDN.

By dynamically selecting the image format, Cloudinary allows you to deliver high quality images with minimal bandwidth use, and with a very minimal development effort.

Ruby:
cl_image_tag("seagull.jpg", :width=>250, :height=>250, :crop=>"fill", :fetch_format=>:auto)
PHP:
cl_image_tag("seagull.jpg", array("width"=>250, "height"=>250, "crop"=>"fill", "fetch_format"=>"auto"))
Python:
CloudinaryImage("seagull.jpg").image(width=250, height=250, crop="fill", fetch_format="auto")
Node.js:
cloudinary.image("seagull.jpg", {width: 250, height: 250, crop: "fill", fetch_format: "auto"})
Java:
cloudinary.url().transformation(new Transformation().width(250).height(250).crop("fill").fetchFormat("auto")).imageTag("seagull.jpg");
JS:
cloudinary.imageTag('seagull.jpg', {width: 250, height: 250, crop: "fill", fetchFormat: "auto"}).toHtml();
jQuery:
$.cloudinary.image("seagull.jpg", {width: 250, height: 250, crop: "fill", fetch_format: "auto"})
React:
<Image publicId="seagull.jpg" >
  <Transformation width="250" height="250" crop="fill" fetchFormat="auto" />
</Image>
Angular:
<cl-image public-id="seagull.jpg" >
  <cl-transformation width="250" height="250" crop="fill" fetch-format="auto">
  </cl-transformation>
</cl-image>
.Net:
cloudinary.Api.UrlImgUp.Transform(new Transformation().Width(250).Height(250).Crop("fill").FetchFormat("auto")).BuildImageTag("seagull.jpg")
Android:
MediaManager.get().url().transformation(new Transformation().width(250).height(250).crop("fill").fetchFormat("auto")).generate("seagull.jpg");
iOS:
imageView.cldSetImage(cloudinary.createUrl().setTransformation(CLDTransformation().setWidth(250).setHeight(250).setCrop("fill").setFetchFormat("auto")).generate("seagull.jpg")!, cloudinary: cloudinary)
Automatic format WebP, JPEG-XR and JPEG
Auto WebP/JPEG-XR/JPEG

The image above is displayed using different formats according to the user’s specific browser. A WebP image is dynamically shown to Chrome users, and a JPEG-XR image is shown to IE users, significantly saving bandwidth and improving user experience for both.

Summary

Image optimization has become a must for speeding load times of modern sites and apps. Modern and efficient image formats, like WebP and JPEG-XR provide a great solution that combines high visual quality with a high compression rate. However, because these formats are only supported by specific browsers, delivering them is a challenge for developers.

Cloudinary is a cloud-based image management service that aims to simplify image-related development work by taking care of all image-related activities on a website. As a dynamic JPEG-XR converter, which can deliver JPEG-XR to users with Internet Explorer, WebP for users of Chrome, and other image formats for other browsers, Cloudinary allows web developers to improve user experience with only a few lines of code. a very small effort.

Automatic conversion and delivery of the JPEG-XR format is available for all of Cloudinary's plans, including the free plan. If you already have a Cloudinary account and you use the f_auto parameter, JPEG-XR images are already automatically generated and delivered to your Internet Explorer users! Enjoy the reduced bandwidth and faster user experience.

Recent Blog Posts

Hipcamp Optimizes Images and Improves Page Load Times With Cloudinary

When creating a website that allows campers to discover great destinations, Hipcamp put a strong emphasis on featuring high-quality images that showcased the list of beautiful locations, regardless of whether users accessed the site on a desktop, tablet, or phone. Since 2015, Hipcamp has relied on Cloudinary’s image management solution to automate cropping and image optimization, enabling instant public delivery of photos, automatic tagging based on content recognition, and faster loading of webpages. In addition, Hipcamp was able to maintain the high standards it holds for the look and feel of its website.

Read more
New Image File Format: FUIF: Why Do We Need a New Image Format

In my last post, I introduced FUIF, a new, free, and universal image format I’ve created. In this post and other follow-up pieces, I will explain the why, what, and how of FUIF.

Even though JPEG is still the most widely-used image file format on the web, it has limitations, especially the subset of the format that has been implemented in browsers and that has, therefore, become the de facto standard. Because JPEG has a relatively verbose header, it cannot be used (at least not as is) for low-quality image placeholders (LQIP), for which you need a budget of a few hundred bytes. JPEG cannot encode alpha channels (transparency); it is restricted to 8 bits per channel; and its entropy coding is no longer state of the art. Also, JPEG is not fully “responsive by design.” There is no easy way to find a file’s truncation offsets and it is limited to a 1:8 downscale (the DC coefficients). If you want to use the same file for an 8K UHD display (7,680 pixels wide) and for a smart watch (320 pixels wide), 1:8 is not enough. And finally, JPEG does not work well with nonphotographic images and cannot do fully lossless compression.

Read more
 New Image File Format: FUIF:Lossy, Lossless, and Free

I've been working to create a new image format, which I'm calling FUIF, or Free Universal Image Format. That’s a rather pretentious name, I know. But I couldn’t call it the Free Lossy Image Format (FLIF) because that acronym is not available any more (see below) and FUIF can do lossless, too, so it wouldn’t be accurate either.

Read more