Can we remove all system based renditions from view? | Community
Skip to main content
dmescia2
dmescia2
Level 4
April 9, 2026
New

Can we remove all system based renditions from view?

  • April 9, 2026
  • 3 replies
  • 25 views

When we add new assets into the DAM the system creates renditions of those assets for use by AEM. We also create custom renditions for use by our users. When users view and asset or click to download it they see all of our custom renditions PLUS the system renditions. Given that the system related renditions are soley for the use of the AEM platform, can we please hide those from our view so they are not noise for our end users?

    3 replies

    Jineet_Vora
    Community Advisor and Adobe Champion
    Jineet_VoraCommunity Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    April 9, 2026

    ​@dmescia2 - It is not recommended to delete the OOTB AEM DAM renditions as renditions like ‘thumbnail’ and ‘web’ are used to view the assets in AEM DAM when you’re navigating or viewing.

    Check best-practises here: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/assets/using/assets-workflow#best-practices-limitations-tips

    dmescia2
    dmescia2Author
    Level 4
    April 10, 2026

    I do not want to delete the renditions. Just hide them. The system needs them. No other user needs to see them so I’d like to hide the system renditions from users. If the admin has to see them I can live with that but it’s so much noise for the end users to see renditions that have zero relevance to them. 

    VishalKa5
    VishalKa5
    Level 6
    April 10, 2026

    Hi ​@dmescia2,

    Yes, this can be done without deleting any system renditions. The system-generated renditions are still required by AEM for previews, thumbnails, and internal processing, so they should remain in the backend. If they are creating confusion for end users, the best approach is to hide them only from the user interface while keeping them available for the platform. This way, users will only see the custom renditions that are relevant to them, while admins can still access all renditions if needed.

    1. System renditions stay in AEM and continue supporting platform functions.
    2. End users do not need to see them if they are not relevant.
    3. AEM has no built-in option to hide only system renditions.
    4. A custom UI customization is needed to filter them from the renditions list.
    5. Only custom/user-facing renditions can be shown to normal users.
    6. Admin access can still include all renditions if required.
    7. In short: hide them in the UI, not from the system.

    Thanks & Regards,

    Vishal

    S
    Adobe Employee
    SubbaraoGa1Adobe Employee
    Adobe Employee
    April 10, 2026

    Hi ​@dmescia2 

    System renditions are almost always named with these patterns (node names under …/jcr:content/renditions):

    • cq5dam.thumbnail.*
    • cq5dam.web.*
    • cq5dam.zoom.*
    • cqdam.machine.metadata.*
    • Any others you know you don’t want exposed

    Your custom renditions generally:

    • Have explicit names you’ve defined (e.g. hi-res.pdf, web-1200, watermark-image.jpeg, etc.)
    • Are created via workflows or Processing Profiles [Custom Asset Renditions design][Custom renditions wiki]

    So the logic is:

    visibleRenditions = allRenditions
      .filter(r -> r.name != "original")          // optional: keep Original always visible
      .filter(r -> !r.name.startsWith("cq5dam.")) // hide system
      .filter(r -> !r.name.startsWith("cqdam."))  // hide machine metadata
      // plus any additional internal patterns you want hidden

    And then optionally:

    if userIsAdmin:
      show all renditions (no filter)
    else:
      show only visibleRenditions
    Terms & ConditionsAccessibility statement

    Loading footer...