AEM Content Fragments vs Experience Fragments Explained
Confused about AEM Content Fragments vs Experience Fragments? Compare their features, storage, and delivery.
If you've worked with Adobe Experience Manager for any length of time, you've hit this fork in the road: you need to reuse some content, and AEM offers two things that sound almost identical — Content Fragments and Experience Fragments. They're both reusable, both live outside individual pages, and both help you avoid copy-pasting content everywhere. So which one do you reach for?
The short answer comes down to one word: presentation. Content Fragments are design-agnostic; Experience Fragments carry their design with them. Everything else follows from that single distinction.
Content Fragments (CF): structured content, no design
A Content Fragment is a reusable, presentation-agnostic piece of content composed of structured data elements like text, dates, and references. Think of it as pure content with no opinion about how it looks. The channel consuming it — a website, a mobile app, a smartwatch — decides the presentation.A few defining characteristics:
- Model-driven. Every CF is based on a structured, form-based data model (the Content Fragment Model) that defines the fields authors fill in. This enforces consistency across every fragment of the same type.
- Stored as an asset. Under the hood, a Content Fragment is implemented as a
dam:Assetand managed in AEM Assets. - Headless-ready. This is CF's superpower. Content is delivered as JSON via AEM's Headless GraphQL APIs, Content Services, or the Assets HTTP API for consumption by any front end.
- Rich authoring features. Variations, versions, visual diff between versions, annotations, and translation/localization support.
CFs shine for headless use cases over GraphQL, structured or form-based content entry, long-form editorial content, and content managed independently of the channels that deliver it. Product data, author bios, blog articles, FAQs, testimonials — the "what," not the "how."
Experience Fragments (XF): content and presentation together
An Experience Fragment is a reusable composite of one or more AEM Components that defines both content and presentation, forming an experience that makes sense on its own. It's a fully-designed, ready-to-drop-in chunk of a page.
Its defining traits:
- Presentation-centric. An XF is an unstructured composition of AEM components that defines the design and layout of its content and is used "as is" in channels.
- Stored as a page. Technically, an XF is implemented as a
cq:Pageand defined by Editable Templates, with a native HTML rendition. - Channel-specific variations. Variations are channel or context specific and kept in sync via AEM Live Copy, so a hero built for web can spawn a variation for Facebook that stays connected to the original.
- Flexible export. XFs can be exported as plain HTML for third-party systems, or pushed to Adobe Target as HTML or JSON offers for personalization campaigns.
XFs are the right tool for centralized management of multi-channel promotional collateral, content reused across multiple pages, and site chrome like headers and footers. Header, footer, campaign banners, hero areas, calculators and branded blocks that should look identical everywhere — the "how" comes baked in.
Side-by-side comparsion
| Content Fragment | Experience Fragment | |
| Focus | Content only | Content + presentation |
| Design/layout | Agnostic (channel decides) | Built-in |
| Stored as |
|
|
| Defined by | Content Fragment Model | Editable Template |
| Primary delivery | JSON (GraphQL / Content Services) | HTML (or JSON with embedded HTML) |
| Best for | Headless, omnichannel, structured data | Reusable designed sections, site chrome |