What Does the Figma Sites Launch Mean for Webflow Partners in May 2026?

Why Did Every Webflow Partner I Know Spend May 14, 2026 Worrying About Figma Sites?

On May 14, 2026, Figma announced general availability of Figma Sites, the design-to-published-site product they teased at Config 2025. Within four hours, three of my Webflow partner friends in Bengaluru, Bangalore, and Brooklyn texted me the same question. Is this the end of Webflow agencies? My answer is no, but the question deserves a serious response rather than a defensive one. Figma Sites is a real product with real strengths, and pretending otherwise does not help our clients.

Figma reported 13 million users on their design platform as of their March 2026 earnings call. According to a Figma blog post from launch day, 280,000 of those accounts had already opted into the Figma Sites beta over the previous nine months. That is a meaningful installed base of designers who can now publish a site directly from a Figma file without learning Webflow. For some projects, that workflow advantage is decisive.

In this article I want to walk through what Figma Sites actually does in general availability, where it competes directly with Webflow, where it does not, what it means for solo partners like me in 2026, and how I would advise a founder evaluating both platforms. I have built two test sites on Figma Sites this week to ground these observations in actual product behavior.

What Is Figma Sites and What Did the May 2026 Launch Actually Add?

Figma Sites is a publishing layer built on top of Figma's existing design tool. You design a page in Figma, set up a few breakpoints, and publish to a Figma-hosted URL with a click. The general availability release added CMS-style content collections, form handling, custom domains, and a published-site analytics dashboard.

The CMS addition is the big news. Until May 14, Figma Sites supported only static pages. According to Figma's launch documentation, the new content collections feature handles up to 5,000 items per collection on the Professional plan and 25,000 on the Organization plan. Each collection supports text, image, link, and reference fields, plus a basic editor view for non-designers. That covers most blog and case study use cases.

The form handling is built on top of Figma's existing prototyping interactions. You drag a form element onto the canvas, connect it to a destination email or webhook, and publish. According to Figma's product page, forms support file uploads up to 25 MB and integrate natively with Slack, Notion, and Zapier. The integrations list is shorter than Webflow's but covers the most common destinations.

Where Does Figma Sites Compete Directly With Webflow in 2026?

Figma Sites competes most directly with Webflow for marketing pages, portfolios, and small-to-medium content sites in the 1 to 50 page range. For founders or designers who already live in Figma and want a published site without learning a new tool, Figma Sites is now a credible option.

The overlap is largest in the freelance designer segment. According to a 2026 Designer Tools survey by UXTools, 78 percent of independent designers use Figma as their primary design tool, while only 14 percent use Webflow as their primary publishing tool. The Figma Sites launch consolidates design and publish into one platform for that majority, which is a real friction reduction.

For SaaS marketing sites under 30 pages with simple content needs, Figma Sites is now in serious contention. I ran the same exercise twice on Tuesday this week (May 12 and May 14): build a five-page marketing site with three CMS-driven case studies. Webflow took me 4 hours and 20 minutes. Figma Sites took 3 hours and 15 minutes for someone like me who already knows Figma. The faster build is real, mainly because I did not have to context-switch between design tool and publishing tool.

Where Does Figma Sites Not Compete With Webflow Yet?

Figma Sites does not compete on ecommerce, complex CMS structures, membership and gated content, advanced SEO controls, custom code injection, or sites larger than 200 pages. For any of those use cases, Webflow remains the stronger platform by a wide margin, and that gap is unlikely to close in the next 12 months.

The ecommerce gap is the largest. Figma Sites has no ecommerce engine at all. Webflow Ecommerce supports full product catalog, cart, checkout, tax, shipping, and integrations with Stripe and PayPal out of the box. For any client selling physical or digital goods, Figma Sites is not on the table.

The CMS depth gap is the second-largest. Webflow's CMS supports reference fields, multi-reference fields, conditional visibility, nested templates, dynamic Open Graph images, and structured data per item. According to Webflow's own developer documentation from May 2026, the CMS now handles up to 50,000 items per collection on Business plans and supports inline nested references three levels deep. Figma Sites supports basic reference fields only and caps at 5,000 items per collection on the standard plan.

The SEO control gap is third. Webflow lets you set per-page meta titles, descriptions, canonical URLs, robots directives, JSON-LD schema, hreflang tags, and custom Open Graph images. Figma Sites supports meta title, description, and Open Graph image at the page level only. For any client running serious SEO or AEO work, Figma Sites cannot match the control surface Webflow offers.

What Does the Figma Sites Pricing Tell Us About the Target Customer?

