Did Figma just kill Webflow and Framer with the launch of Figma Sites?

Less than a month after Figma sent a cease-and-desist letter to AI-coding startup Lovable, the design giant on Wednesday announced the launch of Figma Sites, a new feature that lets users publish responsive websites directly from the design canvas. No coding. No third-party handoffs. Just publish. The launch comes as doubts grow about whether Figma is starting to lose its relevance.

“Introducing Figma Sites. Take your designs straight to the web. With code and AI coming soon,” Figma said on its official page on X.

Introducing Figma Sites

Take your designs straight to the web. With code and AI coming soon.

Source: us#Config2025 pic.twitter.com/S7Gc3cyvPJ

— Figma (@figma) May 7, 2025

The rollout sparked a frenzy of posts, hot takes, and a wave of questions—one louder than the rest: Did Figma just kill Webflow and Framer?

The answer isn’t black and white, but the shake-up is big enough to make everyone pay attention.

Figma Sites: All-in-One or All-Overhyped?

Figma’s been the go-to design tool for years, and now it’s taking aim at the build stage too. With Sites, designers can ship live websites from their design files—complete with responsive layouts, team collaboration, and a new “content seat” setup for managing copy directly inside the editor.

More features are on the way. A CMS is “coming soon,” and AI tools for “code and beyond” are rumored to be next. That’s a lot of ambition packed into one feature, and it’s easy to see why some users are already ditching their Framer or Webflow setups.

One user on X wrote: “Figma Sites just made my workflow 10x smoother. Why would I need Framer now?” Another said: “Webflow’s worst nightmare.”

If you’re already living inside Figma, this new feature could mean fewer tools to juggle. That alone is a big deal for agencies, startups, and freelancers managing tight timelines.

Webflow: Deep Tools, Deep Roots

Webflow isn’t sweating just yet. With over 3.5 million users and adoption across 300,000 organizations, the platform is far more than a visual website builder. It’s packed with serious infrastructure—CMS, e-commerce, SEO tools, and integrations with Stripe, Zapier, Google Analytics, and more.

Figma Sites, as it stands today, is better suited for portfolios, landing pages, and lighter projects. Need a blog with dynamic content or custom code support? Webflow’s still the stronger play.

And here’s something Figma users might forget: Webflow already integrates with Figma through plugins and app connections. One Webflow fan tweeted, “Figma Sites is cute, but Webflow’s CMS and custom code options are untouchable. Good luck building a real site without them.”

In other words, Webflow hasn’t been sitting still. It just hasn’t been this loud about its moves.

Framer: The One with the Most to Lose

Framer, on the other hand, might be feeling the heat. Its whole value proposition has been centered around merging design with site publishing. And now Figma, the design tool it piggybacks on, wants to do that too.

Both platforms speak directly to the design crowd. Both support prototyping. Both offer responsive layouts. But Framer’s standout feature has always been its animation quality—fluid, high-end, and polished.

Framer users aren’t backing down yet. One wrote, “Figma Sites is playing catch-up. Framer’s been doing this for years, and its animations are unmatched.”

Still, Figma’s scale is a serious threat. Designers who already use Figma might wonder: Why export to Framer at all? If Figma’s roadmap delivers on CMS, AI, and performance, it could start to feel like Framer without the extra step. And in tech, friction kills.

Bigger Picture: Specialization vs. Staying Put

This isn’t just a product update—it’s Figma betting that users want less fragmentation. Instead of hopping between design, prototyping, and publishing tools, Figma wants everything to happen under one roof.

That convenience could come at a cost. If Figma Sites stretches itself too thin—half-baked CMS, premium pricing for content seats, or limitations around SEO or integrations—it might land in no-man’s land. Neither as flexible as Webflow nor as polished as Framer.

The community is split. One designer ranted, “Figma’s trying to monopolize design. Webflow and Framer are purpose-built; Sites feels like a shiny toy.” Another fired back: “Why learn three tools when Figma can do 80% of it? Most clients don’t need Webflow’s complexity.”

Well… 🥶#Config2025 pic.twitter.com/FCMt9BYWbk

— Atiqur Rahaman (@atiq31416) May 7, 2025

And that’s the tension. Will designers trade depth for speed? Or does the convenience of Figma’s all-in-one setup win out?

Worst-Case Scenario for the Competition

Now picture this: Figma rolls out its CMS in 2026 with AI-generated content, e-commerce features baked in, and pricing that undercuts the competition. With Adobe’s backing, that’s not a stretch.

Webflow might pivot more heavily toward enterprise. But Framer—smaller, leaner, and aiming for the same target audience—might find itself boxed in.

That’s not fear-mongering. That’s what platform consolidation looks like. We’ve seen it before.

So, Who’s Going Down?

Nobody’s dead. Not yet.

Webflow is still the go-to for complex, scalable websites. Framer still leads with animation and live previews. But Figma’s made its move—and it’s a strong one.

Figma Sites is convenient. And in a world where workflows matter as much as features, that’s dangerous territory for rivals.

The real question isn’t whether Figma can replace Webflow or Framer—it’s whether designers care enough about the extras to stick with specialized tools. Or if “good enough” inside Figma is the future.

You tell us: Is Figma Sites the new standard? Or are Webflow and Framer too deeply embedded to fall?