Image transformations

Cloudinary's dynamic URL transformations enable you to programmatically generate multiple variations of your high quality original images on the fly, without the need for graphic designers and fancy editing tools.

You can build these URLs manually in your code, or take advantage of Cloudinary's SDKs, which enable you to write your transformation code using intuitive syntax designed for your preferred programming language or framework and let the SDK automatically build these URLs for you.

Here are just a few examples of some popular use cases that you can accomplish on the fly by combining Cloudinary transformations. Click each image to see the URL parameters applied in each case:

Convert format, round,
change aspect ratio & crop to face,
add outlines & shadows Place, style, and format
image and text layers Apply special effects like
cartoonify and brightness,
rotate to any angle

Overview

Cloudinary allows you to easily transform your images on the fly to any required format, style and dimension, and apply effects and other visual enhancements. You can also optimize your images to deliver them with minimal file size alongside high visual quality for an improved user experience and minimal bandwidth. You can do all of this by implementing dynamic image transformation and delivery URLs. Your transformed images are then delivered to your users through a fast CDN with optimized caching.

With image transformations, you can:

• Deliver images using the image format that fits your needs.
• Resize and crop your images to the required dimensions using different scaling and cropping techniques, or use our smart cropping techniques, including face-detection or auto-gravity for cropping to focus on the most relevant parts of a photo.
• Generate a new image by layering other images or text on your base image.
• Apply a variety of effects, filters, and other visual enhancements to help your image achieve the desired impact.

On this page:

• Overview
  • Quick example
• Transformation URL syntax
  • Transformation URL structure
  • Delivery types
  • Parameter types
  • Transformation flags
  • Generating secure HTTPS URLs using SDKs
  • Verbose vs non-verbose syntax
  • Asset versions
• Chained Transformations
• Named Transformations
  • Creating named transformations
  • Transformation Builder
  • Named transformation examples
  • Chaining named transformations
  • Limitations of named transformations
  • Named transformation video tutorial
• Embedding images in web pages using SDKs
  • Cloudinary URL helper method
  • Cloudinary image tag helper method
• Image format support
  • Delivering in a different format
  • f_auto
  • Supported image formats
• Image transformation types
• Delivering optimized and responsive media
• Create new images

Rate this page:

Quick example

Below you can see the transformation URL and corresponding SDK code for generating an image with several transformation parameters applied:

• Scales and tightly crops the image to fit into a 200px x 200px square, centering on the auto-detected face: /c_thumb,g_face,h_200,w_200/
• Rounds the corners to a circle: /r_max/
• Converts and delivers the image in the best transparent format for the requesting browser. For example, webp or avif: /f_auto/

https://res.cloudinary.com/demo/image/upload/c_thumb,g_face,h_200,w_200/r_max/f_auto/woman-blackdress-stairs.png

Original

 

 

 

Transformed image

Transformation URL syntax

Your Cloudinary media assets are accessed using simple delivery HTTP or HTTPS URLs, which are then delivered to users via a worldwide fast CDN. The URL contains the public ID of the requested asset plus any optional transformation parameters. The public ID is the unique identifier of the asset and is either defined when uploading the asset to Cloudinary, or automatically assigned by Cloudinary (see Uploading Assets for more details on the various options for specifying the public ID).

Generating transformation URLs with Cloudinary SDKs

Cloudinary's SDKs automatically build the transformation URL for you. They allow you to continue working in your preferred developer framework and also provide helper methods to simplify building image tags and image transformation URLs.

Transformation URL structure

The default Cloudinary asset delivery URL has the following structure:

In the most general case of simply delivering images that were uploaded to your Cloudinary product environment without any transformations, the delivery URL will be in the format:

https://res.cloudinary.com/<cloud_name>/image/upload/<public_id>.<extension>

For example, delivering the image with a public ID of: leather_bag_gray, from the demo product environment in jpg format:

https://res.cloudinary.com/demo/image/upload/leather_bag_gray.jpg

The following shows an example of delivering the same image, this time with transformation parameters applied, so that the image is scaled down and then cropped to fill a 250px square (aspect ratio of 1:1 = 1.0) and then a light blue border is applied:

https://res.cloudinary.com/demo/image/upload/ar_1.0,c_fill,h_250/bo_5px_solid_lightblue/leather_bag_gray.jpg

Transformation URL tips

• For customers with a Custom delivery hostname (CNAME) - available for Cloudinary's Advanced plan and above - the basic image delivery URL becomes: https://<custom delivery hostname>/image/upload....
• You can convert and deliver your image in other supported image formats by simply changing the image format file extension. For details, see Delivering in a different format.

• You can append an SEO-friendly suffix to your URL by replacing the image/upload element of the URL with images and then appending the desired suffix with a slash (/) after the public ID and before the extension. For example, if you have a cooking image with a random public ID like: abc1def2, you can deliver your image as:

  https://res.cloudinary.com/<cloud_name>/images/upload/a12345/cooking.jpg

  For more details, see Dynamic SEO suffixes.

• You can also use shortcut URLs when specifically delivering image files using the default upload type. With Cloudinary's Root Path URL feature, the <asset_type> and <delivery_type> elements can be omitted from the URL (they automatically default to the values image and upload respectively). For example, the Root Path shortcut delivery URL for the cropped image above is:

  https://res.cloudinary.com/demo/c_crop,h_200,w_300/sample.jpg

Transformation URL video tutorial

The following video provides a quick demonstration of how dynamic transformation URLs work with both images and videos.

Video Player is loading.

Play Video

Play

Mute

Current Time 0:00

/

Duration -:-

Loaded: 0%

0:00

Stream Type LIVE

Seek to live, currently behind liveLIVE

Remaining Time --:-

 

1x

Playback Rate

• 2x
• 1.5x
• 1.25x
• 1x, selected
• 0.5x

Descriptions

• descriptions off, selected

Captions

• captions off, selected

Audio Track

Fullscreen

This is a modal window.

The media could not be loaded, either because the server or network failed or because the format is not supported.

Tutorial contents

Delivery types

The delivery type element of the URL provides an indication about the way the asset will be delivered, although in most cases, the delivery type value is determined at the time that the asset is stored in Cloudinary.

The following delivery type values are supported:

Parameter types

There are two types of transformation parameters:

• Action parameters: Parameters that perform a specific transformation on the asset.
• Qualifier parameters: Parameters that do not perform an action on their own, but rather alter the default behavior or otherwise adjust the outcome of the corresponding action parameter.

It's best practice to include only one action parameter per URL component.

If you want to apply multiple actions in a single transformation URL, apply them in separate chained components, where each action is performed on the result of the previous one.

In contrast, qualifier parameters must be included in the component with the action parameter they qualify.

• Most qualifiers are optional, meaning the related action parameter can be used independently, but you can add optional qualifiers to modify the default behavior.
• In some cases, an action parameter requires one or more qualifiers to fully define the transformation behavior.
• There are a few parameters that can be used independently as action parameters, but can also be used in other scenarios as a qualifier for another action.

For example, the transformation below includes multiple transformation actions. The qualifier transformations included together with a particular action define additional adjustments on the transformation action's behavior:

https://res.cloudinary.com/demo/image/upload/ar_1.0,c_thumb,g_face,w_0.7/r_max/co_skyblue,e_outline/co_lightgray,e_shadow,x_5,y_8/docs/blue_sweater_model.png

In this transformation:

• The aspect ratio, gravity, and width qualifiers control the way the thumbnail crop action will be performed.
• The rounding action doesn't have any qualifiers.
• The color qualifier overrides the default color of the outline effect action.
• The color qualifier overrides the default shadow effect color, while the x and y qualifiers adjust its placement.

Transformation flags

Transformation flags alter default transformation behavior. In some cases, they alter the default behavior of the transformation URL as a whole. In other cases, they alter the behavior of one or more specific transformation parameters that must be used together in the same URL component.

In general, tens of flags are available that can alter delivery and format, cropping and positioning, overlays, metadata and color profiles, as well as PDF and text behaviors, just to name a few.

For example:

• fl_attachment alters the normal behavior of the overall transformation. Instead of delivering an asset in a web page, it causes the transformed media file to be downloaded as an attachment. This flag can be used independently of other transformations.

• fl_relative modifies the way overlay resize parameters are evaluated. This flag can only be used in conjunction with the overlay (l_) parameter.

• fl_layer_apply tells Cloudinary to apply all chained transformations, until a transformation component that includes this flag, on the last added overlay or underlay asset instead of applying them on the base asset. This flag acts as an indicator to close the layer section of the transformation, similar to a closing bracket. Placement definitions for how the layer should be applied, such as gravity and offsets are also defined in the component with this flag.

For details on all available transformation flags, see the flag section of the Transformation Reference.

Generating secure HTTPS URLs using SDKs

