Figma Sites: What It Does, What It Costs And How It Compares To Framer And Webflow
Lily Roberts
Senior Marketing Strategist
10.10.2026
Short answer: Figma Sites is Figma’s built-in website builder. It lets you design responsive pages on the Figma canvas, add interactions, a CMS and React-based code layers, then publish straight to a figma.site address or your own domain. It is still labeled beta in October 2026 and comes with a paid Full seat (from $16 per month on the Professional plan). It works well for portfolios, landing pages and small marketing sites, but it still lacks redirects, custom 404 pages, nested URLs and ecommerce, so larger sites are usually better served by Framer, Webflow or WordPress.
Figma Sites is the closest Figma has come to closing the gap between a design file and a live website. Instead of handing a mockup to a developer or rebuilding it in a separate tool, a designer can lay out the pages, set breakpoints, connect content and hit publish from the same file. For teams that already live in Figma, that is a real shortcut. For teams that need a site to rank, migrate cleanly and scale, the picture is more mixed.
This guide covers what the Figma website builder does today, what it costs, where it falls short, and how it compares to Framer, Webflow and WordPress.
Figma Sites is Figma’s all-in-one tool for designing, prototyping and publishing websites. You work in a Sites file that behaves much like a Figma Design file, with web-specific additions.
Figma announced Sites at its Config conference in May 2025 and released it in open beta at that event. Publishing rolled out to users gradually over the following weeks. As of October 2026, both the Figma Sites product page and the Figma help center still label it beta. The name has not changed: it is still called Figma Sites, and it is separate from Figma Make, the prompt-to-app tool that can also publish to the web.
What You Actually Do In A Sites File
Design pages on a canvas. Each webpage is a frame, and frames pasted from Figma Design convert into responsive layouts.
Set breakpoints. You adjust the design for desktop, tablet and mobile widths, and auto layout handles much of the reflow.
Use prebuilt blocks and templates. Navigation, heroes and galleries come with auto layout configured.
Add interactions. Hover states, scroll effects, marquees, custom cursors and similar effects are applied from a panel rather than written in code.
Connect content and code. Bind CMS collections to layouts and add React code layers for anything the visual tools cannot do.
Availability, Plans And What It Costs
There is no separate Figma Sites pricing. You do not buy a site plan the way you would on Framer or Webflow. Instead, Sites is bundled into Figma’s seat-based pricing, and the seat you hold decides whether you can build and publish.
Figma’s help center says Sites is available on all paid plans and requires edit access to the file. Figma’s pricing page lists Sites as a beta feature available on Full seats. The Education plan includes one published site, subject to bandwidth limits. Collab and Dev seats are not the seats for building and publishing sites, so budget for a Full seat for anyone who will edit and publish.
Figma plan
Full seat price (per month)
Figma Sites access
Custom domains
Starter (free)
$0
Limited access to Figma products; Sites publishing is listed for paid plans
Not available
Professional
$16 (billed annually)
Full seat can design and publish
Up to 10
Organization
$55 (billed annually)
Full seat, plus internal-only publishing
Unlimited
Enterprise
$90 (billed annually)
Full seat, plus internal-only publishing
Unlimited
Education
Free for eligible users
One published site, bandwidth limited
Check Figma’s terms
Figures come from Figma’s pricing page and help center in October 2026. Figma restructured its seats in 2025 and has adjusted terms since, so confirm current prices before you budget. For a deeper breakdown of seats, AI credits and plan differences, see our Figma pricing guide.
What The Seat Price Really Covers
A designer who already holds a Full seat gets Sites with no extra line item, plus a monthly AI credit allowance (3,000 credits on Professional) for generating code layers.
Two caveats. First, Figma said custom domains were free through 2025 and that limits and pricing could change after that, so check the current help center terms for domains, bandwidth and storage. Second, cost scales with editors, not with sites or traffic, the opposite of how Framer and Webflow charge.
Publishing And Custom Domains
Publishing is where Figma Sites differs most from a normal Figma file. When you publish, Figma includes every webpage on the canvas in the live site, including dynamic subpages generated by a CMS page. Canvas changes go live only when you publish an update, and you can republish a previous version.
The figma.site Subdomain
Every published site gets a randomly generated figma.site subdomain made of three words, in the format hut-grid-glade.figma.site. Figma’s publishing documentation notes that you cannot currently change that assigned subdomain. A business site will want a custom domain.
Connecting A Custom Domain
Publish the site at least once so it has a figma.site address.
Open the site settings and add your domain (apex domain or subdomain).
Add the TXT record (for verification) and the CNAME record (for routing) that Figma gives you at your DNS provider.
If you use Cloudflare, set the proxy status to DNS only. If your apex domain has existing AAAA records, you may need to remove them.
Wait for the SSL certificate. Figma’s custom domain guide says this usually takes about 15 minutes and can take up to 30.
Each site can connect to one custom domain at a time. Professional plans allow up to 10 custom domains across the team, while Organization and Enterprise allow unlimited domains. That limit is shared with Figma Make, so if your team also publishes Make prototypes on custom domains, they draw from the same pool.
Hosting And Access Control
Figma hosts published sites on AWS in the United States, with domain and routing served through Cloudflare. You cannot export a site’s code for external hosting, so the site lives on Figma’s infrastructure for as long as you keep it. Password protection is available on paid plans, sitewide or per page. Organization and Enterprise plans can also restrict a site to logged-in members.
The Figma Sites CMS
The Figma Sites CMS was not part of the original beta. It arrived later, after a Figma product manager said in September 2025 that CMS and blog support were on the way. The model will feel familiar to Framer and Webflow users:
Collections are sets of fields and items grouped by topic. Figma compares them to a spreadsheet of your content. You can create one from scratch, from a sample template or by importing a CSV.
CMS pages act as templates. Each item in a collection gets its own URL, and its content is inserted into the page dynamically.
CMS lists are repeating blocks that display several items from one collection on a page, such as a blog index or a team grid.
Fields connect to design layers through a Connect view, so a title field drives a heading, an image field drives an image, and so on.
Content is edited in a CMS panel in the right sidebar, and Figma’s pricing page describes a dedicated UI for managing and updating content inside Sites. Figma positions it for blogs, portfolios, catalogs and events pages.
What Figma Does Not Document Yet
Figma’s CMS documentation does not publish item limits, a full list of field types, or detailed permissions for content-only editors. Framer and Webflow both publish item caps per plan. If you plan to run a blog with hundreds of posts or a catalog with thousands of items, test the CMS with real volumes before you commit, and ask Figma support about limits for your plan.
Code Layers And Interactions
Interactions in Figma Sites come in two tiers. The first is the no-code tier: effects you apply from the properties panel, such as hover states, scroll-triggered animations, marquee scrolling and custom cursors. The second tier is code layers.
Figma introduced code layers for Sites in June 2025. A code layer is an element on the canvas that is backed by custom React code. Figma’s help center says code layers support React, TypeScript and Tailwind CSS, and Figma’s launch post lists examples like flyouts, dropdowns, shaders and maps. You can create one in three ways:
Convert an existing design component into a code layer.
Describe what you want in the AI chat (the same engine as Figma Make) and let it generate the code.
Write or edit the code yourself in Figma’s built-in code editor.
Code layers can expose editable properties (strings, numbers and component references), so a designer can change behavior without touching the code. They can be turned into reusable components and can import npm packages such as motion and @react-three/fiber for animation and 3D work. At Config in June 2026, Figma also showed code layers moving onto the wider design canvas, but that broader rollout was still listed as an upcoming beta with a waitlist at the time of writing.
Two cautions. Figma warns never to put API keys in code layers, because they can be discovered and misused. And AI-generated code still needs review for accessibility and page weight, especially with shaders and 3D.
SEO And Performance Controls
Figma Sites covers the SEO basics in its website settings. According to the help center, you can set:
Title and meta description, sitewide and per page.
Noindex, to exclude the whole site or individual pages from search results.
Social sharing image (1200 by 630 pixels recommended), sitewide and per page.
Favicon.
Language code, sitewide and per page.
Google Analytics ID (sitewide).
Custom code in the head and body tags, useful for tag managers, verification tags and schema markup.
A cookie consent banner on paid plans.
That is enough for a portfolio or a campaign page. It is thinner than what SEO teams expect from a site that has to earn organic traffic. Figma’s settings documentation does not mention controls for canonical URLs, robots.txt or sitemap configuration, and the gaps show up in the community forum. In August 2026, a user reported pages being crawled but not indexed, a robots.txt returning a 404 and sitemap detection problems in Google Search Console, and the thread was escalated to Figma support without a public fix.
On performance, Figma serves sites through Cloudflare, which helps with delivery. Figma does not publish documentation on the structure of the HTML it generates, so you cannot assess semantic markup or accessibility from a primary source in advance. Publish a test page and run it through Lighthouse and an accessibility checker before launch.
Known Limitations In 2026
Figma Sites has improved since launch, with custom domains, a cookie banner and the CMS all added during the beta. Several gaps remain. Here is what we could confirm from Figma’s own documentation and staff replies on the Figma forum as of October 2026.
Still in beta. Figma labels Sites beta on its product page, pricing page and help center. Features, limits and pricing can still change.
No custom 404 page or catch-all redirect. In August 2026, Figma community support confirmed there is no way to set a custom 404 page or catch-all redirect, called it a known gap and gave no timeline.
No URL redirects. A long-running feature request for redirects remained open with no staff confirmation of a fix in 2026. This is a serious issue when migrating an existing site, because old URLs lose their link equity without 301 redirects.
Flat URL structure. Users have reported that nested paths such as /legal/privacy-policy are not supported for static pages.
No code export. You cannot export the site for hosting elsewhere. Leaving Figma Sites means rebuilding.
No native ecommerce. There is no cart, checkout or product catalog with payments. You would need a third-party embed.
Fixed figma.site subdomain. The assigned subdomain cannot be changed, so a custom domain is the only way to get a clean address.
Limited CMS documentation. Item limits, field types and editor permissions are not published.
Analytics is basic. Google Analytics is sitewide only, and a forum user reported trouble tracking internal page navigation with GA4 and Google Tag Manager.
Figma Sites Vs Framer Vs Webflow Vs WordPress
The most common question we see is figma sites vs framer, since both target designers who want to publish without a developer. The table below only lists capabilities we could verify on each vendor’s own pages in October 2026. Prices and limits change often, so treat them as a starting point.
Capability
Figma Sites
Framer
Webflow
WordPress (self-hosted)
Status
Beta
Generally available
Generally available
Generally available, open source
Pricing model
Per Full seat (from $16 per month)
Per site plan (Basic $10, Pro $30 per month) plus extra editors
Per site plan (Basic $15, Premium $25 per month billed yearly) plus workspace seats
Free software; you pay for hosting, theme and plugins
Custom domain
Paid plans (10 on Professional)
Paid plans
Paid site plans
Yes
CMS
Yes, collections and CMS pages; limits not published
Yes; 1,000 to 2,500 items depending on plan
Yes on Premium (20,000 items); not on Basic
Yes, native posts and pages plus custom post types
301 redirects
Not supported
Pro plan and up
Premium plan and up
Yes, via plugins or server
Custom code
React code layers plus head and body code
Code components and custom code
Code components on Premium; custom code on workspace plans
Full access to theme and plugin code
Native ecommerce
No
Not listed on pricing page
Yes, from $29 per month billed yearly
Yes, via WooCommerce
Localization
Language code setting only
Paid add-on per locale
Localize add-on on Premium
Via plugins
Staging
Preview before publish
Pro plan and up
Staging sites on workspace plans
Via host or plugins
Code export
No
No
Core workspace plan and up
You own all files
Design source
Native Figma files and libraries
Own canvas; imports from Figma
Own designer; Figma import tools
Theme or page builder; built from Figma by a developer
How To Read The Comparison
Figma Sites wins on one thing: zero translation between design and site. If your design system is in Figma and the site is small, nothing is faster. It loses on SEO depth, redirects, scale and portability.
Framer is the closest competitor and the more mature choice for marketing sites today. It has published CMS limits, redirects, staging and localization. Our Framer pricing guide breaks down the plans and add-ons.
Webflow is the pick when you need a larger CMS, native ecommerce, a mature redirect manager and structured publishing workflows for a marketing team. If you are weighing those two, read our Framer vs Webflow comparison.
WordPress is the most flexible and portable: you own the code and data, and SEO tooling is mature. The tradeoff is that someone has to build the theme from your Figma files and maintain it.
Who Should Use It And When To Hire A Build Team
Figma Sites Is A Good Fit For
Designer and studio portfolios where the work itself is the content.
Event pages, launch pages and campaign microsites with a short life span.
Internal sites, such as design system documentation or team hubs, using internal-only publishing on Organization or Enterprise.
Clickable, high-fidelity prototypes that need a real URL for user testing or stakeholder review.
Small brochure sites (a handful of pages) for teams that already pay for Full seats and do not depend on organic search.
Look Elsewhere, Or Get Help, When
You are migrating an existing site. Without redirects, you risk losing rankings and backlinks tied to old URLs.
Organic search is a core channel. You need dependable control over robots.txt, sitemaps, canonicals and structured data.
You sell online. You need native ecommerce, which points to Webflow, WordPress with WooCommerce or a dedicated commerce platform.
Marketing needs to ship pages weekly. Publishing workflows, roles and content editor seats are more developed on Framer and Webflow.
You need portability. If leaving the platform must not mean a rebuild, WordPress or Webflow with code export is safer.
If your team designs in Figma but needs a production marketing site, a specialist build partner is usually the faster route. For design-led marketing sites on Framer, compare the studios in our list of top Framer agencies and experts. If you need ecommerce, a larger CMS or enterprise publishing workflows, our roundup of top Webflow agencies is a good starting point. And if you want full ownership of the code with WordPress, see the top Figma to WordPress development agencies, which specialize in turning Figma files into custom themes.
Frequently Asked Questions
Is Figma Sites free?
Not for publishing a business site. Figma’s help center lists Sites as available on paid plans, and the pricing page ties it to Full seats, starting at $16 per month on Professional. Education users can publish one site with bandwidth limits.
How does Figma Sites pricing compare to Framer and Webflow?
Figma Sites pricing is per editor seat, not per site, so one Full seat can publish several sites within the domain limit. Framer and Webflow charge per site plan and add costs for extra editors. For one designer running a few small sites, Figma is often cheaper.
Does Figma Sites have a CMS?
Yes. The Figma Sites CMS supports collections, CMS pages that generate a URL per item, and CMS lists that display items on a page. You can import content from a CSV. Figma has not published item limits or a full list of field types, so test with real content volumes.
Can I publish a website from Figma Design files?
You can publish a website from Figma by copying frames from Figma Design into a Figma Sites file, where they convert into responsive web layouts. Publishing happens from the Sites file, not from a standard design file.
Is Figma Sites better than Framer?
On figma sites vs framer, Figma Sites is better if your priority is staying inside Figma with no rebuild. Framer is better for most production marketing sites in 2026 because it supports redirects, staging, localization and has published CMS limits.
Can I export code from Figma Sites?
No. Figma’s help center states that exporting a site’s code for external publishing is not currently possible. If you need figma to website output you can host anywhere, a developer build on WordPress or Webflow with code export is the usual route.
Is Figma Sites good for SEO?
It covers the basics: page titles, meta descriptions, noindex, social images, language codes and custom head code. It lacks redirects and custom 404 pages, and users have reported robots.txt and indexing issues in 2026.
The Short Version
Figma Sites turns a Figma file into a live, responsive website, with a CMS, React code layers, basic SEO settings and custom domains on paid plans. It is included with a Full seat (from $16 per month on Professional) and is still in beta in October 2026. It is a strong choice for portfolios, launch pages, internal sites and small brochure sites built by teams that already work in Figma.
For sites that must rank, migrate cleanly, sell online or scale, the missing redirects, custom 404 pages, nested URLs and code export still matter. In those cases Framer, Webflow or WordPress is the safer platform, and a specialist build team can take your Figma files to production faster than a long trial and error with a beta tool.
