This lesson was released before Agents, Branching, and the CMS update on June 16, 2026. Some UI may differ, but the core concepts still apply.

Edoardo
3:47
Use CMS collection references in Framer
Learn how to use CMS collection references in Framer. This update introduces Collection References in the CMS. This long awaited feature allows you to reference items from one CMS collection to another, enabling dynamic, reusable content throughout your site. You will work with CMS fields, collection items, or collection lists while keeping the content editable in Framer.
Lesson details
Add a collection reference field and connect each item to the related record or records in another CMS collection. Bind fields from the referenced item in a list or detail page so shared data such as an author, category, or product does not need to be copied.
Choose a single or multi-reference based on the content relationship. Test missing references and repeated combinations, and update the source record when shared information needs to change everywhere.
Use stable fields for content and let the page template handle presentation. That separation makes bulk updates safer and keeps every CMS item consistent with the same design rules.
Frequently asked questions
How do I use CMS collection references in Framer?
Learn how to use CMS collection references in Framer. This update introduces Collection References in the CMS. This long awaited feature allows you to reference items from one CMS collection to another, enabling dynamic, reusable content throughout your site. You will work with CMS fields, collection items, or collection lists while keeping the content editable in Framer.
What does this lesson cover?
The lesson covers the settings and steps used to use CMS collection references in Framer. See CMS References. Follow the demonstrated order in your project and review each change on the canvas before moving to the next step.
Does this workflow keep CMS content editable?
Yes. The workflow uses Framer CMS fields, items, references, or collection lists rather than flattening the content into a static page. Review the field mapping and each affected item after the change so editors can keep managing the content from the CMS.
Will CMS changes update collection pages?
CMS-backed collection lists and detail pages use the values stored in their connected fields. A field or item change can therefore appear wherever that content is bound. Review the list page, detail page, references, filters, and empty states after completing the workflow.
What should I review after I use CMS collection references in Framer?
Review the exact pages and elements changed by the workflow. Confirm that copy, links, accessibility, responsive behavior, and interaction states still work as intended. Use preview for the final check and keep publishing separate from editing so you can fix problems before visitors see the update.

