How Do I Build a Portfolio in Framer?

A Framer portfolio is usually built as a CMS collection called Projects, with one detail-page layout that every project reuses — you design the page once, and each new project becomes an item rather than a page you build by hand. Framer's free plan can hold a real version of this structure before you pay anything. This guide covers how the CMS pieces fit together, what the free plan actually restricts, and how a Marketplace portfolio template changes the starting point, sourced from Framer's own Academy lessons, help center, and pricing page, checked September 2026.

How does a CMS-driven project page work in Framer?

Framer's Academy gives the plain building blocks: "A collection groups related content such as articles, projects, or team members," "Each item is one record," and "Fields define the text, images, dates, links, and other values every record can contain" (Framer Academy, "Build your Framer CMS with the Agent", checked September 2026). For a portfolio, the collection is "Projects": fields for title, cover image, a gallery, client or category, and a short description, however your work needs to be described.

Framer builds two separate page types around that collection, and a portfolio uses both:

• A CMS detail page is the reusable layout for one project. Framer's Academy: "A CMS detail page is one reusable layout for individual items in a collection." 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). Design it once with your project's fields bound to it, and it renders with different content for every project you add.
• A collection list is your index — the grid or list a visitor sees first. Framer's Academy walks through building one in steps: "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 finally "configure sorting, filtering, pagination, and empty states so the page remains useful as the collection grows" (Framer Academy, "Create CMS collection lists", checked September 2026).

Framer's own agent can also populate the collection directly from a written description rather than adding items by hand: "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). That's a starting point for structure, not a replacement for writing your own project descriptions and choosing your own images.

What does Framer's free plan actually let me build?

Framer's pricing page FAQ states the free-plan specifics in one line: "Projects on the Free plan include access to 10 CMS collections, 1,000 pages, 5 MB file uploads, and one free locale to try" (Framer, Pricing, checked September 2026). For a portfolio, that's a genuinely workable starting point — 10 collections is more than enough if you only need one (Projects), and 1,000 pages covers a project count far beyond what most portfolios ever hold. Framer's own framing of the Free plan backs this up: it's "ideal for non-commercial use," for exploring Framer, using it as a design tool, or creating templates — not a stripped trial.

What Free doesn't include is specific:

• No custom domain. "To connect a custom domain, you'll need to upgrade to a paid plan" (same source). A free portfolio publishes only to a framer.app address.
• A "Made in Framer" badge, removed only by connecting a custom domain (which itself requires a paid plan) or upgrading your subscription.
• A 5 MB per-file upload cap, which is fine for most web-sized images but tight for large photography or video files a visual portfolio might want to show.

Our guide to Framer's free plan covers the full feature table and what specifically changes on Basic versus Pro if you're deciding whether to launch a real portfolio on Free or budget for a paid plan from the start.

What are the CMS limits once I outgrow Free?

Framer's pricing page states specific collection and item caps by plan:

(Source: Framer, Pricing, checked September 2026.) Basic actually caps collections tighter than Free does — only 2 — which matters if your portfolio grows beyond one collection type (say, adding a separate "Clients" or "Press" collection alongside Projects). Pro's caps can extend further with paid add-ons; Framer's FAQ states Pro can reach "up to 40,000 CMS items, 40 CMS collections... on the Pro plan" with add-ons priced separately. Our guide to the Framer CMS covers the full add-on pricing and the CSV import/export tools if you're migrating existing project write-ups in bulk.

Should I start from a portfolio template instead of building from scratch?

Framer's Marketplace sells and gives away complete portfolio projects built by independent creators, and Framer itself doesn't process the transaction for paid ones. Its help center: "Framer templates are complete website projects designed by creators using Framer. They range from simple landing pages to complex websites tailored for specific industries and use cases" (Framer Help, "Using templates", checked September 2026). The Marketplace's own portfolio category describes what it's built around: "Portfolio website templates that put your best work first, with room for case studies, experience, and the story behind what you do," built "around case studies, galleries, and the work you want seen first" (Framer Marketplace, Portfolio category, checked September 2026).

Getting a copy works differently depending on price. A free template uses a one-click "Use for Free" button and lands in your account immediately; a paid template routes you to the creator's own checkout, and Framer's help center is explicit that "Framer does not process template payments or manage refunds. All purchases are handled directly by the template creator" (same source). Either way, the result is a fully editable copy in your own workspace — "you can edit its content, styling, layout, and components just like any other Framer project" (same source).

The license terms differ by price, and matter if you'd reuse the same design for a second project. Framer's Community Terms state that free-template content can go into commercial work, including client work, but "shall not... Resell, redistribute, sublicense, share, publish, or make the Free Content available as a standalone asset" (Framer, Community Terms, checked September 2026). A paid template's license is narrower: it covers "creating one (1) end product or project," so reusing a single paid purchase across two separate portfolios or client sites isn't covered — you'd need a second license. Our guide to Framer templates covers the full license comparison and the remix mechanics in detail.

Where does Figment fit in?

Not for the CMS-and-Marketplace workflow above — Figment has no CMS, no collections, and no template marketplace of its own. It publishes a website from a Figma design file through its Figma plugin, so a Figment portfolio means laying out each project as its own frame in Figma rather than populating a collection. That's a fit if you want full visual control over a small, fixed set of projects and are comfortable adding a new Figma frame per project by hand; it's not a fit if you want the add-an-item-and-the-index-updates-itself behavior Framer's CMS provides, or if you're already committed to designing inside Framer's canvas. For the equivalent structure on the other major design-first builder, our guide to Webflow portfolios covers Webflow's CMS Collection Pages, its own free-plan limits, and its Template Marketplace as a second comparison point.

Bottom line: A Framer portfolio is, structurally, a CMS collection called Projects with one detail-page layout every project reuses, plus a collection list for the index page a visitor browses first. Framer's free plan — 10 collections, 1,000 pages, one framer.app address — is enough to build and test a real one, and the only two things it withholds that matter for a live portfolio are a custom domain and badge removal. Starting from a Marketplace template instead changes the license terms you're working under, not the underlying CMS structure.