How Do I Build a Portfolio in Webflow?

Webflow doesn't have a dedicated "portfolio" feature — most portfolio sites use a CMS Collection for projects, with one Collection page template that every project reuses. You design the layout once, and each new project becomes an item rather than a new page you build by hand. This guide covers how that structure works, what Webflow's free plan actually restricts if you want to start there, and how a Template Marketplace portfolio template fits in, sourced from Webflow's own help center, checked September 2026.

How does a CMS-driven project page actually work?

When you create a CMS Collection, Webflow generates a Collection page automatically. Its help center describes the mechanism directly: "When you create a Collection, Webflow automatically creates a blank Collection page — a dynamic template that powers individual pages for each Collection item (e.g., blog post, recipe, team member, etc.). All Collection pages share the same layout and design, so when you update the Collection page, you're updating the template for every item" (Webflow Help Center, "Structure and style Collection pages", checked September 2026). For a portfolio, that Collection is "Projects": one field set (title, cover image, description, gallery, client, year — whatever your work needs), one page layout, and every project you add becomes a live URL without a new page being built by hand.

To make that layout dynamic rather than static, you connect individual elements to Collection fields. Webflow's help center: "You can convert static elements you add into a dynamic elements by connecting them to a Collection field. Any option highlighted in purple or containing a purple icon above it in the Settings panel can be connected to a Collection field" (same source). A project's index page — the grid or list a visitor browses first — is a separate element called a Collection list, added to any page and pointed at the Projects Collection; Webflow's help center says to "use Collection lists to add dynamic content to any page on your site" (Webflow, "Collection list"), so updating or adding a project in the CMS automatically updates that index without editing the page itself.

One structural detail worth knowing before you build: Collection pages aren't directly clickable from a static page without that Collection list acting as the link source. Webflow's guide is specific: "Collection pages aren't available as link targets for static elements on static pages. To link to a Collection page from a static page, you'll need to add a Collection list" (same source). In practice this just means your homepage's project grid needs to be a Collection list, not a set of hand-placed buttons, if you want each one to route to its own project's page automatically.

What does the free Starter plan let me build?

Webflow's pricing page lists Starter, the free tier, with "Webflow.io domain," "Limited Webflow CMS," "2 static pages," "1 GB bandwidth," and "50 form submissions" (Webflow Pricing, checked September 2026). Two of those numbers matter most for a portfolio specifically:

• "Limited Webflow CMS." The pricing page doesn't state a specific collection or item cap for Starter on that page, and Webflow's own pages have given different CMS item-count figures for the same plan in the past — so this guide won't print a number here. What's clear is the direction: Starter's CMS access is limited, and Premium ($25/mo billed yearly) is the plan Webflow positions "For content-rich sites with robust CMS and traffic needs." A portfolio with more than a handful of projects should plan around Premium rather than assuming Starter's CMS will stretch.
• 2 static pages. This cap is separate from CMS items — it limits your hand-built pages (About, Contact, a homepage), not the number of projects a Collection can hold. A portfolio built mostly from CMS project pages can work within it, but you'll want Basic ($15/mo billed yearly, 300 static pages) the moment you need more than two non-CMS pages.

Starter also keeps a "Made in Webflow" badge on the published site with no way to remove it at that tier — our guide to Webflow's free plan covers the badge rule, the exact plan-by-plan feature table, and when Basic or Premium actually becomes necessary in more detail than fits here.

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

Webflow's Template Marketplace sells both free and paid portfolio templates, and starting from one creates an entirely new site in your Dashboard with the template's pages already built — it doesn't skin an existing project the way a WordPress theme applies to existing content. Webflow's help center draws that contrast explicitly: "Webflow's templates behave differently than Wordpress themes. The design and layout of a Webflow template will not automatically replace the design and layout of an existing site in your Workspace" (Webflow Help Center, "Webflow templates overview", checked September 2026).

The licensing difference between free and paid templates matters more for a portfolio than it might first seem, especially if you ever build client work under your own name and later want to reuse the same layout for someone else's project. Our Webflow templates guide covers the Free Template License versus the paid Single-Use License in full — the short version is that a paid template is licensed for one End Product, and reusing it for a second client requires buying it again.

Two limits from that same help article apply directly to a template-based portfolio:

• Page count. "If the template-based site has more than two pages, you will need to either add a paid Site plan to the template-based site, or purchase a paid Workspace plan." Most portfolio templates ship with well more than two pages (home, about, several projects), so budget for a paid plan the moment you pick one, not later.
• Bringing in existing content. A template doesn't reach out and import your old projects automatically — Webflow's guide notes you "migrate CMS Collection data or copy and paste elements from other sites in your Workspace" if you want to bring existing work into the new template-based site.

What should a portfolio actually include, structurally?

Beyond the CMS mechanics above, a few practical choices are worth deciding before you build:

• One project = one Collection item, with a consistent field set (title, year, role, cover image, a gallery or embedded media, and a short write-up). Consistency here is what makes the Collection page template actually reusable across every project.
• A Collection list for the index, sorted or filtered by category, year, or featured status if your work spans more than a few pieces.
• A parent folder for project URLs, if you want them under a subdirectory like /work/project-name rather than at the site root — Webflow's Collection page settings support setting a parent folder for exactly this.
• Publish settings per Collection, if you want to keep a project unpublished (a draft, or work you're not ready to show) without deleting it — the same Collection page settings include a toggle for whether that Collection's item pages publish at all.

Where does Figment fit in?

Not for the CMS-and-templates workflow described above — Figment doesn't have a CMS, a Collection concept, or a template marketplace. It publishes a website from a Figma design file through its Figma plugin, so a Figment-published portfolio is built by laying out each project frame in Figma rather than by populating CMS items. That fits a designer who wants full visual control over a small, fixed set of projects and is comfortable adding a new frame per project by hand; it isn't a fit if you want the add-an-item-and-the-index-updates-itself behavior that Webflow's CMS provides, or if you're already committed to Webflow's Designer and Collection structure. If you're weighing a Figma-first portfolio against a builder with a real CMS, our guide to Squarespace portfolio pages covers the equivalent structure on that platform — up to 60 projects, gallery blocks capped at 250 images, and page-level password protection — as a second comparison point.

Bottom line: A Webflow portfolio is, structurally, a CMS Collection called Projects with one Collection page template that every project reuses, plus a Collection list on your homepage that links out to each one. The free Starter plan can hold a small one together, but its "Limited Webflow CMS" and 2-page cap mean most real portfolios end up on Basic or Premium — and if you start from a Template Marketplace template instead of building from scratch, budget for a paid plan immediately, since Webflow's own rule kicks in the moment a template-based site has more than two pages.