DocumentationExperience Cloud KCS

Dynamic Media: Duplicate images with numeric suffixes are created instead of overwriting existing assets

Last update: September 8, 2026

This article describes the behavior in Adobe Experience Manager Dynamic Media where duplicate image assets with numeric suffixes are created during uploads or updates and provides guidance on how to address this issue.

Description description

Environment

Adobe Experience Manager Dynamic Media/Scene7 (all versions)

Issue/Symptoms

  • When you upload or update images through an integrated application, Dynamic Media/Scene7 creates multiple assets with names such as .tif, _1.tif, _2.tif, and so on, instead of overwriting the original image.
  • Only the most recently suffixed asset (for example, _1.tif) is updated by the application, while the original asset remains unchanged.
  • This behavior occurs for some images, particularly when image content, such as the background color, changes and is uploaded again.
  • The issue does not occur for all images. Some images are overwritten as expected.
  • No error message appears, but the presence of multiple assets with similar names is unexpected.

Cause

Dynamic Media/Scene7 creates suffixed asset names, such as _1 or _2, when uploads do not meet the configured overwrite conditions. Common causes include differences in folder location, file extension, or update workflow. Delete-and-re-upload workflows or asset renames can also trigger this behavior because of internal asset retention.

Resolution resolution

Follow these steps to resolve the issue:

  1. In Dynamic Media Classic, go to the Upload / Overwrite Images settings for your company.
  2. Confirm whether you use Overwrite in current folder, same base name/extension or Overwrite in any folder, same base asset name regardless of extension.
  3. Align your upload or update process with the configured overwrite settings.
  4. Ensure that all updates for a product image use the same filename.
  5. Upload to the same folder when using current folder mode, or use the same base name across folders when any folder mode is enabled.
  6. Review your application update workflow.
  7. Verify whether the application uploads a new file with the same filename and relies on overwrite, renames assets during the update process, or deletes and re-uploads assets with the same name.
  8. Avoid delete-and-re-upload workflows because Scene7 can retain the original asset in its internal trash, causing the new upload to receive a numeric suffix.
  9. Upload new content to the same asset handle or use consistent filename and folder combinations.
  10. Avoid name collisions during bulk uploads by ensuring filenames are unique for each product or version, or by strictly controlling folder usage for each product line to support predictable overwrite behavior.
  11. Validate the behavior with a controlled test.
  12. Upload a sample product image and confirm the asset name and URL.
  13. Perform an update by using your current workflow.
  14. Check whether Dynamic Media creates a new suffixed asset or overwrites the original asset.
recommendation-more-help
experience-cloud-kcs-help-kbarticles