Framer New CMS Field: How to handle repeating content properly

What Framer shipped

On 8 September 2026, Framer added a List field to the CMS. It holds repeating content inside a single field: FAQs, feature rows, tutorial steps, case study stages. You add and reorder rows the same way you would in a CMS table, according to the official Framer changelog.

There are two ways to get a list onto the canvas. Insert it from the Insert panel, or select a card you have already designed and use the new Repeat property to repeat that card for each list item. The field also works through the API and with the Framer Agent.

The same release brought inline editing for content editors, duplicating several CMS items at once, and searching for CMS fields in the Insert panel.

Why Title 1, Title 2 was the wrong shape

Until now, repeating content on a single CMS item had one workaround: duplicate the fields. A service page with room for eight FAQs needed sixteen fields, and most items left half of them empty.

That cost the client more than it cost us. The editor filled up with near-identical field names, the order rarely matched the page order, and nobody could tell which numbered slot appeared where. Adding a ninth FAQ was not a content edit any more. It meant new fields in the CMS and new bindings on the canvas, which usually meant a message to us.

A List field removes the ceiling. One row, then another, in the order the reader sees them.

Setting up a List field

1. Open the collection and add a new field of type List.

2. Define the sub-fields inside it. For an FAQ list, that is a plain-text question and a formatted-text answer.

3. Name the sub-fields the way the client thinks about them, not the way the layout is built. Question and Answer beat Heading and Body.

4. On the canvas, either insert the list from the Insert panel, or select an existing card and switch on Repeat.

5. Bind the elements inside the card to the sub-fields, then check the preview on an item that has the fewest rows filled in.

That last check matters. A card designed against five rows can look broken on an item with one.

Migrating an existing collection

Framer's own route is to ask the Framer Agent to convert repeated CMS fields into a List. The Agent also reconnects the CMS data on the canvas, which used to take an afternoon.

A safer order of operations on a live client site:

1. Work on a branch, or duplicate the project.

2. Run the conversion with the Agent.

3. Check every template that reads those fields, including any page where only the first three of eight slots were ever bound.

4. Publish, check the live pages, then delete the old numbered fields.

One caveat: if the collection is fed by a plugin or an external sync. Framer's developer changelog lists Plugins 5.0 as a breaking release: managed collection array items now need stable IDs, and array field definitions changed shape. Test that integration before you migrate anything it writes to.

When a List field is the wrong tool

A List field is content that belongs to its parent item. It has no page, no URL and no metadata of its own, and nothing else on the site can pull one row out of it.

So use a List field for FAQs on a service page, steps in a process, feature rows on a pricing card, or the stages of a case study.

Use a separate collection with references when the entries need their own pages, their own SEO fields, or when the same entry appears on several pages, and you want to edit it once. Team members, blog posts and services still belong in collections.

The rule of thumb: if a reader could ever land on it directly, it is a collection item, not a list row.

What it changes at handover

We build in Framer partly because clients can maintain the site themselves after launch. Every numbered field worked against that. Fewer fields means less to explain, fewer wrong guesses, and fewer edits that need us.

To be clear about the limit: this tidies how content is structured and who can safely edit it. It does not change how your pages rank or convert. It does make the sort of content that supports both, such as a well-kept FAQ section, cheap enough to actually keep up to date.