Dynamic Media Dynamic Renditions are incorrect for assets with the same name

[zen_____]

After bulk uploading a large amount of assets to AEM Assets, I noticed that the Dynamic Renditions for some assets with the same name were getting "mixed up" - they have the wrong image content in the renditions.

For example:

I upload two assets: /content/dam/page1/HeroImage.png and /content/dam/page2/HeroImage.png.

Dynamic Media requires unique filenames, so these were created in DM as HeroImage.png and HeroImage-1.png respectively.

When I look at the Dynamic Renditions in AEM Assets for /content/dam/page1/HeroImage.png, it's showing the HeroImage-1.png renditions.

What is the correct workaround for this? It's not realistic to expect every asset in the DAM to have a unique name.

[Avinash_Gupta_]

Hi @zen_____ 

Adobe Dynamic Media does not allow two files to have the same name. Each item’s Adobe Dynamic Media ID must be unique. Because of this rule, Upload to Application has an overwrite. The exact effect of this option depends on the specified Overwrite Images option you have chosen. These options specify how replacement images are uploaded: whether they replace the original images, or become duplicate images. Duplicate images are renamed with a -1. For example, test.jpg is renamed test-1.jpg. 

You would need to check the Dynamic Media General Settings configuration. These are the options available:-

1. Overwrite in current folder, same base name/extension

2. Overwrite in current folder, same base name regardless of extension

3. Overwrite in any folder, same base asset name/extension

4. Overwrite in any folder, same base asset name regardless of extension

More details are available in this link :- https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/dynamicme... 

Thanks,

Avinash

[Syed_Shaik]

@zen_____ 

Use Unique Filenames When Uploading to DAM

The only guaranteed fix is to ensure that each asset name is unique across the DAM (at least for assets synced to Dynamic Media).
You can enforce this by:

• Renaming assets before upload.

• Using a naming convention, e.g.:

  HeroImage_page1.png HeroImage_page2.png

• Automating renaming with a custom upload workflow or asset listener.

---

2. Use Folder-based Dynamic Media Publish Contexts

If possible, separate uploads by folder mappings in DM configuration.
For example:

• Configure multiple DM company folders or root paths.

• Map /content/dam/page1 and /content/dam/page2 to different DM publish contexts, so filenames don’t collide.

---

3. Disable DM Upload for Certain Folders

If some folders don’t need Dynamic Media renditions, exclude them:

• Go to AEM → Tools → Cloud Services → Dynamic Media Configuration.

• Uncheck or restrict “Dynamic Media Upload Enabled” for those folders.

---

4. Reprocess Problematic Assets

If renditions are already mixed:

• Delete the affected assets from Dynamic Media.

• Re-upload them from AEM after renaming or adjusting the config.

• Run the “Reprocess Assets” workflow.

[Heena_Shirke]

Hi @zen_____ , actual dynamic media file name(which is HeroImage-1 in your case) will be stored under a property dam:scene7File/dam:scene7Name which can be referred for any custom logic.

That property will be stored under this path:
test.svg/jcr:content/metadata > dam:scene7File OR dam:scene7Name