The Framer CMS stores repeating content, such as blog posts, case studies or team bios, as collections of items with typed fields. You design a page around a collection once, then add items instead of duplicating pages. Every Framer plan includes some CMS allowance, and the number of collections and items rises with the plan: Basic has 2 collections and 1,000 items, Pro has 10 collections and 2,500 items. The structure and limits below come from Framer's Academy lessons, help articles and pricing page.
What is a collection, an item, and a field?
Framer's Academy lesson gives the 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). In short: "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 or video), link, color, toggle, multi-select option, number and file upload. A collection reference field connects an item to a related record, or several, in another collection.
What is the difference between a CMS list page and a detail page?
A list page shows many items from one collection, and a detail page shows one item in full. Framer builds both around a collection.
- Collection list. It displays multiple items 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 layout, gap, columns and item limit, and configure "sorting, filtering, pagination, and empty states" as the collection grows (Framer Academy, "Create CMS collection lists"). This is your index, such as a blog homepage or a portfolio grid.
- CMS detail page. It is one reusable layout for a single item. 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"). Framer describes it as "one reusable layout for individual items in a collection." You design it once, and it renders each item's own field values. You can also place a second collection's list on a detail page, for 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?
Each plan caps collections and items, and add-ons raise the Pro caps. Re-check the table against Framer's live page before you commit content to a plan.
| Plan | CMS collections | CMS items | Entry price |
|---|---|---|---|
| Free | 10 collections (per the Free plan FAQ) | 1,000 pages total (not a CMS-item-specific cap) | $0 |
| Basic | 2 | 1,000 | $10/mo |
| Pro | 10 | 2,500 | $30/mo |
| Enterprise | Custom | Custom | Custom |
(Source: Framer, Pricing.) Framer's FAQ on that page gives the Pro ceiling with add-ons: "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." Add-on pricing on the same page is "$40 per 10" additional collections (to a 40 maximum) and "$20 per 10,000" additional items (to a 40,000 maximum).
The Free plan figures come from a separate FAQ answer: "Projects on the Free plan include access to 10 CMS collections, 1,000 pages, 5 MB file uploads, and one free locale to try."
How do I import and export CMS content in bulk?
Use two marketplace plugins published by Framer: CMS Export and CSV Import. CMS Export is listed as "by Framer" and lets you "export any CMS collection as a CSV file" (Framer Marketplace, "CMS Export"). CSV Import is also published by Framer and imports "CSV files into the CMS" with "automatic field mapping and validation" and a "built-in conflict resolution system" (Framer Marketplace, "CSV Import").
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"). Re-importing the same file with a matching slug updates existing items instead of duplicating them, so CSV works for bulk edits as well as a one-time migration.
Can AI add content to the CMS for me?
Yes. Framer's own agent can create a collection from a written description. Per 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").
This uses the same credit system as Framer's other AI features, so check Framer's pricing page for your plan's monthly credit allowance. Framer's official External Agents connection (covered 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, as an alternative to the CSV Import plugin's own interface.
Do I need the CMS, or is a static page enough?
A static page is enough when every piece of content is one-off, such as a single About page or pricing page. A collection adds complexity without benefit in that case.
The CMS earns its place when several items share the same shape: blog posts, job listings, portfolio pieces, testimonials. A detail-page template then means designing the layout once instead of once per item, and a collection list is an index that updates as you add items.
If the CMS is a deciding factor between Framer and Webflow, our Framer vs Webflow comparison covers how their CMS scale, plan gates and export paths differ. Framer has no code export, so a CMS-heavy Framer site has no documented way to move its content to a self-hosted alternative beyond the CSV export above.
What should I check before I plan a collection?
- List your repeating content types (posts, team members, products). Each is a candidate collection.
- Define the fields you need for each collection before creating items, since field types (text, image, reference and so on) decide what you can bind on the page.
- Decide whether each collection needs a list page, a detail page, or both.
- Compare your plan's collection and item caps with your real content volume. Basic stops at 1,000 items, and Pro's add-ons reach 40,000.
- If you migrate content in, match your CSV headers to your field names exactly and include a stable slug column.
- If you may ever leave Framer, remember that CSV export is the only documented content portability path.