Can I Save Dynamic Media Image Templates in code repository? | Community
Skip to main content
L
Luis_Moreno_Deustua
Level 1
February 25, 2026
Solved

Can I Save Dynamic Media Image Templates in code repository?

  • February 25, 2026
  • 4 replies
  • 46 views

I’m exploring to start using Image Templates to generate composed Images with embedded text.
Now that we are defining Template details, I would like to save the templates in our code repository so it can be versioned, replicated through different environments and protected from unwanted access or modifications. 

I looked through documentation but didn’t found explicitly where can these templates be stored and at the same time, be available to be used. 
 

Do you know if this templates can be saved in ui.apps, ui.config or ui.content modules and if there is any specific path allowed?
I asked chatgpt and mentioned that it cna be under ui.apps directly below ui.apps as:
 

/apps/your-project-name/dynamic-media-templates/
 

But I would like to know if anyone has already done this before. 

Thank you in advance for your help :) 

Luis Moreno

Best answer by giuseppebaglio

hi ​@Luis_Moreno_Deustua,

AFAIK DM (Scene7) Image Templates do not live in the AEM JCR. They are uploaded and managed directly in the Scene7 and reside in the Dynamic Media Classic cloud infrastructure. Unfortunately, they can’t be versioned within your code repository.

4 replies

giuseppebaglio
giuseppebaglioAccepted solution
Level 10
February 25, 2026

hi ​@Luis_Moreno_Deustua,

AFAIK DM (Scene7) Image Templates do not live in the AEM JCR. They are uploaded and managed directly in the Scene7 and reside in the Dynamic Media Classic cloud infrastructure. Unfortunately, they can’t be versioned within your code repository.

    A
    aemskunkworks
    Level 2
    February 26, 2026

    Hi ​@Luis_Moreno_Deustua  - it depends on what type of Dynamic Media you have. Dynamic Media with OpenAPI assigns a delivery URL to every approved asset, and those URLs follow a structured pattern. So you can store the delivery URL references in your codebase without carrying binaries in Git, and this is better, because any changes to approved assets are automatically reflected in the delivery URLs, which keeps code references current without redeployment.

    With DM with OpenAPI, delivery URL references in your code could allow you to apply transformations via query parameters at runtime, which is similar to what the image templates do but through URL composition rather than a stored object.

    And then, the AEM Assets plugin for EDS allows you to configure projects to retain external image URLs insetad of rewriting them to internal paths. 


    See links below: 
    https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/dynamicmedia/dynamic-media-open-apis/dynamic-media-open-apis-overview   
    https://github.com/adobe-rnd/aem-assets-plugin

      L
      lisab94981616
      Level 2
      February 26, 2026

      Hi ​@Luis_Moreno_Deustua  - I sent you a direct message on this, let me know if you have questions!

        L
        Luis_Moreno_DeustuaAuthor
        Level 1
        March 20, 2026

        Thank you Everyone for your help. 

        It seems there are two ways to create Dynamic Media Templates, the same for Presets and image profiles. They can be created in Dynamic Media Classic, they are created in Cloud and managed there. However these can also be created first in the AEM JCR repo and then publish to DM. What remains to be validated is the publish. If having them deployed to AEM by code also publish or update the version(in case the preset already existed) in DM Classic. 

        Will test and let you know. 

        Thanks again! ​@giuseppebaglio ​@aemskunkworks ​@lisab94981616 

        Luis Moreno

          L
          lisab94981616
          Level 2
          March 20, 2026

          ​@kautuk_sahni  - ​@Luis_Moreno_Deustua  should get the badge for answering his own question, ha!

          Terms & ConditionsAccessibility statement

          Loading footer...