Custom renditions in AEM Assets | Community
Skip to main content
dmescia2
dmescia2
Level 3
March 13, 2026
Question

Custom renditions in AEM Assets

  • March 13, 2026
  • 2 replies
  • 47 views

I am wondering if there is a way to save renditions in AEM that are in essence individual assets? Here is an example:

  • We have over 20 different lines of business and 4 separate brands. This leaves us with a lot of logos. And each logo has multiple variations: 4 color, 2 color, black and white, etc. Then there are separate file formats and resolutions for those as well.
  • I do not trust any system to render logos out using presets so we have each of these created to meet our specific branding needs when it comes to the colors and their breakdowns.
  • This leads to an oppressive amount of individual assets in the DAM that a user has to sift through and makes it difficult for non-creatives to know which file is the one they should use for their need.

I’m hoping there is a way to set up one asset in the DAM, we’ll call it Brand 1 Logo, and then upload the rest of the variants as renditions of that one asset that we can give titles to that are related to the use (For example, Large format print, Website header, Instagram graphic). Then when a user goes to download or link to the asset they are presented with a popup showing them the options they have to choose from for their download.

 

This approach will greatly simplify the user experience and allow us a more streamlined manner to manage these assets as well.

2 replies

VishalKa5
VishalKa5
Level 6
March 14, 2026

Hi ​@dmescia2 ,

 

In Adobe Experience Manager (AEM) Assets, renditions are mainly meant for system use, but there are a few ways to manage logo variants.

Key Points:

  1. Renditions Purpose – Renditions are stored under the asset and usually used for system-generated versions, not as separate user-selectable assets.

  2. Manual Renditions – You can upload custom renditions (e.g., web, print, social), but the UI does not easily allow custom labels for users.

  3. Better Approach – Store logo variants as separate assets and organize them using folders, metadata, or collections.

  4. Custom Solution – If needed, a custom UI or extension can show different logo versions as download options.

Conclusion: Renditions can store variants, but for better usability it is usually easier to manage logo versions as separate assets grouped with metadata or collections.

Thanks,
Vishal

dmescia2
dmescia2Author
Level 3
March 14, 2026

Do you have any documentation on how your second option works? The manual renditions. I’d love to see what that option looks like. The custom captions are a nice to have for us so I can live without those if I have to. 

AmitVishwakarma
Community Advisor
AmitVishwakarmaCommunity Advisor
Community Advisor
March 14, 2026

Hi ​@dmescia2 

You can do this in AEM, but via static renditions of a single asset, not "separate assets disguised as renditions".

1. Model: one logo asset, many curated renditions

  • Upload a single master asset, e.g. brand1-logo-master.ai or brand1-logo-master.svg.
  • Open it in Assets -> click the asset -> Details.
  • In the right rail, open Renditions and use Add Rendition for each pre‑built variant:
    • brand1-logo_print-large-cmyk.pdf
    • brand1-logo_web-header-rgb.png
    • brand1-logo_ig-post-rgb.png
  • Use semantic filenames that encode the usage (print/web/IG/etc.). Those names are what users will see and what go into the downloaded files.
  • AEM treats these as first‑class static renditions attached to one asset, not as separate assets. https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/assets-view/renditions

This gives you exactly what you want technically: one asset node, many curated, pixel‑perfect binaries, no auto‑reprocessing.

2. How users pick "the right one" to download

You have two out‑of‑the‑box options:

A. Directly in AEM Assets (author UI)

For power users / internal teams:

  1. Open the logo asset -> Details.
  2. In Renditions, click the specific rendition you want -> Download.

This is simple and reliable, but the "selection" happens in the Renditions panel, not a fancy popup.

B. Content Hub / Brand Portal – popup with selectable renditions (best for non‑creatives)

If you front this with AEM Assets Content Hub or Brand Portal:

  1. Admin enables renditions in the configuration:
  2. End‑user selects the logo asset and clicks Download.
  3. A popup dialog lists available renditions; they tick:
    • "print-large-cmyk"
    • "web-header-rgb"
    • "ig-post-rgb" …and download only what they need.

That is the closest out‑of‑the‑box implementation of the "user sees a popup of variants and chooses the right one".

3. Notes / constraints (to avoid surprises)

  • Renditions are not separate assets: metadata, lifecycle, and permissions are shared with the main asset.
  • You control fidelity: because you upload the final logo files as renditions, AEM does not re‑render or change them.
  • For friendlier labels than filenames, you can:
    • Adopt a strict naming convention (logo – Instagram story – RGB 1080x1920.png), or
    • Do a light UI customization to show dc:title for each rendition (small dev effort).
Amit Vishwakarma - Adobe Commerce Champion 2025 | 16x Adobe certified | 4x Adobe SME
Terms & ConditionsAccessibility statement

Loading footer...