But here’s the thing: the version we’ve seen so far?
It’s a bad start for a great idea.

That doesn’t mean it should be dismissed. It just means we’re watching the beginning of something that could change how we work—if the right steps follow.

The Vision Is Exciting (Even If the Execution Isn't)

Figma Sites offers a way to turn your design files into live websites. Instantly. Without leaving the canvas. On paper, this is everything we want: less context-switching, faster iterations, tighter design-to-dev loops.

But in practice? It’s clunky. The performance isn't there. The sites rely on JavaScript rendering that bloats the DOM and reduces speed, and once they’re published, they’re nowhere near as editable as what you’d expect from tools like Framer or Webflow.

As someone who’s worked in Framer for a while now, the contrast is clear. Framer feels polished, fast, and surprisingly flexible—even if it sometimes leans too much into templates. Its UI mirrors Figma closely, making the transition between design and development nearly seamless. The community around it? Active, creative, and generous with resources.

Figma Sites, by comparison, feels like a private beta that accidentally went live.

Why It Still Might Win

Despite its rough start, I’m not writing Figma Sites off. In fact, I’m excited about its future. Why?

Because Figma has a track record of playing the long game—and doing it well. If they commit to evolving Sites with the same pace and intention that Framer does with its updates, they might actually outrun their competitors.

But it’s not just about updates or interface parity. The real wildcard is something else Figma announced at Config this year: Figma Make.

This AI tool is designed to let you generate fully functioning custom code components using a couple of prompts. It’s still new, but if it delivers on its promise, it could render plugin libraries and even communities somewhat obsolete. Imagine asking, “Make me a responsive testimonials carousel,” and getting actual working code components—without diving into a tutorial rabbit hole or browsing forums.

That kind of integration, paired with design and publish capabilities, would be a serious threat to every no-code builder in the market.

What's Missing: CMS, Control, and Confidence

There are still some dealbreakers, though.

The biggest one? CMS.
Right now, Figma Sites doesn’t offer a real content management system. It’s more like a "one-pager maker" than a serious publishing platform. And if you're building anything beyond a portfolio or a simple product page, CMS flexibility matters.

Framer recently made huge improvements to their CMS tables, and Webflow’s CMS is still the gold standard for visual builders. Until Figma catches up, Sites is simply not viable for client projects that require even basic structured content.

On top of that, control is limited. Want to tweak SEO tags or page speed? Good luck. Sites are mostly locked down, and customization beyond the initial design is minimal. For most client-facing work, that’s a hard pass.

So... Should You Use Figma Sites Right Now?

In short: not for production work.

Performance issues alone make it risky to use for anything beyond internal testing. And without a strong CMS or better developer handoff tools, it’s hard to see where it fits into a pro team’s workflow today.

But should you try it out anyway? Yes.

There’s real potential here, and it’s worth getting familiar with the tool while it’s still evolving. If Figma Sites becomes what it’s trying to be, we could be looking at a future where we move directly from design to deployment without touching another tool.

And that future is one worth preparing for.

Final Thoughts: This Isn’t the End of Framer or Webflow—Yet

It’s too early to say whether Figma Sites will dethrone the platforms that currently dominate the no-code space. Framer is beloved for good reasons. Webflow is still powerful and flexible in ways others can’t yet match.

But this is the beginning of a new chapter.

If Figma continues investing in Sites—and especially in Make—we might see a major consolidation of design, development, and deployment inside a single platform. That’s huge.

Until then, it’s a "watch and wait" moment for most of us.

Want a Team That Builds With the Right Tools—At the Right Time?

At Behoove, we don’t just follow trends—we test, break, build, and adapt them. Whether you're looking to prototype fast or launch something real, we help brands choose the best platforms for their stage, team, and goals.

Curious about whether Framer, Webflow, or even Figma Sites is right for your next project?
Let’s talk it through. Get in touch →