If you have ever uploaded an asset to AEM Dynamic Media and seen it come back renamed with a -1 or similar suffix, you have run into Scene7's deduplication behavior — and it catches most teams off guard exactly once before they build a naming convention around it.
Why the suffix appears
Dynamic Media (built on the underlying Scene7 platform) treats the asset name as part of its addressing scheme in the image serving layer. When an asset with the same name already exists in the same publish target, the platform appends a numeric suffix to avoid an addressing collision, rather than overwriting or rejecting the upload.
Where this causes real problems
- Broken image references: if code or Content Fragments reference the asset by an assumed clean name, a silently suffixed name breaks that reference
- Inconsistent naming across environments: the same asset uploaded in a different order across dev, stage, and production can end up with different suffixes in each environment
- Bulk migration tooling: automated asset migration scripts that assume a 1:1 name mapping need explicit handling for this case, or they will silently produce broken links at scale
Designing around it
- Build a naming convention with enough natural uniqueness (SKU, locale, campaign ID) that collisions are rare by design rather than relying on manual renaming discipline
- Where automation uploads assets, check the actual returned asset path after upload rather than assuming the requested name was used
- For bulk re-uploads or migrations, clear or rename existing conflicting assets deliberately as part of the migration script, rather than letting the platform's dedup logic decide silently
The takeaway
This is not a bug — it is Dynamic Media protecting its own addressing scheme — but it behaves like a bug if your naming convention and automation were not designed with it in mind from the start.