{"id":21434,"date":"2022-09-11T07:45:47","date_gmt":"2022-09-11T14:45:47","guid":{"rendered":"http:\/\/adaptive_browser_based_image_format_delivery"},"modified":"2025-10-26T14:11:43","modified_gmt":"2025-10-26T21:11:43","slug":"adaptive_browser_based_image_format_delivery","status":"publish","type":"post","link":"https:\/\/cloudinary.com\/blog\/adaptive_browser_based_image_format_delivery","title":{"rendered":"Automatically Reduce Image Size Without Losing Quality"},"content":{"rendered":"

One of the main optimization<\/a> challenges for website and mobile developers is how to display sufficiently high quality images to their visitors while minimizing the image file size. A smaller image file size can lead to faster load times, reduced bandwidth<\/a> costs and an improved user experience. The problem is that reducing the file size too much may lead to a lower image quality and could harm visitor satisfaction. Delivering an optimized image with just the right balance between size and quality can be quite tricky.<\/p>\n

Selecting the Optimal Image Format – f_auto<\/h2>\n

Some formats such as AVIF<\/strong>, WebP<\/strong> and JPEG-2000<\/strong> are more efficient than the standard JPEG format for delivering web images, but they are not supported by all browsers. The result is that the best image to deliver to your visitor depends on which browser they are using.<\/p>\n

Cloudinary has the ability to automatically detect which browser is requesting the image and then select the most efficient image format to deliver. Just add the fetch_format<\/code> parameter and set its value to auto<\/code> (f_auto<\/code> in URLs).<\/p>\n

The example below displays two sample images. The first image uses a URL without Cloudinary\u2019s f_auto<\/code> flag and is therefore delivered in JPEG format across all browsers (while being scaled on-the-fly to 300px width with its aspect ratio retained). The second image includes f_auto<\/code> in its delivery URL and so is delivered as either an AVIF (14.6 KB<\/strong> – a saving of 56.5%), WebP (16.1 KB<\/strong> – a saving of 52%), or JPEG-2000 (21.0 KB<\/strong> – a saving of 37%) to supported browsers.<\/p>\n

\"JPEG<\/a><\/p>\n

\"With<\/a><\/p>\n

\n Loading code examples<\/span>\n <\/cld-code-widget><\/p>\n

The example above demonstrates automatic format selection for images that were uploaded to Cloudinary first, either using our upload API from your server code or directly from your visitor\u2019s browsers or mobile apps.<\/p>\n

In addition to direct uploads, Cloudinary also supports fetching images via their public URLs, transforming these on-the-fly and delivering the resulting images optimized via a CDN. This means, for example, that you can easily integrate Cloudinary with your website without modifying your infrastructure and code. Simply prefix your image URLs with Cloudinary\u2019s fetch URL.<\/p>\n

With Cloudinary\u2019s automatic format feature, you can also dynamically convert and deliver remote images and improve your site\u2019s performance.<\/p>\n

For example, the following URL delivers a picture of Dwayne Johnson from a remote Wikimedia Commons HTTP URL. The remote image is fetched by Cloudinary, stored persistently in the cloud, dynamically converted to AVIF, WebP<\/a> or JPEG-2000 as required by the user\u2019s browser and delivered optimized and cached through a high-end CDN.<\/p>\n

\n Loading code examples<\/span>\n <\/cld-code-widget>\"Remote<\/a><\/p>\n

Under the Hood with f_auto<\/h2>\n

The automatic format feature provides live functionality under the hood, and as browser support evolves and changes, Cloudinary customers get continuously growing value as our serving is updated.<\/p>\n

When it comes to selecting the best format, Cloudinary does not blindly select the format only by browser, and not even by the accepts-header. Cloudinary monitors the browser ecosystem, and thanks to a vast community of users, detects issues in browser support and immediately reacts. Occasionally browser support for different formats gets broken, even if a specific browser advertises that a particular format is supported. Sometimes these failures are partial, for example broken Safari support on a specific version of an operating system, or sometimes the failures are for images with specific attributes, such as transparency, or potentially even more subtle cases.<\/p>\n

Using f_auto<\/code> means that your website media will react to browser bugs and browser updates, based on a per image analysis.<\/p>\n

Reduce Image Size Without Losing Quality<\/h2>\n

Cloudinary\u2019s dynamic format selection feature can be further enhanced by using it together with Cloudinary\u2019s automatic quality selection feature. Including the quality<\/code> parameter and setting its value to auto<\/code> (q_auto<\/code> in URLs) tells Cloudinary to automatically determine the optimum quality setting for an image based on its format and contents, which results in the smallest file size while maintaining visual quality. When you add f_auto<\/code> together with q_auto<\/code> in the delivery URL, the Cloudinary algorithm also checks if a different image format gives a smaller file size while maintaining the visual quality.<\/p>\n

For example, the canyons<\/code> image scaled down to a width of 400 pixels and delivered with both automatic quality selection and automatic format selection (q_auto<\/code> and f_auto<\/code>), will be delivered as either an AVIF<\/a> (14KB<\/strong> – a saving of 62%), WebP (20.2KB<\/strong> – a saving of 45%), or JPEG-2000 (24.3KB<\/strong> – a saving of 34%) to supported browsers, and JPEG (36.6KB<\/strong>) to all other browsers:<\/p>\n

\n Loading code examples<\/span>\n <\/cld-code-widget>\"Optimized<\/a><\/p>\n

Furthermore, when using f_auto<\/code> and q_auto<\/code> together, not only is the visitor\u2019s browser taken into account when deciding on the best image format<\/a>, but also the image contents. For example, the Cloudinary algorithm might determine that the PNG format is a better fit for specific images that contain content such as drawings. For some images, even the PNG8 format can be automatically selected for providing great looking results with a very efficient file size.<\/p>\n

For example, the following URL dynamically generates a 400 pixels wide version of a drawing only using automatic image quality selection (q_auto<\/code> without f_auto<\/code>).<\/p>\n

\n Loading code examples<\/span>\n <\/cld-code-widget>\"Drawing<\/a><\/p>\n

The result is a JPEG image (20.4KB) where, if you look carefully, you can see that the lossy nature of the JPEG<\/a> format resulted in some visual artifacts. In the next example with the same drawing, we will combine both q_auto<\/code> and f_auto<\/code>:<\/p>\n

\n Loading code examples<\/span>\n <\/cld-code-widget>\"Drawing<\/a><\/p>\n

In this case, the algorithm decided to encode the image using the PNG8 format. The image looks better, has no artifacts, and weighs even less – just 16.5KB<\/p>\n

Summary – Automatic Format Delivery<\/h2>\n

Delivering an image in the best format can be easily automated with Cloudinary\u2019s format selection algorithm. The feature can also be combined with automatic quality selection for a powerful and dynamic solution that delivers all your images using minimal bandwidth and maximum visual quality.\nFor more details, see the automatic format selection documentation<\/a>.<\/p>\n

All image transformation and delivery features discussed here are available with no extra charge for all Cloudinary\u2019s plans, including the free plan<\/a>.<\/p>\n

\n

Want to Learn More About Image Optimization?<\/h2>\n