How AEM DAM Asset renditions are getting used in AEM | Community
Skip to main content
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
krati_garg
krati_gargAccepted solution
Employee
October 12, 2022

For example, Can I use rendition instead of original image？


In above thread, it is mentioned that you don't see the renditions. There are some OOTB renditions that are generated when an image is uploaded. 
Please see below link for OOTB renditions and check if these are available on your AEM set up. If not please share a screen shot.
https://experienceleague.adobe.com/docs/experience-manager-learn/assets/authoring/renditions.html?lang=en

View reply

7 replies

digarg17
Employee
October 11, 2022

In different views - like card vieow , list view , column view  etc , you would see the thumbnail , and also in side rail when dragging/dropping assets on pages and many more places you will see use of OOTB renditions. 

 

You can generate custom renditions  / check these renditions in DAM update workflow.

Translate
    Johann_LuAuthor
    Level 4
    October 11, 2022

    Sorry, maybe there is something wrong with my statement, what I want to ask is how do I use it in the component. Now I can only see the original assets stored in the dam in the component and can't use the renditions,I want to use the renditions.

    Translate
      digarg17
      Employee
      October 11, 2022

      This cannot be done through drag/drop directly on the component but in your component logic you can refer to the path of the image rendition e.g. You could add a dropdown with all possible rendition options and based on what is selected in dialog image url is rendered as 

      <img src="<dampathofimage>/jcr:content/original">

      or<img src="<dampathofimage>jcr:content/<rendition1>" Example :-

      /content/dam/June_2022.pdf/jcr:content/original

      /content/dam/June_2022.pdf/jcr:content/renditions/cq5dam.web.1280.1280.jpeg

      Translate
        Terms & ConditionsAccessibility statement

        Loading footer...