Assets conflict when files you're uploading to Acquia DAM have the same filename and file extension as assets that are already in your site. 

Two important things to know are:

• Assets with the same filename and different extensions (e.g., tulips.jpg and tulips.tif) will not conflict because the extensions differ.
• Filenames are not case sensitive, meaning an asset named MyFile.jpg would conflict with an asset named myfile.jpg. 

When assets conflict, you'll be given the option to resolve conflicts so they can be added to your site.
 

Resolve conflicting assets

Resolve conflicted assets in the Conflicted uploads table on the Uploads page. Or, if you're a DAM admin, you can view and resolve conflicted uploads in the Admin app. Under Global Settings, click Admin dashboard and go to Conflicted Asset Uploads. 

There are several options for resolving conflicting assets:

• Delete the existing asset
• View the existing asset's details
• Rename the existing asset
• Delete the conflicting asset
• Rename the conflicting asset
• Add the conflicting asset as a version

Assets conflict when files you're uploading to Acquia DAM have the same filename and file extension as assets that are already in your site. 

Two important things to know are:

• Assets with the same filename and different extensions (e.g., tulips.jpg and tulips.tif) will not conflict because the extensions differ.
• Filenames are not case sensitive, meaning an asset named MyFile.jpg would conflict with an asset named myfile.jpg. 

When assets conflict, you'll be given the option to resolve conflicts so they can be added to your site.
 

Resolve conflicting assets

Resolve conflicted assets in the Conflicted uploads table on the Uploads page. Or, if you're a DAM admin, you can view and resolve conflicted uploads in the Admin app. Under Global Settings, click Admin dashboard and go to Conflicted Asset Uploads. 

There are several options for resolving conflicting assets:

• Delete the existing asset
• View the existing asset's details
• Rename the existing asset
• Delete the conflicting asset
• Rename the conflicting asset
• Add the conflicting asset as a version
• Add the conflicting asset and the asset's metadata, categories, and asset groups as a version 

Set version preferences for conflicting assets in upload profiles

You can create and edit upload profiles and set version preferences so that when assets conflict, only the assets will automatically be added as versions or so that the assets and their metadata will be added as versions. You can also choose to not add conflicting assets as versions at all and have users resolve them.

Do not automatically add conflicted uploads

When you choose to not automatically add conflicted uploads, conflicts will not be added as versions of existing assets and they'll be listed in the Conflicted Uploaded Assets table for you to resolve. This is where you can add assets as versions or add assets and their metadata as versions.

Automatically add the version file only for conflicting uploads

When you choose to automatically add conflicting assets as versions, conflicts will automatically be added as versions of existing assets. The new versions will inherit existing versions' metadata. Metadata from new versions will not replace metadata in existing versions and no new metadata from an upload profile (glossary term, activate to view definition) will be added. The assets will not be listed in the Conflicted Uploaded Assets table.

Automatically add the version file and group information for conflicting uploads

When you choose to automatically add conflicting assets and their metadata as versions, conflicts will automatically be added as versions of existing assets. The new versions will inherit the previous version's metadata AND any new metadata from the upload profile, or if it's mapped from embedded metadata. The assets will not be listed in the Conflicted Uploaded Assets table.

If there's embedded metadata that differs between conflicting and existing assets, and if you select to add the file and group information, the embedded metadata is not inherited from existing assets embedded metadata.

Note that when a conflicting asset's metadata, categories, and asset groups are identical to an existing asset's, you can choose to either add the file only or and the file and group information.