> ## Documentation Index
> Fetch the complete documentation index at: https://cloudinary.com/documentation/llms.txt
> Use this file to discover all available pages before exploring further.

# Asset management


As an Assets administrator, you can perform several tasks related to asset management. 

Some of these tasks involve configuring options that enable functionality for your users, and others involve managing assets directly:

* [Creating named transformations](#named_transformations): Create sets of pre-defined transformations that can be used for: 
  * [Transformation templates](#transformation_templates) (previously known as presets), which enable others to easily apply named transformations to assets.
  * [Strict transformations](#strict_transformations), which free selected named transformations from certain security restrictions.
* [Configuring access control](dam_manage_asset_protection#access_control_modes): Determine who can access an asset and when.
* [Moderating assets](#automatic_and_manual_moderation): Moderate assets when they're uploaded to keep unwanted content out of your system.
* [Register for add-ons](#add_ons): Enable add-ons to extend your Assets functionality.
* [Requesting external uploads (Beta)](#requesting_external_uploads_beta) (free plan only): Share a public link to grant external upload access to a selected folder.

> **TIP**: To learn how to manage digital rights, including the actions you can take to protect and control asset usage, see [Digital rights management](dam_admin_digital_rights_management).

## Named transformations

A **named transformation** is a pre-defined set of transformations saved with a name for easy reference and reuse. Named transformations enable you to apply several, possibly complex transformations with one concise name. When used in delivery URLs, named transformations shorten the URLs and the descriptive names can improve SEO. 

Additionally, you can set named transformations as **transformation templates** (previously known as presets) and strict transformations, which enable additional functionality:

* Especially useful for Assets administrators, setting a named transformation as a [transformation template](#transformation_templates) enables your users to apply that named transformation to assets as [templates](dam_editing_and_transformations#transformation_templates) for preview and/or download at the click of a button. (Video previews are available to **Assets Enterprise** customers [by request](https://cloudinary.com/contact).)

* You can also allow a named transformation for a [strict transformation](#strict_transformations). The **Strict transformations** setting prevents end users from dynamically applying transformations to media assets by changing their URLs. If this setting is on, you can allow dynamically applying specific named transformations as exceptions. 

You can coordinate with developers on your team to create and manage named transformations [programmatically](named_transformations_tutorial), or you can create and manage named transformations in the Console using the  [Transformation Builder (Beta)](#transformation_builder).

[//]: # (Nearly identical info (but worded for developers) in partial_named_trans_note and admin_api - if updating here, update there too)
> **INFO**:
>
> * Keep in mind that not all transformations support all asset types and formats. Applying a named transformation to an asset of an unsupported type or format {valeExclude}will{/valeExclude} fail and you won't be able to deliver those assets. You can check whether you can use the all parameters in your named transformation for both images and videos in the [transformation reference](transformation_reference).  You can also check the [supported formats for transformations](formats_supported_for_transformation).

> * Before you **update** the transformation parameters of an existing named transformation that's already used in your production assets, make sure you're aware of all existing instances. To mitigate risk, when you update the parameters of an existing named transformation (whether via the Console UI or API), existing derived assets (already generated copies of an asset with the transformation applied) using the named transformation {valeExclude}are **not**{/valeExclude} automatically invalidated and regenerated.  If you're sure you want to apply the new definition to any **already derived** assets with that named transformation, a developer must specifically [invalidate](invalidate_cached_media_assets_on_the_cdn) those transformations so that the asset {valeExclude}will be{/valeExclude} re-derived using the new definition the next time anyone tries to view it in a browser.

> * Before you **delete** an existing named transformation, make sure that transformation isn't currently used in production. When you **delete** an existing named transformation (via the Console UI or API), and if there are fewer than 1000 existing derived assets using that named transformation, they're automatically invalidated and {valeExclude}will{/valeExclude} return errors when next requested in a browser.  If there are 1000 or more such derived assets, you'll get an error and you won't be able to delete the named transformation until a developer invalidates the existing derived assets.

### Creating named transformations

You can create a named transformation from the **Image** product in the Console in one of a few ways:

* Start with a pre-defined transformation from the [Image Home](https://console.cloudinary.com/app/image/home) examples as a template and experiment with it in the UI. Click **Use it** to open the Transformation Builder and refine it to your needs, and finally use **Save As** to save it as a new named transformation with your chosen name.
   
* View all your delivered dynamic transformations (those that were generated and delivered on the fly) in the [Log](https://console.cloudinary.com/app/image/manage/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)](#transformation_builder) and save with your chosen name. Open the builder by clicking **New Transformation** from either of the Transform and Customize pages.

> **NOTE**:
>
> Names used for named transformations:

> * Must contain valid UTF8 characters only

> * Must not contain more than 1024 characters

> * Must not contain any of these characters: `\`, `/`, `?`, `&`, `#`, `%`, `.`, `,`, ``

Once you've saved your named transformations, you can view a list of them on the [Named Transformations](https://console.cloudinary.com/app/image/manage/named) tab of the **Manage Transformations** page in the **Image** product of the Console (**Image > Manage Transformations > Named Transformations**).

From here, you can edit or copy the named transformation.  

You can also select to include a named transformation as a [transformation template](#transformation_templates), so they can be used as [templates](dam_editing_and_transformations#transformation_templates) in the Media Library, or to allow a named transformation for [strict transformations](#strict_transformations).

### Transformation Builder
The Cloudinary Transformation Builder UI is designed to help you create and save your transformations in a simple and easy to use way. Open the builder by clicking **New Transformation** from either of the Transform and Customize pages accessible from the Product Navigation menu.

Here are some of the features and functionality you can get by using the builder:

* 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.
* Ability to update the default preview asset to something from your own Media Library.
* Developers can copy URL and SDK snippets directly into their code. 

> **INFO**:
>
> The **Transformation Builder** is currently in Beta. Some implementation details may change before the official release. The builder for creating named transformations is enabled for all new customers. Follow the instructions below to check if it's available to you. If you don't have it enabled and would like access to the Beta, send us a [support request](https://support.cloudinary.com/hc/en-us/requests/new) and we will enable it for you.

> **NOTE**:
>
> The builder has support for most common transformation actions. If the transformation action you are trying to apply isn't listed, you can add an **Additional Transformation** action and use [transformation URL syntax](#transformation_url_syntax) to specify your transformation. Alternatively, you can switch to the legacy editor to create your transformation.

### Transformation templates

> **READING**:
>
> :no-title
> The **transformation templates** feature is a premium offering for **Assets Enterprise** plans, and its availability depends on your account setup. If **transformation templates** is not yet enabled for your account and you'd like to enable it, please contact your Customer Success Manager.

A **transformation template** (previously known as a transformation preset) can be applied to an asset to generate a copy modified according to a set of pre-defined transformations (i.e., a [named transformation](#named_transformations)). 

Transformation templates can be applied in the following contexts:

* Assets users can preview assets with a transformation template applied, download those assets, and download their transformed delivery URLs using [Studio](dam_editing_and_transformations#studio). In addition, administrators can use this tool to [create and edit](#studio) transformation templates.
* Assets users can preview an asset with transformation templates applied from the [Download Options tab](dam_manage_individual_assets#drill_down_tabs) of the asset management drill-down page to see how the selected asset would look with those transformations applied. Users can perform operations such as opening the displayed asset in a new tab, downloading it, copying the URL, or, if you have Assets, further editing the transformation.
* Assets users can download [one asset](dam_editing_and_transformations#downloading_a_single_transformed_asset) or [multiple assets](dam_editing_and_transformations#downloading_transformed_assets_in_bulk) with a transformation template applied in the Media Library.
* Depending on your account or product environment setup, external stakeholders may be able to download assets with transformation templates (presets) applied from [dedicated collection web pages](dam_folders_collections_sharing#sharing_collections_externally_via_public_links) and [basic portals](dam_folders_collections_sharing#basic_portals_beta) accessed via public links. This functionality enables modified assets to be shared with external stakeholders instead of originals.

> **READING**:
>
> :no-title
> In the **Assets Free** plan, transformation templates are only accessible in the Media Library from within Studio. The full feature is included in the Media Library for **Assets Enterprise** customers only. 

>    * To learn more about the features available in the **Assets Free** plan and how they can support development workflows, see [Media Library for Developers](media_library_for_developers). 

>    * For upgrade options or more information, [contact us](https://cloudinary.com/contact).

Several transformation templates are provided by default, and you can replace these with your own by setting [named transformations](#named_transformations) as transformation templates, or saving transformations created in [Studio](dam_editing_and_transformations#studio) as templates, up to a maximum of 60.

> **NOTES**:
>
> * Any user can create transformation templates directly from within the Media Library, albeit with fewer transformation choices, by utilizing [Studio](dam_editing_and_transformations#studio).

> * Keep in mind that transformation templates may be applied to assets by other users and not all asset formats are supported for transformations. If an asset's original format doesn't support transformations, applying transformation templates to it will result in an error. See a list of [supported transformations](formats_supported_for_transformation).

**To set an existing named transformation as a transformation template**:

1. In the [Named Transformations](https://console.cloudinary.com/app/image/manage/named) tab of the **Manage Transformations** page in the Cloudinary Console, hover over the named transformation you want to use as a transformation template and open the menu using the kebab (3-dots) icon.
   ![Named Transformation UI](https://cloudinary-res.cloudinary.com/image/upload/q_auto/f_auto/bo_1px_solid_grey/v1711871425/docs/DAM/named_transformations_templates.png "thumb: w_700,dpr_2, width:700, with_code:false, with_url:false, popup:true")
2. From the menu, turn on the Media Library Templates **Use for images** or **Use for videos** options. To ensure that your transformation templates are valid:
   * Make sure that named transformations that you set as a video templates only contain transformations that are valid for videos, and that those that you set as image templates only contain transformations that are valid for images.
   * Make sure the transformation doesn't include any [user-defined variables](user_defined_variables).

> **NOTE**:
>
> When you set one or more named transformations as transformation templates, the default transformations are no longer displayed. To revert to the default transformations, open the Named Transformations page and turn off the Media Library Templates **Use for images** or **Use for videos** options for each relevant named transformation.

> **TIP**:
>
> :title=Tips

> * Transformation templates can be a convenient way to see how an asset may look with different levels of compression applied. To create a template for this purpose, create a new named transformation, set the **Quality** option to the [desired compression level](image_optimization#automatic_quality_selection_q_auto), and give the named transformation an appropriate name, such as "Good quality mode" or similar. Then select the Media Library Templates **Use for images** or **Use for videos** options as described above. You can select **Auto** for your quality setting and Cloudinary will automatically apply the compression that achieves the optimal balance between file size and visual quality to your asset.

> * When you click a transformation template in the Management drill-down page to preview an asset with that template, it doesn't count against your transformation quota. However, the first time someone views that transformation template for a specific asset outside the Media Library (open in a browser tab, download, etc.), a derived asset is generated and [counts](transformation_counts) like any other asset transformation.

> * You can make transformation templates (presets) available from [dedicated collection web pages](dam_folders_collections_sharing#sharing_collections_externally_via_public_links) and [Media Portals](dam_folders_collections_sharing#media_portal_beta) accessed via public links. When available, external stakeholders accessing dedicated collection web pages or portals can download assets transformed by a template, instead of, or in addition to, being able to download originals. Keep in mind that external stakeholders won't be able to preview the transformation templates. Use descriptive names to make it easier to anticipate what the transformation templates will do.

### Studio

[Studio](dam_editing_and_transformations#studio) provides a user-friendly interface for applying transformations and AI-driven actions to multiple images at once, generating variations for download, and copying the transformed images' delivery URLs.

Administrators can create new [transformation templates](#transformation_templates) in Studio. Once created, these templates are available for users to apply within Studio, as well as any other context that named transformations set as transformation templates can be applied. In addition, templates created within Studio are displayed on the [Named Transformations](https://console.cloudinary.com/app/image/manage/named) page of the Console, with the Media Library Templates **Use for images** or **Use for images** options selected.

Templates created within Studio can be used as a base for new templates and are editable.

[Named transformations](#named_transformations) set as transformation templates for images are available in Studio for users to apply. However, they can't be used as a base for new templates and aren't editable.

#### Watch and learn: Manage templates in Studio

#### Read how to: Manage templates in Studio

To create a new transformation template in Studio, open Studio and add one or more images, apply AI-actions and transformations, and click **Save Transformation**.

To use a templates as a base for a new template, click **Templates**, select a base template, add or remove AI-actions and transformations, click **Save Transformation**, and then select **Save as New** to save the edited template under a new name.

To edit templates that were created within Studio, click **Templates**, select a template, add or remove AI-actions and transformations, click **Save Transformation**, and then select **Save Changes** to overwrite the original template. 

To deselect a template, click the reset button next to the **Templates** title.

For more information on using Studio, see [Studio](dam_editing_and_transformations#studio) in the User Guides.

### Strict transformations

When transformations are added to Cloudinary asset delivery URLs the transformed assets are generated dynamically, meaning that if the requested transformed asset doesn't already exist, then it's created on the fly. This is a powerful feature, but you may not want your end users to play with these options on your assets. 

Enabling the [Strict transformations](control_access_to_media#strict_transformations) setting prevents unexpected transformations from being charged to your account by blocking end users, who have access to your delivered assets via your website or app, from dynamically generating transformations on them. 

If this setting is on, you can allow specific named transformations to be used dynamically as an exception.

Enable the **Strict Transformations** setting in the [Security](https://console.cloudinary.com/console/settings/security) page of the Console Settings. To mark a specific transformation as allowed, open the [Named Transformations](https://console.cloudinary.com/app/image/manage/named) page of the Console. Next to each transformation you can open the menu and toggle to either allow or restrict the transformation.

![Named Transformation UI](https://cloudinary-res.cloudinary.com/image/upload/f_auto/q_auto/bo_1px_solid_gray/v1664381469/docs/DAM/named_transformations_video.png "thumb: w_500,dpr_2, width:500, with_code:false, with_url:false, popup:true")

## Automatic and manual moderation

It’s sometimes important to moderate assets uploaded to Cloudinary. For example, you might want to keep out inappropriate or offensive content, reject assets that don't answer your needs (e.g., making sure there are visible faces in profile images), or make sure that photos are of high enough quality. 

Assets can be marked for moderation both [through the UI](#marking_assets_for_moderation) and programmatically during the upload flow. For more information on programmatically marking assets for moderation on upload, see [Moderation of uploaded assets](moderate_assets).

You can apply one or more of these moderations to your incoming assets in a single upload action:

* **Automatic moderation**: You can register for a variety of [add-ons](#add_ons) that provide different automatic moderation functionality: 
    * [Webpurify](webpurify_image_moderation_addon): Human moderation experts reject adult-oriented or inappropriate images.
    * [Perception Point](perception_point_malware_detection_addon): Detects and prevents advanced threats by incorporating multi-scanning and controlled data workflows. 
    * [Amazon Rekognition](aws_rekognition_ai_moderation_addon): Rejects images with adult-oriented or inappropriate content using deep learning algorithms.
    * [Amazon Rekognition (Video)](aws_rekognition_video_moderation_addon) and [Google Video Moderation](google_ai_video_moderation_addon): Reject videos with adult-oriented or inappropriate content using deep learning algorithms.
    * [Duplicate Image Detection](cloudinary_duplicate_image_detection_addon): Prevents duplicate images from being uploaded.
      > **READING**:
>
> :no-title
>       Duplicate Image Detection isn’t included in the Media Library available with the **Assets Free** plan, which offers essential media management capabilities. It's part of the Media Library for **Assets Enterprise** plans.

>           * To learn more about the features available in the **Assets Free** plan and how they can support development workflows, see [Media Library for Developers](media_library_for_developers). 

>           * For upgrade options or more information, [contact us](https://cloudinary.com/contact).
* **Manual moderation**: A Cloudinary moderator must personally review, and accept or reject, assets marked for manual moderation from the [Moderation](#reviewing_assets_manually) page. From there, the moderator can actually review all assets marked for moderation, per moderation type and status, and override a decision made by any one of the automatic moderations.

When an asset is sent for moderation, it's marked as **Pending** as soon as it's uploaded. For automatic moderations, the resolution time can vary based on the asset and moderation type. For instance, large videos may take longer to process, while average-sized images are usually moderated almost instantly with algorithm-based add-ons. If an asset is subject to multiple types of moderation, the overall process duration depends on the time taken by each individual moderation to complete.
> **NOTE**: By default, assets that are marked for moderation are deliverable and available via the Media Library. If you'd like the assets marked for moderation to be blocked (until approved) either from the Media Library, or from being delivered, or from both, [contact support](https://support.cloudinary.com/hc/en-us/requests/new).
### Marking assets for moderation

You can send incoming assets to be moderated automatically or manually.

**To mark assets being uploaded for moderation:**

1. Go to the [Upload Presets](https://console.cloudinary.com/app/settings/upload/presets) page of the Console Settings.
2. Add a new [upload preset](upload_presets) or edit an existing one from its (3-dots) option menu. 
3. Select the **Manage and Analyze** tab to enable manual moderation.![Manual moderation](https://cloudinary-res.cloudinary.com/image/upload/f_auto/q_auto/bo_1px_solid_grey/v1731425442/docs/upload_preset_manual_moderation.png "thumb: w_350,dpr_2, width:350, popup:true")
4. Select the **Addons** tab, and select one or more of the moderations listed:![Automatic moderations](https://cloudinary-res.cloudinary.com/image/upload/f_auto/q_auto/bo_1px_solid_grey/v1731425503/docs/upload_preset_auto_moderation.png "thumb: w_550,dpr_2, width:550, popup:true")
   > **NOTES**:
>
> * Make sure you're already registered for its corresponding moderation [add-on](#add_ons), or assets uploaded using that preset will fail.

>    * When defining an upload preset that may be used for both image and video uploads, you can select both image-specific and video-specific moderations and only the relevant moderations will be applied when a file is uploaded with that preset.

>    * The order in which the moderations are listed dictates the order in which the moderations are applied to uploaded assets. For example, if you select the **Amazon Rekognition** and **Duplicate** moderations, **Amazon Rekognition** will be applied to uploaded assets before **Duplicate**. When selected, Manual moderation is always applied last.
5. There are two ways to apply the moderation to assets being uploaded: Apply the moderation automatically to all the assets uploaded to the Media Library by setting the upload preset with the desired moderation settings as the [Media Library upload preset](dam_admin_upload_presets#media_library_upload_presets).  ORChoose if you want to apply the moderation to assets during each upload. To apply the moderation, upload assets via the [Media Library Upload Widget](dam_upload_store_assets#media_library_upload_widget) and select the **Upload Preset** with the desired moderation settings from the **Advanced** drop-down.   > **NOTE**:
>
> Depending on your product environment setup, the **Upload Presets** option may not be available in the **Advanced** options of the Media Library Upload Widget. If the option isn't there, you can submit a [support request](https://support.cloudinary.com/hc/en-us/requests/new) to activate it.
### Applying multiple moderations

You can mark assets for more than one type of moderation in a single upload action. This might be useful if you want to reject an asset based on more than one criteria, for example, if it's either a duplicate or has inappropriate content. In that case, you might moderate the asset using the **Amazon Rekognition** as well as the **Duplicate** moderation.  

#### Status when applying multiple moderations

Each of the moderations selected is, in turn, applied to the uploaded asset. The status of the asset for all moderations is set to `pending` immediately on upload, and changes to **accepted** or **rejected** for each of the moderations that's applied. 

The selected moderations are applied and resolved one by one, until either:

* **All selected moderations approve the asset**, in which case the final status of the moderation is **approved**.
* **One of the moderations rejects the asset**, in which case the final status of the asset is **rejected**. The process ends and the remaining moderations are never applied. There's no way to resume moderation once an asset has been rejected.
* **The asset is [manually accepted or rejected](#reviewing_assets_manually).** This can be done at any point in the process, regardless of the asset's status and whether the asset was originally marked for manual moderation. A manual decision always overrides the automatic ones.

#### Moderation history

You can view an asset's moderation history to visually track its progress through the moderation process:

* **While moderation is in progress**: you can find out which moderations have been applied, which is currently being applied, and which are pending. 
* **If an asset's final status is resolved**: you can find out which moderation accepted or rejected the asset, and if any moderations weren't applied.
**To view an asset's moderation history:**

Once you've opened the moderation page and [found the asset](#review_assets_instructions) you're looking for either:

* Double click the asset to open the **Management drill-down** and select the **Moderation** icon.  OR 
* Select the asset and open the **Preview Pane**, then click the **Moderation** tab.

See how the moderation changes after each moderation is applied:

One moderation applied

Three moderations applied

### Reviewing assets manually
Users with Master admin, Media Library admin, and Technical admin [roles](dam_admin_users_groups#role_based_permissions) can moderate assets. Additionally, Media Library users with the [Moderate asset](dam_admin_users_groups#ml_user_permissions) administrator permission can moderate assets in [folders](dam_admin_users_groups#folder_permission_levels) that they have **Can Edit** or **Can Manage** permissions to. You can view all moderated assets from the **Moderation** page and filter assets by moderation type and decision status.

* **Manual moderation**: When manual moderation is enabled, assets are marked as **Pending** after upload and are displayed on the **Moderation** page, where a moderator reviews them and decides whether to **accept** or **reject** based on the content.

* **Automatic moderation**: You can also view assets marked for automatic moderations on the **Moderation** page, along with their decision status. 
  * You can manually override automatic decisions, such as approving a rejected image or rejecting an approved one. 
  * If you manually approve or reject an asset, it will be considered manually moderated, even if it was initially flagged by automatic moderation. The asset will then appear under the **Manual** filter.
* **Multiple moderation**: As each moderation type is applied and resolved, the asset’s moderation status changes. 
  * You can manually override moderation decisions for assets marked for multiple moderations, as well. 
  * You can also view the asset’s [moderation history](#moderation_history) to track this progressFor more information see [Applying multiple moderations](#applying_multiple_moderations).

**To review assets:**

1. From the [Product Navigation menu](dam_digital_asset_management#assets_navigation_options), select **Moderation**. 
   ![Moderation page](https://cloudinary-res.cloudinary.com/image/upload/f_auto/q_auto/bo_1px_solid_black/v1667726089/docs/DAM/moderation_page.png "width:700, popup:true")
2. Browse the assets. Use the filters to select the moderation type and status of the assets you want to review. 
   ![Moderation kind filter](https://cloudinary-res.cloudinary.com/image/upload/f_auto/q_auto/v1667466998/docs/DAM/moderation_kind_filter "thumb: w_100,dpr_2, width:100, popup:true")
   To find assets marked for multiple moderations:
      * While the asset is being processed, filter **pending** assets under the moderation type currently applied.
      * If the asset's final status is **rejected**, the asset will be found under the moderation type that rejected it.
      * If the asset's final status is **accepted**, the asset will be found under the last moderation type that was applied.
      * If the final status was determined manually, the asset will be found under Manual moderation, regardless of whether the asset was originally marked for manual moderation.
3. Accept or reject them. If you reject the asset and your administrator enabled requiring a rejection reason from the [Asset Visibility](dam_admin_media_library_options#require_a_rejection_reason) page of the Media Library preferences, you'll be required to select a reason for rejection from a drop-down list.![Rejection reason](https://cloudinary-res.cloudinary.com/image/upload/f_auto/q_auto/bo_1px_solid_grey/v1750709278/docs/DAM/rejection_reason.png "thumb:c_scale,w_400/dpr_2, with_code:false, with_url:false, width:400, popup: true") 

> **NOTE**:
>
> Depending on your account or product environment setup, you may also be able to moderate assets that are pending manual moderation directly in the Media Library, and not just from the Moderation page, by selecting **Approve** or **Reject** from the (3-dots) options menu on the asset itself, or, after selecting one or more assets, on the asset toolbar.
## Add-ons

You can register for a variety of add-ons that offer unique image and/or video processing or delivery capabilities, including celebrity recognition, automatic tagging, background removal, and [asset moderation](#automatic_and_manual_moderation). Some of these add-ons are based on advanced Cloudinary AI functionality and others provide special functionality from a variety of vision and media processing partners. The add-ons are simple to use and fully integrated into Cloudinary's image and video management pipeline.

### Registering for add-ons
To register for an add-on, first make sure you are logged into Cloudinary. Then, go to the [Add-ons](https://console.cloudinary.com/app/settings/addons) page by clicking the icon in the left sidebar. From the **All Add-ons** tab, choose an add-on, scroll down to select a monthly plan (**Free** is selected by default), and click **Install Add-on**. 

> **NOTE**:
>
> Depending on your account setup, you may need to access add-ons from **Settings -> Add-ons** instead. Scroll to the **Available add-ons** section, click the add-on you want to register for, and select a plan.

When registering for an add-on, consider the following:

* Most add-ons provide a **Free** plan with a small monthly quota. In most cases, you can register for these, even when on a Free Cloudinary plan.
* Paid add-on plans with a larger monthly quota require a Cloudinary account on a [paid plan](https://cloudinary.com/pricing).
* You can view your add-on subscriptions and usage in the **Installed Add-ons** tab in the **Add-on Marketplace**.
  > **NOTE**:
>
> If your **Add-ons** page is in the Console Settings, scroll to the top of the page to see the add-ons that you've already installed.
* Some third-party add-on plans require that you review and accept their terms of service.

### Applying add-ons using upload presets

You can enable users to apply add-ons to assets on upload by configuring an [upload preset](dam_admin_upload_presets), as a set of predefined options that streamline the upload process by automatically applying specified actions or configurations to uploaded assets. You can either create a new **signed** upload preset or edit an existing one to include the activation of one or more add-ons.

Users can apply upload presets selectively during upload, such as removing background for specific use cases. However, if you want the preset to be applied to all future image or video uploads by default, such as enforcing auto-tagging or moderation, add the add-on option into your existing [Media Library upload preset default](dam_admin_upload_presets#upload_preset_defaults) for images, videos or both, as appropriate. Alternatively, set the relevant newly created upload preset as the default. 

**To activate an add-on:** 

1. Go to the [Upload Presets](https://console.cloudinary.com/app/settings/upload/presets) page of the Console Settings, then add a new preset or edit an existing one. 
2. Select the **Addons** tab and choose your desired add-ons. In some cases, you may have a few sub-options you can optionally select for an individual add-on.  

> **NOTES**:
>
> * Make sure you're already registered for any add-on you enable. 

> * For a complete list of all available add-ons, see [Add-ons](cloudinary_add_ons).

#### Special configuration for AI captioning

AI captioning is one of several features available with the Cloudinary AI Content Analysis Add-on. 

Similar to other add-ons, you activate it in your upload preset by turning on the **AI captioning** sub-option under **Cloudinary AI Content Analysis** in the Upload Presets **Addons** tab. 

However, if you'd like to store the generated captions in an asset metadata field so that you can view or edit it from the Media Library, you need to also add a special custom configuration in the **On success script** section of the **Advanced** tab of your upload preset.

For example:

* To add the generated caption to the relevant assets' **Title (caption)** contextual metadata field and add the value `autocaption` to the assets' tags, add the following **On success script** code: 
  
      ```
      current_asset.update({tags: ['autocaption'], context: {caption: e.upload_info?.info?.detection?.captioning?.data?.caption}})
      ```
* To add the caption to a previously created structured metadata field called **Caption** (whose `external_id` is `auto_caption`) and add the value `autocaption` to the assets' tags, add the following **On success script** code:
  
      ```
      current_asset.update({tags: ['autocaption'], metadata: {auto_caption: e.upload_info?.info?.detection?.captioning?.data?.caption}})
      ```

### Using add-ons

You can apply add-on functionality to assets during uploads using [upload presets](dam_admin_upload_presets#addons). For example, you can set automatic tagging or background removal for all assets uploaded using a specific upload preset. 

In addition, users can apply some add-ons to assets that are already in the Media Library from the [Analysis tab](dam_analysis_insights#analyze_assets) of the Manage page. Others can be applied using [Studio](dam_editing_and_transformations#studio).

For more information on applying the add-ons, see [Add-ons](dam_add_ons) in the User Guides.

For example, below is an example of applying auto-tagging from the Analysis tab of the Manage page:

![Running an add-on in the Analysis tab of the Manage Page](https://cloudinary-res.cloudinary.com/image/upload/f_auto/q_auto/bo_1px_solid_grey/v1710095415/docs/DAM/add_on_manage_page.png "thumb: w_600,dpr_2, width:600, popup:true")