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.
Benjamin
5:44
Use conditionals and transforms in Framer CMS fields
Learn how to use conditionals and transforms in Framer CMS fields. With the Is Set conditional for Formatted Text fields, you can adapt your layout based on when your CMS Content exists. See How to create flexible CMS detail pages.
Lesson details
Use conditionals to show, hide, or change content based on whether a CMS field matches the required value. Add transforms when a stored value needs formatting before display, and keep the original CMS data reusable across layouts.
Test empty fields, unexpected values, and every conditional branch with real items. Avoid stacking transformations until editors can no longer predict how the collection value becomes the rendered result.
Build with representative collection data rather than one ideal record. Empty values, long titles, missing media, and several references expose binding and layout problems before editors meet them.
Frequently asked questions
How do I use conditionals and transforms in Framer CMS fields?
Learn how to use conditionals and transforms in Framer CMS fields. With the Is Set conditional for Formatted Text fields, you can adapt your layout based on when your CMS Content exists. See How to create flexible CMS detail pages.
What does this lesson cover?
The lesson covers the settings and steps used to use conditionals and transforms in Framer CMS fields. See How to create flexible CMS detail pages. 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 conditionals and transforms in Framer CMS fields?
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.