Mapping keywords from Adobe Bridge/Lightroom to AEM | Community
Skip to main content
J
Justin Best
Level 2
February 24, 2026
Solved

Mapping keywords from Adobe Bridge/Lightroom to AEM

  • February 24, 2026
  • 3 replies
  • 79 views

I’m setting up our keyword hierarchy structure in AEM. I would like to mirror these in Adobe Bridge and Lightroom so I can add keywords in Bridge. I’m running into some difficulties in understanding the workflow and what’s needed.

Has anybody done this? Can you provide any step-by-step directions?

Thanks,

Justin

Best answer by lisab94981616

Yes! I think you can do this with XMP metadata. Give me another week to mock something up in the evenings and I’ll share over a quick video to see if I have it right.

3 replies

L
lisab94981616
Level 2
February 26, 2026

​@Justin Best - By “keyword strategy” do you mean tags or something else? Because AEM Assets can read XMP metadata, which also works in Adobe Bridge and Adobe Lightroom. Let me know and I’ll write step-by-step instructions for you, thanks!

 

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/admin/xmp-metadata

https://helpx.adobe.com/bridge/using/metadata-adobe-bridge.html

https://helpx.adobe.com/lightroom-classic/help/metadata-basics-actions.html

    J
    Justin BestAuthor
    Level 2
    February 26, 2026

    The end goal is to be able to use Bridge and LR to add keywords to assets before putting them in AEM.

    I was able to map the basic IPTC info (caption, headline, etc), but I can’t figure out how to do this for Keywords between Bridge and AEM

    I have my my Keywords built out in Adobe Experience Manager and in Bridge, but I don’t know how to get those fields to sync in AEM. 

    Would appreciate any help or instructions you can provide. 

    Thank you!!!

      L
      lisab94981616Accepted solution
      Level 2
      March 1, 2026

      Yes! I think you can do this with XMP metadata. Give me another week to mock something up in the evenings and I’ll share over a quick video to see if I have it right.

        J
        Justin BestAuthor
        Level 2
        March 2, 2026

        That would be amazing, thank you for the help!

        AmitVishwakarma
        Community Advisor
        AmitVishwakarmaCommunity Advisor
        Community Advisor
        March 2, 2026

        Hi ​@Justin Best ,

        To make Bridge/Lightroom keywords show up in AEM and stay in sync, treat XMP dc:subject as the single source of truth:

        1. In Bridge
          • Turn on keyword writing so keywords are stored in XMP (Preferences -> Keywords -> enable writing/hierarchical keywords).
        2. In Lightroom Classic
          • Enable “Automatically write changes into XMP” so all keyword edits are written into the file/sidecar.
        3. In AEM (metadata schema)
          • Edit the metadata schema used for your DAM folders.
          • Add a multi-value text or “Keywords” field and map it to: 
            ./jcr:content/metadata/dc:subject
          • Assign that schema to the folder where you upload assets.

        Thanks,
        Amit

        Amit Vishwakarma - Adobe Commerce Champion 2025 | 16x Adobe certified | 4x Adobe SME
          J
          Justin BestAuthor
          Level 2
          March 5, 2026

          Hi Amit,

          Thank you for sharing this detailed explanation. I was able to get this to work, but it’s not exactly what I’m looking for.

          I want to mirror the the 7 specific metadata fields I have in AEM (Ex: Subject, Building, Location) instead of the having all tags in one keyword field.

          Thanks,

          Justin

           

          L
          lisab94981616
          Level 2
          March 9, 2026

          Justin, XMP metadata that’s authored in Creative Cloud shows in AEM like the attached screenshot. Is this what you’re seeing on your end as well? If not, let’s huddle and figure out what’s going on. If it is showing like this, and doesn’t meet the use case, we may need to give it more thought.

           

          Terms & ConditionsAccessibility statement

          Loading footer...