
Figma Sites doesn't have its own price: publishing a Site requires a Full seat on a paid Figma plan (Professional, Organization, or Enterprise), and Figma's free Starter plan doesn't have Sites yet. Beyond the seat gate, custom domains are governed by a beta policy that's explicitly tied to a 2025 date, and Figma's pricing FAQ and help pages don't state bandwidth or storage limits as specific numbers. This guide walks through what each plan actually gets you, sourced from Figma's pricing page and help center, checked September 2026.
Figma's own pricing FAQ states the gate plainly: "Sites is available on the Full seat for paid plans. Limited Sites experience on Starter is coming soon." That means two things worth being precise about. First, it's a seat requirement, not just a plan requirement — a Dev or Collab seat on the same paid plan doesn't unlock Sites publishing, the same way it doesn't unlock Figma Make publishing. Second, if you're on Figma's free Starter plan today, you don't yet have a way to publish a Site at all; the FAQ frames a "Limited Sites experience" for Starter as something still coming, not something live.
Figma's pricing page lists Full-seat prices on its annual billing view (checked September 2026):
| Plan | Full seat price | Custom domains for Sites |
|---|---|---|
| Starter (free) | $0 | Not yet — Sites isn't available on Starter |
| Professional | $16/mo | 10 |
| Organization | $55/mo | Unlimited |
| Enterprise | $90/mo | Unlimited |
Since the same Full seat also covers Figma Make, if your team already pays for a Full seat for design work, publishing a Site with it costs nothing beyond that seat price. If you're evaluating Sites specifically and don't otherwise need a Full seat, that $16-90/mo (depending on plan) is effectively what Sites costs you.
Figma's custom-domain help article gives the same figures as the pricing FAQ: Professional connects up to 10 custom domains, and Organization and Enterprise can connect as many as needed. That allowance isn't Sites-exclusive — it's shared with Figma Make, so a workspace running both products draws custom domains from one combined pool, not two separate ones. See Figma Make pricing for how that plays out from the Make side.
Here's where you need to read the date on the page, not just the headline claim. Figma's custom-domain article states, as of this writing: "Custom domains are free of charge through 2025." The same page adds: "These limits are subject to change after 2025." In September 2026, after the date named in its own text, the page still reads that way, with no visible update describing what happens now that 2025 has passed. Treat that as an unresolved, dated claim rather than an ongoing guarantee: check the page yourself before you plan a paid rollout around free custom domains.
Figma's separate pricing FAQ uses the same framing for bandwidth and storage: "During beta, custom domains, bandwidth, and storage are free of charge through 2025," followed by "You can purchase additional bandwidth or storage in early 2026." The same FAQ also says "We do not support purchasing additional bandwidth or storage at this time". Neither page states what a paid tier would cost, or what the current bandwidth and storage ceiling is in gigabytes. If your site is high-traffic or media-heavy, that absence is worth flagging to your team now rather than discovering it after a 2026 policy change.
No, at least not as a separate line item. Figma's Guide to Figma Sites CMS states the CMS is "Available on all plans" — meaning all plans that include Sites at all, so the same Full-seat gate above is the real cost, not an extra CMS tier. There is a size cap, though: Figma's Create a CMS collection article says "CMS currently has a limit of 200 items per collection while in beta." If you have more than 200 posts, products or case studies for one collection, plan around that limit before a large content migration (Framer's CMS publishes its own per-plan caps; see how the Framer CMS works for that comparison point).
No. Figma's pricing FAQ states this without qualification: "There are no limits on published websites." The constraint isn't how many Sites you publish, it's the Full seat needed to publish any of them at all.
If the seat-and-plan gate above is the blocker — you don't want to pay for a Full Figma seat just to publish a website — that's exactly the gap Figment's free tier is built for. Figment publishes a Figma design as a website through a Figma plugin: Free for unlimited sites on a figment.so subdomain with a badge, Pro at $49/mo ($39/mo billed yearly) for 10 custom domains, no badge, and HTML/CSS export to hand off or self-host, or Studio at $199/mo ($159/mo billed yearly) for 50 domains and priority support, with a 30-day free trial on either paid plan. Figment has no CMS and no interaction/animation engine to match Figma Sites' — Figma Sites vs Figment covers that full tradeoff, and Figma Sites vs Framer covers how Sites' pricing and CMS stack up against a dedicated site builder instead.
Bottom line: Figma Sites' real cost is whatever Full-seat price your plan already carries — $16, $55, or $90 a month, annual billing — with custom domains and bandwidth still riding on a beta policy tied to a 2025 date that's already passed as of this writing. Re-check Figma's pricing page and custom-domain article directly before you build a launch plan around either the seat gate or the free domain terms.