How the Framer CMS Works

The Framer CMS stores repeating content — blog posts, case studies, team bios — as collections of items with typed fields, which you design a page around once and then populate by adding items, not by duplicating pages. It's built into every Framer plan in some form, but the number of collections and items you can hold is capped by plan, and those caps change if you add on more. Here's the structure and the limits, sourced from Framer's own Academy lessons, help articles, and pricing page.

What is a collection, an item, and a field?

Framer's own Academy lesson gives the plain definitions: "A collection groups related content such as articles, projects, or team members," "Each item is one record" within that collection, and "Fields define the text, images, dates, links, and other values every record can contain" (Framer Academy, checked September 2026). Put together: "The CMS contains collections, each collection contains items, and fields define the information stored in every item." Supported field types include text, date, media (image/video), link, color, toggle, multi-select option, number, and file upload, plus a collection reference field that connects an item to a related record — or several — in another collection.

What's the difference between a CMS list page and a detail page?

Framer builds two page types around a collection, and they do different jobs:

• Collection list — displays multiple items from a collection on one page, in a repeating layout. Per Framer's Academy: you "add a collection list to the page, connect it to the correct CMS collection, and design the repeated item with bound title, image, link, and supporting fields," then set the list layout, gap, columns and item limit, and configure "sorting, filtering, pagination, and empty states" as the collection grows (Framer Academy, "Create CMS collection lists", checked September 2026). This is your index — a blog homepage, a portfolio grid.
• CMS detail page — one reusable layout for a single item's full content. To create one: "Open the Pages panel, choose New CMS Page, select the collection, and choose Detail Page" (Framer Academy, "Create a CMS detail page in Framer", checked September 2026). Framer's own description: "A CMS detail page is one reusable layout for individual items in a collection" — design it once, and it renders differently for every item using that item's own field values. You can also add a second collection's list onto a detail page, for something like a "related items" block, by dragging that collection from the Insert menu's Collection Lists section onto the canvas.

What are the CMS limits by plan?

Framer's pricing page states specific collection and item caps per plan, and add-on limits beyond them, so re-check this table against the live page before you commit content to a plan:

(Source: Framer, Pricing, checked September 2026.) Framer's own FAQ on that page confirms the ceiling for add-ons on Pro: "With add-ons you can have up to 40,000 CMS items, 40 CMS collections, 2 TB of bandwidth, 700 pages, and 1.5M events on the Pro plan." The add-on pricing shown on the same page is "$40 per 10" additional collections (to a 40 max) and "$20 per 10,000" additional items (to a 40,000 max).

The Free plan figures come from a separate FAQ answer on the same page: "Projects on the Free plan include access to 10 CMS collections, 1,000 pages, 5 MB file uploads, and one free locale to try."

Can I import and export CMS content in bulk?

Yes, both directions, through marketplace plugins published by Framer itself. CMS Export is listed as "by Framer", which lets you "export any CMS collection as a CSV file" (Framer Marketplace, "CMS Export", checked September 2026). CSV Import is the same: also published by Framer, described as importing "CSV files into the CMS" with "automatic field mapping and validation" and a "built-in conflict resolution system" (Framer Marketplace, "CSV Import", checked September 2026).

Before importing, Framer's Academy lesson recommends you "prepare the CSV with one header per CMS field, stable values for the slug or identifier, and consistent date, number, image, and reference formats," then "import it into the matching collection and review the field mapping before Framer creates or updates items" (Framer Academy, "CSV import", checked September 2026). Re-importing the same file with a matching slug updates existing items rather than duplicating them, which makes CSV a workable path for bulk edits, not just a one-time migration.

Can AI add content to the CMS for me?

Framer also lets its own agent populate a collection directly from a written description, rather than through a CSV or the Editor. Framer's help center: you "describe the kind of content you want to manage, like blog posts, team members, or job listings," and "the agent creates the collection, sets up the fields, and adds items for you" (Framer Help, "How to add content to your CMS with Framer Agents", checked September 2026). This runs on the same credit system as Framer's other AI features — check Framer's pricing page for your plan's monthly credit allowance, since it changes by tier. Framer's official External Agents connection (covered in full in our guide to AI editing a Framer site) can also read a CSV you attach to a prompt and map it to your CMS fields directly, as an alternative to the CSV Import plugin's own interface.

Do I actually need the CMS, or is a static page enough?

If every piece of content on your site is genuinely one-off — a single About page, a single pricing page — a collection buys you nothing beyond added complexity. The CMS earns its place when you have several items that share the same shape: blog posts, job listings, portfolio pieces, testimonials. At that point a collection with a detail-page template means designing the layout once instead of once per item, and a collection list means an index page that updates itself as you add items rather than one you edit by hand every time.

If you're choosing between Framer and Webflow specifically and the CMS is a deciding factor, our Framer vs Webflow capability matrix covers how their CMS scale, plan gates, and export paths actually differ — including the fact that Framer has no code export at all, so a CMS-heavy Framer site has no documented way to move its content to a self-hosted alternative beyond the CSV export covered above.

A quick planning checklist

• List your repeating content types (posts, team members, products) — each one is a candidate collection.
• For each collection, define the fields you actually need before creating items, since field types (text, image, reference, and so on) drive what you can bind on the page.
• Decide whether you need a list page, a detail page, or both for each collection.
• Check your plan's collection and item caps against your real content volume — Basic caps out fast at 1,000 items; Pro's add-ons scale to 40,000.
• If migrating content in, prepare your CSV headers to match your field names exactly, and include a stable slug column before importing.
• If you'll ever need to leave Framer, confirm you're comfortable that CSV export is your only documented content portability path — there's no code export to fall back on.

Bottom line: the Framer CMS is a real structured content system — collections, typed fields, list pages, and detail pages — not a simplified stand-in for a full CMS. Its plan-based collection and item caps are explicit and add-on-expandable, CSV import and export are first-party Framer tools rather than third-party workarounds, and Framer's own agent can populate a collection directly from a prompt. Check the current numbers on Framer's pricing page before you commit content to a plan, since caps and add-on pricing are the kind of detail vendors update.