Do you build things with AMP? Fill out the new AMP Developer Survey!



Dynamically downloads data and creates list items using a template.

Required Scripts

<script async custom-element="amp-list" src=""></script>

Fetches content dynamically from a CORS JSON endpoint and renders it using a supplied template.


The <amp-list> component fetches dynamic content from a CORS JSON endpoint. The response from the endpoint contains data, which is rendered in the specified template.

Your endpoint must implement the requirements specified in the CORS Requests in AMP spec.

You can specify a template in one of two ways:

  • a template attribute that references an ID of an existing templating element.
  • a templating element nested directly inside the amp-list element.

When using <amp-list> in tandem with another templating AMP component, such as <amp-form>, note that templates may not nest in valid AMP documents. In this case a valid workaround is to provide the template by id via the template attribute. Learn more about nested templates in <amp-mustache>.

For more details on templates, see AMP HTML Templates.

Example: Displaying a dynamic list

In the following example, we retrieve JSON data that contains URLs and titles, and render the content in a nested amp-mustache template.

  <template type="amp-mustache">

    <div class="url-entry">
      <a href="{{url}}">{{title}}</a>
Open this snippet in playground

Here is the JSON file that we used:

  "items": [
      "title": "AMP YouTube Channel",
      "url": ""
      "title": "",
      "url": ""
      "title": "AMP By Example",
      "url": ""
      "title": "AMP Start",
      "url": ""

Here is how we styled the content fetched:

amp-list div[role='list'] {
  display: grid;
  grid-gap: 0.5em;


The request is always made from the client, even if the document was served from the AMP Cache. Loading is triggered using normal AMP rules depending on how far the element is from the current viewport.

If <amp-list> needs more space after loading, it requests the AMP runtime to update its height using the normal AMP flow. If the AMP runtime cannot satisfy the request for the new height, it will display the overflow element when available. Notice however, that the typical placement of <amp-list> elements at the bottom of the document almost always guarantees that the AMP runtime can resize them.

By default, <amp-list> adds a list ARIA role to the list element and a listitem role to item elements rendered via the template. If the list element or any of its children are not "tabbable" (accessible by keyboard keys such as the a and button elements or any elements with a positive tabindex), a tabindex of 0 will be added by default to the list item.

XHR batching

AMP batches XMLHttpRequests (XHRs) to JSON endpoints, that is, you can use a single JSON data request as a data source for multiple consumers (e.g., multiple <amp-list> elements) on an AMP page. For example, if your <amp-list> makes an XHR to an endpoint, while the XHR is in flight, all subsequent XHRs to the same endpoint won't trigger and will instead return the results from the first XHR.

In <amp-list>, you can use the items attribute to render a subset of the JSON response, allowing you to have multiple <amp-list> elements rendering different content but sharing a single XHR.

Specifying an overflow

Optionally, the <amp-list> component can contain an element with the overflow attribute. Add an element with the AMP overflow attribute to amp-list if the AMP framework is unable to size it as requested. If you include a child element of amp-list with the overflow attribute, it will appear if one of the following conditions are met:

  • The bottom of amp-list is below the viewport.

  • The bottom of amp-list is within 15% of the height of the entire page and within 1000px of the end of the page.

If amp-list is outside the viewport, it will be automatically expanded.

Example: Displaying an overflow when the list needs more space

In the following example, we display a list of images and titles. Because the <amp-list> content requires more space than available, the AMP framework displays the overflow element.

See more
  <template type="amp-mustache">

    <div class="image-entry">
      <amp-img src="{{imageUrl}}" width="100" height="75"></amp-img>
      <span class="image-title">{{title}}</span>
  <div overflow class="list-overflow" style="background-color:red;">
    See more
Open this snippet in playground

AMP applies the following CSS to elements with the overflow attribute:

.list-overflow[overflow] {
  position: absolute;
  bottom: 0;
  left: 0;
  right: 0;

Placeholder and fallback

Optionally, <amp-list> supports a placeholder and/or fallback.

  • A placeholder is a child element with the placeholder attribute. This element is shown until the <amp-list> loads successfully. If a fallback is also provided, the placeholder is hidden when the <amp-list> fails to load.
  • A fallback is a child element with the fallback attribute. This element is shown if the <amp-list> fails to load.

Learn more in Placeholders & Fallbacks. Note that a child element cannot be both a placeholder and a fallback.

<amp-list src="">
  <div placeholder>Loading ...</div>
  <div fallback>Failed to load data.</div>

Refreshing data

The <amp-list> element exposes a refresh action that other elements can reference in on="tap:..." attributes.

<button on="tap:myList.refresh">Refresh List</button>
<amp-list id="myList" src="">
  <template type="amp-mustache">

Dynamic resizing

In several cases, we may need the <amp-list> to resize on user interaction. For example, when the <amp-list> contains an amp-accordion that a user may tap on, when the contents of the <amp-list> change size due to bound CSS classes. The changeToLayoutContainer action handles this by changing the amp list to layout="CONTAINER" when triggering this action. See the following example:

<button on="tap:list.changeToLayoutContainer()">Show Grid</button>
  <template type="amp-mustache">
{{title}}  </template>


src (required)

The URL of the remote endpoint that returns the JSON that will be rendered within this <amp-list>. This must be a CORS HTTP service. The URL's protocol must be HTTPS.

Your endpoint must implement the requirements specified in the CORS Requests in AMP spec.

If fetching the data at the src URL fails, the <amp-list> triggers a low-trust fetch-error event.

items (optional)

Defines the expression to locate the array to be rendered within the response. This is a dot-notated expression that navigates via fields of the JSON response. By defaut <amp-list> expects an array, the single-item attribute may be used to load data from an object.

  • The default value is "items". The expected response: {items: [...]}.
  • If the response itself is the desired array, use the value of ".". The expected response is: [...].
  • Nested navigation is permitted (e.g., "field1.field2"). The expected response is: {field1: {field2: [...]}}.

When items="items" is specified (which, is the default) the response must be a JSON object that contains an array property called "items":

  "items": [...]

max-items (optional)

An integer value specifying the maximum length of the items array to be rendered. The items array will be truncated to max-items entries if the returned value exceeds max-items.

single-item (optional)

Causes <amp-list> to treat the returned result as if it were a single element array. An object response will be wrapped in an array so {items: {...}} will behave as if it were {items: [{...}]}.

binding (optional)

For pages using <amp-list> that also use amp-bind, controls whether or not to block render on the evaluation of bindings (e.g. [text]) in rendered children.

We recommend using binding="no" or binding="refresh" for faster performance.

  • binding="no": Never block render (fastest).
  • binding="refresh": Don't block render on initial load (faster).
  • binding="always": Always block render (slow).

If binding attribute is not provided, default is always.

Common attributes

This element includes common attributes extended to AMP components.

Invalid AMP email attributes

The AMP for Email spec disallows the use of the following attributes on the AMP email format.

  • [src]
  • [state]
  • [is-layout-container]
  • auto-resize
  • credentials
  • data-amp-bind-src
  • load-more
  • load-more-bookmark
  • reset-on-refresh
  • xssi-prefix


See amp-list rules in the AMP validator specification.

Need more help?

You've read this document a dozen times but it doesn't really cover all of your questions? Maybe other people felt the same: reach out to them on Stack Overflow.

Go to Stack Overflow
Found a bug or missing a feature?

The AMP project strongly encourages your participation and contributions! We hope you'll become an ongoing participant in our open source community but we also welcome one-off contributions for the issues you're particularly passionate about.

Go to GitHub