For backward compatibility reasons, some of Cloudinary's earlier SDK major versions generate http URLs by default. When using one of these SDKs, you'll generally want to instruct the SDK to generate https URLs by setting the secure parameter to true globally as part of your SDK configuration. However, you can also pass the secure option locally in each transformation operation.

The following example shows only the SDKs and library versions that require passing secure = true to generate HTTPS:

<Image publicId="phone_tree.jpg" secure="true">

</Image>

Verbose vs non-verbose syntax

Some transformation parameters with multiple options offer two alternative syntaxes for defining the option values:

• Verbose, unordered: Each option of the transformation (whether required or optional) is specified in the verbose format name_value and each option is separated by a colon (:) or semicolon (;) depending on the transformation.

  The options can be specified in any order, and you only need to include those that you want (or are required) to define.

  With this syntax, you can also choose to specify only the options for which you don't want to use default values and default values will be applied for the others.

• Non-verbose, ordered: Transformation options are specified only by values, and must be entered in the pre-defined option order for that transformation. All values from the syntax to the left of the value you want to supply must also be entered.

Transformations that support both verbose and non-verbose URL syntax are indicated as such in the Transformation Reference. When both are supported, SDKs always output the verbose syntax.

Verbose vs non-verbose example

The theme effect supports the color and photosensitivity options, but you can specify them in a different order using verbose syntax. For example:

e_theme:photosensitivity_110:color_black

However, when using non-verbose syntax, you must specify the parameters in order. Therefore, even if you only want to change the default behavior of the photosensitivity (last) option, you must still specify the value to use for the color (first) option:

e_theme:black:110

Asset versions

The version component is an optional part of Cloudinary delivery URLs that can be added to bypass the CDN cached version and force delivery of the newest asset. Cloudinary returns the value of the version parameter as part of every upload response, and the returned url and secure_url parameters also include the version component, which represents the timestamp of the upload.

• Delivering the URL without a version value will deliver the cached version on the CDN if available or will request the latest version from Cloudinary if not cached (or when the cached version expires).
• Delivering the URL with a version will deliver the cached CDN version only if the cached version matches the requested version number. Otherwise, it will bypass the cached CDN version and immediately request and deliver the latest version from Cloudinary.

Example image delivery URL without version:

https://res.cloudinary.com/demo/image/upload/water-park-aerial-view.jpg

Example image delivery URL with version:

https://res.cloudinary.com/demo/image/upload/v1699883548/water-park-aerial-view.jpg

Chained Transformations

Cloudinary supports powerful transformations that are applied on the fly using dynamic URLs. You can combine multiple transformation actions together as part of a single delivery request, e.g., crop an image and then add a border to it.

In general, it's best practice to chain each transformation action in your URL as a separate component in the chain.

To support chained transformations, Cloudinary's transformation URLs allow you to include multiple transformation components, each separated by a slash (/), where each of the transformation components is executed on the result of the previous one. Cloudinary's SDKs can apply multiple transformation components by specifying the transformation parameter and setting it to an array of transformation maps.

Examples:

1. Three chained transformations: fill to a 250px square, then round to a circle, and deliver in the optimal transparent format:

   URL

   Node.js

   React

   Vue.js

   Angular

   JS

   Python

   PHP

   Java

   Ruby

   .NET

   Dart

   iOS

   Android

   Flutter

   Kotlin

   jQuery

   React Native

   https://res.cloudinary.com/demo/image/upload/ar_1.0,c_fill,w_250/r_max/f_auto/livingroom-yellow-chair.png

   Open In Transformation Builder
   

2. Five chained transformations: Fill to a 250*400px portrait, then rotate the result by 20 degrees, then add a brown outline to the rotated image, and optimize the resulting image to deliver with the best compression that gives good visual quality and in the optimal transparent format:

   URL

   Node.js

   React

   Vue.js

   Angular

   JS

   Python

   PHP

   Java

   Ruby

   .NET

   Dart

   iOS

   Android

   Flutter

   Kotlin

   jQuery

   React Native

   https://res.cloudinary.com/demo/image/upload/c_fill,h_400,w_250/a_20/e_outline,co_brown/q_auto/f_auto/kitchen-island.png

   Open In Transformation Builder
   

Named Transformations

A named transformation is a pre-defined set of transformation parameters that has been given a custom name for easy reference. Instead of applying each of the required transformations separately to an asset, you can apply a single named transformation to apply all the transformations defined for it. This makes it easy to:

• Reuse transformations on multiple assets
• Shorten complex transformation URLs
• Hide the details of a transformation in your delivery URL.
• Simplify the enabling/disabling of transformations in Strict Transformations mode.

Named transformations can include other named transformations, which allows you to define a chain of transformations to run on multiple assets more easily.

Named transformations are required for baseline transformations, which save processing time and cost by avoiding regeneration of the baseline part of the transformation.

You can create and manage named transformations via the API or in the console UI using the Transformation Builder.

Once the named transformation has been defined, you can transform an asset with the transformation parameter (t for URLs) and the name of your named transformation. For example t_instagram-auto-crop.

You can include user-defined variables in your named transformations, and then pass the value for the user-defined variable into the transformation from an external source. This enables creating a named transformation 'template' with a lot of flexibility.

For example, you could define a complex named transformation that includes a text overlay as a named transformation, using a user-defined variable for the text string value.

You can also set named transformations as transformation templates, which you can apply as templates in the Media Library so that you can preview how assets will look with different named transformations applied.

For more details, see user-defined variables. For a use-case example demonstrating named transformations with user-defined variables, see Named transformation with a user-defined variable.

Creating named transformations

You can create a named transformation programmatically or using the Transformations UI in your Cloudinary console:

To create a named transformation programmatically, use the Transformations Admin API method. The following example defines a named transformation called small_profile_thumbnail that uses automatic cropping to resize assets to the required size for a particular application's thumbnail display:

curl \
  -d 'transformation=w_100,h_150,c_fill,g_auto' \
  -X POST \
  https://<API_KEY>:<API_SECRET>@api.cloudinary.com/v1_1/<CLOUD_NAME>/transformations/small_profile_thumbnail

For more details and examples, see the Create Transformation method in the Admin API Reference.

To create a named transformation using the UI: Expand the Transform and Customize section, accessible from the Console Product Navigation menu.

From here, there are a few ways to create a named transformation:

• Start with a transformation from the Transformations Center as a template and experiment with it in the UI, click Use it to open the Transformation Builder and refine the transformation to your needs, and finally save it with your chosen name.
  
• View all your delivered dynamic transformations (those that were generated and delivered on the fly) in the Log tab of the Manage Transformations page and save one of those with your chosen name.
• Create a new transformation from scratch using the Transformation Builder (Beta) and save with your chosen name. Open the builder by clicking New Transformation from either of the Transform and Customize pages.

Once you've saved your named transformations, you can view a list of them on the Named Transformations tab of the Manage Transformations page of the Console. From here, you can edit, copy, or enable/disable Strict Transformations.

To access the page:

• If you have the new App Console, the page is part of the Image product: Image > Manage Transformations .
• If you have the Classic Console, go to Programmable Media > Manage Transformations.

You can also select to include a transformation as a preset so that it can be applied to an asset in the Download Options tab of the asset management drill-down page (available for Assets Enterprise plans).

Transformation Builder

The Cloudinary Transformation Builder is the UI for creating and saving your transformations in a simple and easy to use way. The Transformation Builder has two modes of operation:

• Construct: Build transformations manually by selecting and configuring transformation actions.
• Converse: Build transformations using AI chat by describing the transformation with natural language.

Transformation Builder video tutorial

Watch this video for a quick introduction to the Transformation Builder:

Video Player is loading.

Play Video

Play

Mute

Current Time 0:00

/

Duration -:-

Loaded: 0%

Stream Type LIVE

Seek to live, currently behind liveLIVE

Remaining Time -0:00

 

1x

Playback Rate

• 2x
• 1.5x
• 1.25x
• 1x, selected
• 0.5x

Descriptions

• descriptions off, selected

Captions

• captions off, selected

Audio Track

Fullscreen

This is a modal window.

The media could not be loaded, either because the server or network failed or because the format is not supported.

Tutorial contents

Create a transformation using the Builder

To create a new transformation, open the Builder and select the mode to use.

Construct mode

The Transformation Builder in construct mode provides:

• A simple and intuitive UI for selecting and configuring transformation actions - easily discover actions and parameters as you build.
• Transformations built as a series of self-contained actions so you can see the results of each one as you apply it.
• URL and SDK code ready to copy and paste directly to your code.
• The ability to update the default preview image to something from your own product environment.
• Quick edit functionality, to easily add transformations using URL syntax.

