At Config 2025, Figma unveiled six new features — one of the most notable being Figma Site. In this article, I’ll give you a quick overview of the tool, walk you through how it works, explore its benefits & limitations, and share some thoughts on how it might shape the future of web design.
What is Figma Site
Figma Site is a site builder built on top of the Figma design toolkit. It’s designed to bridge the gap between design and a ready-to-use web solution. The idea is simple: once you’ve created a pixel-perfect UI in Figma, you don’t need to switch to an integrated development environment (IDE) like VS Code to code it — you can stay within the Figma environment and continue building your site seamlessly.
How it works
I’ve recorded a quick video tutorial on how to use Figma Sites.
To create a site, you simply open Figma and select the “Site” option (note: this feature is available only to paid users). From there, you design your website just as you would any other project in Figma — the main difference is that Figma Site supports multiple mediums. In the example below, I’ve designed layouts for Desktop, Tablet, and Mobile.
Because its Figma, you can use your existing design—both UI components and styles. Figma Site also offers a well-curated collection of ready-to-use components (like hero sections, featured items, and navigation bars), all built with auto layout. This makes UI design significantly easier.
Figma allows you to optimize your design for a specific medium (e.g., mobile), and you can choose a primary medium (meaning the design from that medium will be adapted to others).
Once you’re happy with your design, you can publish it, and Figma will generate a shareable URL for your website that you can visit or share with your team.
Why Figma Site can be right move for Figma
There are two reasons for that. First, it reduces the learning curve. Not all UI designers have front-end coding skills, and they appreciate tools that will help them turn their design into code without too much hustle.
The second reason is the fact of switching from one environment to another — when you have a design in Figma and want to turn it into a coded solution, you naturally need to recreate it again, but in code. Of course, Figma design tools help with that, offering Dev mode, but you still have to do a lot of work. Figma Site solves both problems.
Why Figma Site can be wrong move for Figma
When we think of Figma, we primarily see it as a tool for UI designers, not a versatile tool for both designers and developers. Figma was created at a time when high-fidelity design was still a luxury, and it quickly gained recognition for democratizing the design process. Figma also aimed to simplify typical UI design procedures, such as design handoff (when you share the ready-for-implementation design with developers), by introducing Dev features.
The recent move to the web development territory is Figma’s attempt to react to changes that are happening in our industry. More and more companies are trying to combine the roles of designer and developer, and are hiring one full-stack product creator who can do both design and code. But the problem with this approach is that full-stack product creators are not necessarily UI designers; they are more likely to be front-end developers who know UI design. And when it comes to code, they are more comfortable with IDE rather than Figma UI simply because access to code gives them more freedom.
Plus, in 2025, a wave of “vibe coding” tools hit the market — Bolt, Lovable, and Cursor AI, to name a few. These tools can generate decent code (emphasis on decent, not perfect).
Vibe Coding for web with Cursor AI
But what about Figma? The unfortunate truth is that Figma doesn’t generate clean code. For example, even a simple text element results in a block of overly nested <div> elements, making the structure unnecessarily complex. The code Figma generates is better suited for quick web prototypes rather than production-ready websites.
Was Releasing Figma Site the Right Move?
We all know that predicting the future is tough, so what I’m sharing below is just my personal perspective. That said, I believe Figma’s attempt to become a more versatile, all-in-one tool is a misstep. It’s understandable that Figma feels pressure from rising competitors, and as a result, is expanding into the design-to-development space in an effort to stay ahead.
But by adding features that drift from its original vision, Figma risks alienating its core audience: UI designers who loved the tool for its simplicity and focus. Meanwhile, front-end developers are likely to stick with their preferred workflows — whether it’s coding in an IDE, using vibe coding tools, or relying on mature site builders.
Figma Site: Another Site Builder or a Glimpse Into the Future of Design-to-Web? was originally published in UX Planet on Medium, where people are continuing the conversation by highlighting and responding to this story.