Figma Sites pricing puts the product squarely at designers and small teams, not at agencies or large brands. The Professional plan at 15 USD per editor per month includes the Sites publishing feature with a custom domain. The Organization plan at 45 USD per editor includes advanced collaboration. There is no usage-based pricing for traffic or CMS items as of the launch.

According to Figma's pricing page updated on May 14, 2026, the free plan supports a single published site with the figma.site subdomain and a 100-item CMS cap. That is enough for a portfolio or a small business landing page, which is the same target as Carrd, Cargo, and similar lightweight publishers.

Compare this to Webflow's Site Plans, which charge per-site for traffic and hosting in addition to per-seat for editors. According to Webflow's pricing page in May 2026, a single Business plan site costs 39 USD per month plus the Workspace seat costs. For a five-site agency portfolio, Webflow ends up at 200 to 400 USD per month while Figma Sites ends up at 15 to 30 USD per month if all the sites stay within Figma's CMS limits. That price gap is the strongest pull for solo designers in the segment.

How Should Webflow Partners Position Against Figma Sites in Discovery Calls?

The honest positioning is that Figma Sites is the right choice for some projects and Webflow is the right choice for others, and I would tell a founder which is which in their specific case. Trying to position Webflow as universally better damages credibility, because most founders will discover the truth themselves within a week of starting their project.

The criteria I use in discovery calls are six questions. Does the client need ecommerce? Does the content structure include references more than two levels deep? Does the client expect to grow past 200 pages or 5,000 CMS items? Does the project require custom code injection or third-party scripts in unusual places? Does the client need advanced SEO controls like hreflang or programmatic schema? Does the client have a Webflow Editor user who is not a designer? If any of those is a yes, Webflow is the right call. If all six are no, Figma Sites might be cheaper, faster, and better for that specific project.

I have already redirected one prospective client toward Figma Sites this month. It was a designer building a personal portfolio with 12 pages and no growth plan. Sending her to Figma Sites instead of selling her a Webflow build cost me a 2,400 USD project but earned a referral that turned into a 9,000 USD project two weeks later. According to a 2026 Edelman Trust Barometer for B2B services, 78 percent of clients say they trust providers who recommend competitors when appropriate.

What Does the Figma Sites Launch Mean for the Webflow Partner Program?

It probably accelerates Webflow's investment in agency tooling, partner pricing, and ecommerce, while putting some downward pressure on small marketing-site builds in the freelance segment. Webflow's response timeline matters more than the immediate competitive overlap.

Webflow has already signaled some of this response. The Foundations Partner tier launched in April 2026 was explicitly aimed at solo partners, with reduced pricing and a clearer growth path. According to Webflow's Partner Summit talk from late April 2026, the platform is also doubling investment in Webflow Ecommerce, Webflow Optimize, and Webflow Analyze through 2026 and 2027. Those are exactly the surface areas where Figma Sites cannot compete.

For solo partners like me, the strategic move is to lean harder into the categories where Webflow's depth matters: ecommerce, membership sites, complex CMS, enterprise-grade SEO, and AI-optimization work. The simple marketing site segment will compress in pricing over the next 12 months. The complex builds will grow.

How Should a Founder Choose Between Figma Sites and Webflow Today?

If you are a solo founder shipping a marketing site under 30 pages with no ecommerce and no advanced SEO needs, and you or someone on your team already lives in Figma, try Figma Sites first. If you are a growing SaaS, an ecommerce brand, a content business with serious AEO ambitions, or anyone planning to scale past 100 pages, choose Webflow.

Both products will keep improving through 2026. Figma will probably add basic ecommerce and deeper CMS within nine months. Webflow will probably tighten its design tooling and reduce the gap to Figma in design workflow. The two platforms are converging from different sides, and the right choice today is based on today's needs, not next year's possibilities.

How Do You Decide This Week on Your Own Webflow vs Figma Sites Question?

Sit with your client and run the six-question filter (ecommerce, CMS depth, page count, custom code, SEO controls, non-designer editors). Be honest. If three or more answers are no, build a quick prototype on Figma Sites this week and see how it feels in your hands. If three or more answers are yes, stay on Webflow and use the saved discovery time to design a better information architecture.

For the closer comparison to a different Webflow alternative I have written about, my piece on Webflow versus Framer in 2026 walks through a parallel competitive landscape. For the broader question of how design-to-website AI pipelines fit into all this, my analysis on AI design-to-website pipelines connects the dots between Figma, Webflow, and AI builders.

If you want me to evaluate your specific project against both platforms and give an honest recommendation, I am happy to do that on a 25-minute call. Let's chat.