The builder supports most common transformation actions. If the transformation action you are trying to apply is not listed, you can add an Additional Transformation action and use transformation URL syntax to specify your transformation. Alternatively, you can switch to the legacy editor to create your transformation.

Converse mode

The Transformation Builder in converse mode provides:

• An AI-powered conversational interface to describe the transformation you want to create with natural language.
• Iterative prompts to continue the conversation and perfect the transformation.
• URL and SDK code ready to copy and paste directly to your code.
• The ability to update the default preview image to something from your own product environment.

Named transformation examples

Below are two quite different named transformations applied to the same lighthouse_reflection image:

• fill_square_400 is defined as ar_1:1,c_fill,g_auto,w_400, which fills (scales and crops) the image into a 400*400 square, automatically focussing on the most interesting area of the image:
  URL

  Node.js

  React

  Vue.js

  Angular

  JS

  Python

  PHP

  Java

  Ruby

  .NET

  Dart

  iOS

  Android

  Flutter

  Kotlin

  jQuery

  React Native

  https://res.cloudinary.com/demo/image/upload/t_fill_square_400/lighthouse_reflection.jpg

  Open In Transformation Builder
  

   

• rounded_cartoonified_frame is defined as e_cartoonify/r_max/co_rgb:add8e6,e_outline:30/b_rgb:add8e6, which applies a cartoonify effect, rounds it to a circle or oval shape, adds a light blue outline around the oval so that the image won't be touching the edges of the frame, and then fills the transparent background with the same color as the outline:
  URL

  Node.js

  React

  Vue.js

  Angular

  JS

  Python

  PHP

  Java

  Ruby

  .NET

  Dart

  iOS

  Android

  Flutter

  Kotlin

  jQuery

  React Native

  https://res.cloudinary.com/demo/image/upload/t_oval_cartoonified_frame/lighthouse_reflection.jpg

  Open In Transformation Builder
  

Chaining named transformations

You can chain named transformations before or after other transformations. For example, here the oval_cartoonified_frame named transformation is applied after a grayscale effect:

https://res.cloudinary.com/demo/image/upload/e_grayscale/t_oval_cartoonified_frame/lighthouse_reflection.jpg

https://res.cloudinary.com/demo/image/upload/t_fill_square_400/t_rounded_cartoonified_frame/lighthouse_reflection.jpg

It is now simple to specify a single named transformation and apply it to any asset:

https://res.cloudinary.com/demo/image/upload/t_fill_circle_cartoon/sunset_lake.jpg

Where the fill_circle_cartoon named transformation is defined as: t_fill_square_400/t_rounded_cartoonified_frame.

Limitations of named transformations

Automatic format

The automatic format transformation parameter (f_auto) is not effective if used in named transformations.

When f_auto is used in a delivery URL, the CDN layer determines the best format to deliver. If this parameter is hidden in a named transformation then it is not visible to the CDN.

You can use f_auto together with a named transformation by chaining the components, for example, t_square/f_auto.

Automatic quality

The automatic quality transformation parameter (q_auto) is effective in named transformations, except in one situation.

When q_auto is used in a delivery URL and the browser sets the Save-Data HTTP header to on in the request, q_auto is translated to q_auto:eco at the CDN level. If this parameter is hidden in a named transformation then it is not visible to the CDN, so the default level is applied, q_auto:good.

To accommodate this situation, you may prefer to use q_auto together with a named transformation by chaining the components, for example, t_square/q_auto.

Learn more: Save-Data support

Automatic width

The automatic width transformation parameter (w_auto) is not effective if used in named transformations.

For responsive image solutions, w_auto must appear directly in the delivery URL. If it's hidden within a named transformation, it won't be visible to the client or CDN (depending on the solution) and therefore won't take effect.

See Responsive images using the cloudinary-core JS library and Responsive images using client hints.

Automatic device pixel ratio

The automatic device pixel ratio transformation parameter (dpr_auto) is not effective if used in named transformations.

For responsive image solutions, dpr_auto must appear directly in the delivery URL. If it's hidden within a named transformation, it won't be visible to the client or CDN (depending on the solution) and therefore won't take effect.

See Responsive images using the cloudinary-core JS library and Responsive images using client hints.

Named transformation video tutorial

Watch this video tutorial to learn how to create re-usable named transformations with the Cloudinary Transformation Builder UI.

Tutorial contents

Embedding images in web pages using SDKs

You access uploaded images or their derived transformations with URLs. These URLs can be used as the <src> of the <img> tags in your HTML code or other frontend functions to deliver your media assets.

But the easiest way to deliver them is using Cloudinary's framework SDKs to automatically generate transformation URLs and embed them using HTML image tags. The SDKs offer two main helper methods: the URL helper and the image tag helper.

Cloudinary URL helper method

The Cloudinary URL helper method (e.g., cloudinary_url in the Ruby/Rails SDK) automatically generates the image source URL itself. For example, using the URL helper method to return the URL of the leather_bag_gray image, padded to a scaled width and height of 300 pixels with a blue background for the padding:

cloudinary.url("sample.jpg", {background: "blue", height: 300, width: 300, crop: "pad"})

This SDK code outputs the URL:

https://res.cloudinary.com/demo/image/upload/b_blue,c_pad,h_300,w_300/sample.jpg

Cloudinary image tag helper method

By default, the Cloudinary image tag helper method (e.g., cl_image_tag in Ruby on Rails) automatically generates an HTML image tag including the image source URL.

The following shows the same transformations as above, but this time using the image tag to generate a complete HTML image tag.

cloudinary.image("sample.jpg", {height: 100, width: 300, crop: "scale"})

This SDK code will output the following HTML code:

<img 
  src="https://res.cloudinary.com/demo/image/upload/c_scale,h_100,w_300/sample.jpg"
>

The Cloudinary Image Tag helper method allows you to not only specify any Cloudinary transformations parameters, but also to specify regular HTML image tag attributes (e.g., alt, title, width, height). For example, using the Image Tag helper method to create an HTML image tag for the sample image, with the 'alt' attribute set to "A sample photo" and the 'className' attribute set to "Samples":

cloudinary.image("sample.jpg", {alt: "A sample photo", className: "Samples"})

For more information on these SDK helper methods, see the transformation documentation in the relevant SDK guide.

cloudinary.image("sample.jpg", { transformation: { raw_transformation: "w_400,c_pad" }})

Image format support

Images can be uploaded to Cloudinary in various formats (input formats), and you can easily convert these images to other formats for displaying in your web site or application (output formats). Examples of situations where you might want to change the delivered image format:

• Delivering JPEG images for photos that you want to load quickly (or AVIF or WebP if your users are on a browser that supports these).
• Delivering a PNG (24 bit) for high quality illustrations with a transparent background.
• Delivering an image where the original format is not supported for delivery by the browser. For example, you could deliver a Photoshop (.psd) image as a JPEG.

Delivering in a different format

You can convert and deliver images in any supported image format by specifying the required format as the file extension of the delivery URL. When using an SDK to build the URL, you can either append the extension of the new format to the asset's public ID or use the format parameter.

For example, to display the uploaded woman-business-suit JPEG image as a PNG:

https://res.cloudinary.com/demo/image/upload/woman-business-suit.png

https://res.cloudinary.com/demo/image/upload/e_background_removal/e_grayscale/woman-business-suit.png

Another option for changing the format is to explicitly call the fetch_format transformation parameter (f in URLs). This can be useful in situations where you cannot change the file extension, for example, when fetching remote assets that already have a different file extension (format) as part of their URLs.

For example, to fetch a remote image from Wikimedia in PNG format, and deliver the image in JPEG format (also scaled down to a width of 400 pixels):

https://res.cloudinary.com/demo/image/fetch/c_scale,h_400/f_jpg/https://upload.wikimedia.org/wikipedia/commons/1/13/Benedict_Cumberbatch_2011.png

f_auto

You can take advantage of Cloudinary's automatic format selection (f_auto) transformation to automatically deliver images in the most optimized format that's supported by the requesting browser.

For example, if you deliver a JPEG image with f_auto, Cloudinary might generate and deliver the image as a WebP, AVIF or JPEG XL file, depending on the requesting browser and your account setup. The f_auto algorithm will similarly deliver the best format when the original asset is a PNG (with or without transparency), an animated GIF, etc.

For details, see Automatic format selection (f_auto) and Tips and considerations for using f_auto.

Supported image formats

The table below summarizes the supported image formats.

Image transformation types

This page walked you through the basics of how image transformations work. The rest of the pages in this guide provide details, use cases and examples of the many different types of transformations you can apply to the images you deliver:

Delivering optimized and responsive media

In addition to changing the appearance of your media assets by transforming them, you can also use Cloudinary URLs and a variety of parameters to control how they're delivered:

Create new images

Cloudinary provides a variety of methods to create new assets in your product environment.