DocumentationExperience Cloud KCS

AEM LTS: DAM Touch UI List View shows incorrect asset size (1 B) after ACS Content Sync

Last update: September 3, 2026

This article explains why DAM Touch UI List View displays an incorrect asset size of 1 B (1 byte) after content synchronization and how to resolve it.

Description description

Environment

Adobe Experience Manager (AEM) LTS (including 6.5)

Issue/Symptoms

  • In DAM Touch UI List View, certain assets display a file size of 1 B instead of the expected value.
  • The same assets show the correct file size in Classic UI.
  • This occurs after synchronizing content from one AEM instance to another using ACS Content Sync.
  • The dam:size property on affected assets is set to 1 on the target system, while the source system shows the correct value (For example: 184628).
  • When the asset package is installed directly (bypassing ACS Content Sync), the issue doesn’t occur.

Example metadata difference:

Source system: dam:size = {Long}184628
Target system: dam:size = {Long}1
  • No error messages are shown in the UI.
  • The issue is reproducible by synchronizing assets using ACS Content Sync and viewing them in Touch UI List View.

Cause

ACS Content Sync overwrites the dam:size property with an incorrect value (1), causing Touch UI List View to display 1 B. Classic UI calculates size directly from the asset binary, so it’s not affected.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Update ACS Content Sync configuration:

    • Ensure that your ACS Content Sync process doesn’t write or default the jcr:content/metadata/dam:size property on the target system.

  2. Identify affected assets:

    • In AEM LTS, locate assets where dam:size = 1 under the relevant asset paths.

  3. Recompute asset size metadata:

    • Run the DAM Update Asset or Add Asset Size workflow on the affected assets. This will recalculate dam:size from the binary data.

  4. Verify the fix:

    • Check the same assets in Touch UI List View; the file size should now display correctly and match the value shown in Classic UI.

  5. For future migrations:

    • Treat dam:size as a system-maintained field and avoid modifying it in custom tools or workflows.
    • Raise a bug with the ACS Commons community if the issue persists.
recommendation-more-help
experience-cloud-kcs-help-kbarticles