Guide · Framer

Framer CMS — what it can do and when it's enough

Framer's CMS is built into every plan and handles most common use cases without configuration. Here's what it actually supports, and where it stops.

What the Framer CMS is

A collection-based content system

You define a collection — a set of fields — and add items to it. Each item gets its own page, generated from a template you design once. The classic example is a blog: one template, many posts.

Tightly integrated with the canvas

You connect CMS fields to text layers, image layers and components directly in the Framer editor. No code, no separate template language. What you see in the editor is what the CMS page looks like.

Editable by non-designers

Clients and teammates can add and edit CMS content from a simple table view without touching the visual editor. The design stays intact.

Supported field types

Text — single line
Rich text — formatted content with headings, lists, bold, links
Image — with alt text
Number — integer or decimal
Boolean — true/false toggle
Color — hex picker
Date — date only, no time
Link — external URL
Enum — a fixed list of options (dropdown)

What it handles well

Blog or articles

Title, date, cover image, rich text body, author, category. All supported. Works well up to a few hundred posts.

Project portfolio

Name, year, category, cover, description, images, external link. The most common use case for independent designers and studios — and exactly what the Framer CMS is built for.

Team or people pages

Name, role, photo, bio, social links. Simple collection, straightforward to maintain, easy to hand off to an ops team.

Changelog or release notes

Date, version, rich text. A common need for SaaS products. Design the template once, add entries without touching the editor.

Where it stops

No relational fields

You can't link a blog post to an author collection item. You can't link a project to a client collection. If your content model has relationships between collections, you've hit the ceiling.

No filtering or search on the frontend

You can display a filtered subset of a collection on a page, but there's no live filtering or search the visitor can interact with. For a product catalog or job board, you'd need a custom solution.

No content API

Framer's CMS has no public API. You can't pull content from it programmatically or push to it from an external tool. If your workflow involves syncing content from Notion, Airtable or a headless CMS, you'll need to manage that manually or use a different tool.

Is it enough for your project?

Count your content types

Blog posts, projects, team members, testimonials, FAQs. If each content type is independent — no relationships between them — Framer CMS handles it cleanly.

Check if you need filtering

"Show all posts in category X" on a static page: yes. "Let the visitor filter by category in real time": no.

Think about who edits it

A client or teammate who needs to add a blog post or a new project: Framer CMS is easy to hand off. A team that needs to manage thousands of SKUs or a structured editorial workflow: use a purpose-built CMS.

Guide Framer vs Webflow

How the two tools compare on CMS, design, pricing and performance.

Guide Framer SEO — what you can and can't control

How CMS pages affect your SEO setup in Framer.

Templates Framer templates — minimal, boring by design

Templates with CMS-ready structure where relevant.

Guide All Framer guides

Read all the Framer guides.