![]() Simply prefix your image URLs with Cloudinary’s fetch URL. ![]() This means, for example, that you can easily integrate Cloudinary with your website without modifying your infrastructure and code. 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. 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’s browsers or mobile apps. ![]() The second image includes f_auto in its delivery URL and so is delivered as either an AVIF ( 14.6 KB – a saving of 56.5%), WebP ( 16.1 KB – a saving of 52%), or JPEG-2000 ( 21.0 KB – a saving of 37%) to supported browsers. The first image uses a URL without Cloudinary’s f_auto 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 example below displays two sample images. Just add the fetch_format parameter and set its value to auto ( f_auto in URLs). The result is that the best image to deliver to your visitor depends on which browser they are using.Ĭloudinary has the ability to automatically detect which browser is requesting the image and then select the most efficient image format to deliver. Some formats such as AVIF, WebP and JPEG-2000 are more efficient than the standard JPEG format for delivering web images, but they are not supported by all browsers. Selecting the Optimal Image Format – f_auto
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |