Skip to main content
Haswanth
Level 1
August 26, 2026
Question

Recommendation Required for DAM URL to Asset Delivery URL Conversion

  • August 26, 2026
  • 1 reply
  • 47 views

Hi Team,

We have a requirement to replace existing hardcoded /content/dam asset references in RTE and Text Components with Asset Delivery URLs (URN-based).

Since the content has already been migrated to AEM Cloud, we are looking for the recommended approach to:

  • Map existing DAM paths to Asset Delivery URLs.
  • Update existing content containing /content/dam references.
  • Follow AEM Cloud/Adobe best practices for this conversion.

Could you please share your recommendations on the preferred architectural approach and any considerations we should keep in mind?

    1 reply

    shrutid56001193
    User Group Leader
    shrutid56001193User Group Leader
    User Group Leader
    August 31, 2026

    ​@Haswanth ,

    Whats the purpose behind the requirement?  is it for performance/image optimization, decoupled delivery, or avoiding direct AEM asset URLs? as it may influence the chosen architecture.

    For existing RTE/Text content, I would generally avoid replacing /content/dam/... references directly in the repository with Asset Delivery URLs. The DAM path is the stable AEM asset identifier, whereas the Asset Delivery URL is a delivery representation of that asset.

    A possible approach would be:

    • Keep the DAM path as the canonical asset reference in the stored content.

    • Resolve the referenced asset to its Asset Delivery URL at rendering/delivery time, where applicable.

    • For existing migrated content, identify /content/dam references through a script and validate that each referenced asset has a corresponding Asset Delivery url.

    • If the requirement is specifically to persist Asset Delivery URLs in the content, treat this as a migration exercise with a clear mapping between the original DAM path and the generated delivery URL, rather than a simple string replacement.

    • Consider how future authoring should work so that newly inserted RTE/Text assets follow the same model and the problem does not reappear.

    For a large existing content base, I would recommend a small PoC first, covering RTE images, Text components, different asset types/renditions, and author/publish behavior before running a bulk migration.

    https://www.shrutidamle.com/
      Terms & ConditionsAccessibility statement

      Loading footer...