DocumentationExperience Cloud KCS

Asset name validation differs between Assets View and Admin View in AEM Assets

Last update: October 14, 2026

In Adobe Experience Manager (AEM) Assets, asset name validation behaves differently between Assets View and Admin View. Assets View allows asset names that contain unsupported characters, while Admin View blocks them through validation. To fix this issue, use supported naming conventions, validate filenames before upload, and rename existing assets that contain unsupported characters.

Description description

Environment

Adobe Experience Manager (AEM), all supported versions.

Symptoms

  • In AEM Assets Admin View, validation blocks uploading or renaming assets with names that contain unsupported characters, such as #.
  • In AEM Assets View, users can upload or rename assets with unsupported characters, such as #, without receiving a validation error.
  • Assets View does not display a validation message, and the operation completes successfully.
  • Assets with unsupported names can cause issues in production environments or downstream integrations.

Cause

AEM Assets View and Admin View currently use different asset name validation rules. This difference creates a compatibility gap that allows unsupported characters in asset names through Assets View.

Resolution resolution

Follow the steps below to resolve the issue.

  1. Avoid using unsupported characters, such as #, in asset names, especially for assets that must remain compatible across AEM interfaces and integrations.
  2. Implement filename validation before uploading or migrating assets to AEM to prevent unsupported characters in asset names.
  3. If assets with unsupported names already exist, use Admin View or another supported interface to rename the assets and remove unsupported characters.
  4. Monitor Adobe product updates for changes that address this validation inconsistency.
  5. If you encounter issues caused by this behavior, submit a product bug with reproduction details, including the AEM release/build, environment, and steps to reproduce.
  6. To verify the resolution, confirm that asset names in your environment do not contain unsupported characters and that Admin View validates uploads and renames as expected.
recommendation-more-help
experience-cloud-kcs-help-kbarticles