You're viewing help content for version:

An Experience Fragment is a group of one or more components including content and layout that can be referenced within pages. They can contain any component.

An Experience Fragment:

  • Is a part of an experience (page).
  • Can be used across multiple pages.
  • Is based on a template (editable only) to define structure and components.
  • Is made up of one or more components, with layout, in a paragraph system.
  • Can contain other experience fragments.
  • Can be combined with other components (including other Experience Fragments) to form a complete page (experience).
  • Can have different variations, which may share content and/or components.
  • Can be broken down into building blocks that can be used across multiple variations of the fragment.

You can use Experience Fragments:

  • If an author wants to re-use parts (a fragment of an experience) of a page, they need to copy and paste that fragment. Creating and maintaining these copy/paste experiences is time-consuming and prone to user errors. Experience Fragments eliminate the need for copy/paste.
  • To support the headless CMS use-case. Authors want to use AEM only for authoring but not for delivering to the customer. A third party system/touchpoint would consume that experience and then deliver to the end user.


Write access for experience fragments requires the user account to be registered in the group:


Please contact your system administrator if you are experiencing any issues.

When Should You Use Experience Fragments?

Experience Fragments should be used:

  • Whenever you want to reuse experiences.
    • Experiences that will be reused with same or similar content
  • When you use AEM as a content delivery platform for third parties.
    • Any solution that wants to use AEM as the content delivery platform
    • Embedding content in third party touchpoints
  • If you have an Experience with different variations or renditions.
    • Channel or context-specific variations
    • Experiences that make sense to group (for example a campaign with different experiences across channels)
  • When you use Omnichannel Commerce.
    • Sharing commerce-related content on social media channels at scale
    • Making touchpoints transactional

Creating an Experience Fragment

To create an Experience Fragment:

  1. Select Experience Fragments from the Global Navigation.

  2. Select Create. You can create Folders and/or Experience Fragments.

    Creating folders allows you to create a meaningful structure for your Experience Fragments.

  3. From the required folder, select Create then Experience Fragment to open the Create Experience Fragment wizard.

    Select the required Template, then Next:



    You can use the template editor to create your own template.

    Only editable templates can be used; static templates are not fully compatible.

  4. Enter the Properties for your Experience Fragment.

    A Title is mandatory. If the Name is left blank it will be derived from the Title.

  5. Click Create.

    A message will be displayed. Select:

    • Done to return to the console
    • Open to open the fragment editor

Editing your Experience Fragment

The Experience Fragment Editor offers you similar capabilities to the normal page Editor. See Editing Page Content for more information on how to use it. 

The following example procedure illustrates how to create a teaser for a product:

  1. Drag and drop a Category Teaser from the Components Browser.

  2. Select Configure from the component toolbar.

  3. Add the Asset and define the Properties as required.

  4. Confirm the definitions with Done (tick icon).

  5. Add more components as required.

Creating An Experience Fragment Variation

You can create variations of your Experience Fragment, depending on your needs:

  1. Open your fragment for editing.

  2. Open the Variations tab.

  3. Create allows you to create:

    • Variation
    • Variation as live-copy.
  4. Define the required properties:

    • Template
    • Title
    • Name; if left blank it will be derived from the Title
    • Description
    • Variation tags
  5. Confirm with Done (tick icon), the new variation will be shown in the panel:


Using your Experience Fragment

You can now use your Experience Fragment when authoring your pages:

  1. Create an instance of the Experience Fragment component, by dragging the component from the Components browser to the page paragraph system:

  2. Add the actual Experience Fragment to the component instance; either:

    • Drag the required fragment from the Assets Browser and drop onto the component
    • Select Configure from the component toolbar and specify the fragment to use, confirm with Done (tick)


    Edit, in the component toolbar, operates as a shortcut to open the fragment in the fragment editor.

Building Blocks

You can select one or more components to create a building block for recycling within your fragment:

Creating a Building Block

To create a new Building Block:

  1. In the Experience Fragment editor, select the components you want to re-use:

  2. From the components toolbar, select Convert to building block:


    For example:

  3. Enter the name of the Building Block, and confirm with Convert:

  4. The Building Block will be shown in the tab, and can be selected in the paragraph system:


Managing a Building Block

Your building block is visible in the Building Blocks tab. For each block, the following actions are available:

  • Go to master: open the master variation in a new tab
  • Rename
  • Delete  

Using a Building Block

You can drag your building block to the paragraph system of any fragment, as with any component.

The Plain Rendition

Using the .plain. selector in the URL, you can access the plain HTML rendition.

This is available from the browser, but its primary purpose is to allow other applications (for example, third party web apps, custom mobile implementations) to access the content of the Experience Fragment directly, using only the URL.

The plain HTML rendition adds the protocol, host and context path to paths that are:

  • of the type: src, href, or action
  • or end with: -src, or -href

For example:



Links always reference the publish instance. They are intended to be consumed by third parties, so the link will always be called from the publish instance, not the author.


This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy