Experience Fragments in AEM, and How They Differ from Content Fragments
Experience Fragments in AEM: what they are, templates, variations, building blocks, MSM, the Experience Fragment component, plain HTML and Adobe Target export, and Content Fragments vs Experience Fragments.
Rewritten in October 2026 for AEM as a Cloud Service and AEM 6.5, checked against Adobe's Experience Fragments documentation.
On this page
An Experience Fragment is a reusable piece of a page in Adobe Experience Manager: one or more components together with their layout. A site header, a footer, a promotional banner, a sign-up block. Authors build it once, use it on many pages, and change it in one place. Experience Fragments can also be exported as HTML to other channels and to Adobe Target.

More in Content Fragments and headless
- Content Fragments in AEM: Models, Editor, Variations and Delivery
Enabling models, the 11 data types, the Content Fragments console and editor, variations, references, publishing and delivery.
- AEM Headless Tutorial: From Content Fragments to a React App
Configuration, models, fragments, a GraphQL endpoint, persisted queries and a React client, step by step.
- AEM GraphQL API: Endpoints, Persisted Queries and Examples
The schema from Content Fragment Models, endpoints, GraphiQL, filtering and paging, persisted queries, caching and CORS.
- AEM 6.4 Content Fragment Output as JSON
Why Content Fragments need JSON, the two kinds of fragments, and how to get JSON for a fragment and for a fragment authored on a page with the AEM 6.4 JSON exporter.
- Create a Content Services Endpoint in AEM 6.4
How to configure a Content Services endpoint in AEM 6.4 that exports Content Fragment variations as JSON for mobile apps and single-page applications.