Figma Sites Just Dropped, Should Framer Be Worried?

So… Figma just dropped a site builder.

Yep, you can now design a page and hit “Publish” in the same tool. No more exporting. No more copy-pasting into something else. It’s got breakpoints, components, hover effects, a few starter templates. Basically, it’s trying to be Framer. Or Webflow. Or both.

Let’s break down what this means, and whether you should even care.

What Is Figma Sites?

Figma Sites is a brand-new site builder, built right into Figma. It’s designed to let you ship websites from inside the tool you already design in.

What you can do today:

• Start from an existing Figma design

• Add responsive breakpoints with multi-edit support

• Use components from your design system

• Set hover and pressed states, scroll transforms, and parallax

• Connect to a custom domain

• Publish fully responsive live sites

• Use templates and common blocks like navs, hero sections, and image galleries

It’s like adding a publish button to Figma.

Coming Soon in Figma Sites

Here’s what Figma announced but hasn’t launched yet (yes, they’re already building it out):

• CMS: Create collections, fields, and inline editors right in the canvas

• Code Layers: Add React components directly to your site

• AI App Builder (Figma Make): Use prompts to generate interactions or animations

• Componentized Code: Turn code layers into shareable components

• Advanced Interactions: Smart animate, draggable lists, scroll effects, etc.

Basically, Figma's aiming to turn design production into a single, fluid flow from portfolio sites to full landing pages.

What’s Still Missing

Day 1 of a new builder means…gaps!

• No plugin system yet

• No analytics or tracking integrations

• No localization tools

• No built-in SEO controls beyond titles/meta

• No password protection or staging

• Interactions still feel a bit… lets say static

• Custom fonts and overflow behavior = still buggy

Figma clearly nailed design and collaboration, but publishing and scaling? Framer’s still winning.

Who Should Use Figma Sites?

This is best for:

• Designers who already live inside Figma

• Solo makers spinning up personal sites or one-pagers

• Teams who don’t want to leave Figma or touch code

• Building a simple personal/portfolio site

But if you’re working with a dev team, need dynamic content, or are building at scale, or really anything more complex! Framer still wins.

Figma vs Framer: Tool breakdown

Let’s be real: Figma Sites looks a lot like Framer V1.

But here’s the breakdown:

Framer Wins On:

• Powerful CMS with reference fields

• Plugin ecosystem (FramerForms, Frameship, Thenty…)

• Scalable workflows (localization, analytics, staging)

• Interactive components and animations

• A huge creator economy (templates, Experts program)

Figma Wins On:

• Familiar design-first workflow

• Collaboration

• Lower learning curve for existing Figma users

• (Eventually) shared libraries + design system integration

Figma’s angle: stay inside one tool.
Framer’s angle: build marketing sites that scale.

Final Verdict: Should You Switch?

Not yet.

If you’re already in Framer and building serious websites, Figma Sites isn’t ready to replace it.

But if you’re a Figma superfan looking to launch simple sites fast, it’s a solid first step, and the roadmap looks promising.

We’ll be watching it closely.


We’ve built a whole ecosystem for the Framer community. Explore plugins, resources, and courses here.
We've also set up a Discord to get feedback from the community Join the conversation here.

Catch you next time!
Ryan ✌️