For years, the handoff between design and development has been one of the most friction-heavy moments in any agency workflow. Designers finish in Figma, export assets, write specs, and then watch developers rebuild the thing from scratch in a separate tool. The gap between a polished prototype and a live URL has cost studios thousands of hours annually, and entire product categories, from Webflow to Framer, have been built specifically to fill it.
Figma is now stepping directly into that gap. At its Config 2026 conference, the company announced Figma Sites, a native web publishing feature built inside Figma itself. The tool lets users publish responsive websites directly from their design files, with no export, no third-party platform, and no rebuild required. It is the company's most significant product expansion since it launched FigJam in 2021.
Figma Sites works by treating frames as publishable web components. Designers assign interactions, set responsive breakpoints, and define hover states using familiar Figma logic. When ready, they hit publish and receive a live URL hosted on Figma's infrastructure. The feature supports custom domains, basic CMS-style content blocks for teams that need repeatable layouts, and real-time collaboration on the published version the same way teams already co-edit design files. No code is required for standard layouts, though developers can inject custom CSS or JavaScript for more complex behavior.
The underlying architecture is worth understanding. Figma Sites does not simply screenshot your frames and serve them as images. It generates semantic HTML from vector shapes, text layers, and components, which means the output is indexable, accessible, and responsive by default. In early tests shared by the company, Lighthouse performance scores on Sites-published pages averaged 87 out of 100, a credible number for a no-code output. The feature is available immediately to all Professional and Organization plan subscribers, with a usage-based pricing tier for high-traffic sites launching later this quarter.
What It Actually Replaces
For many agency use cases, Figma Sites replaces Framer or Webflow at the prototype-to-microsite stage. Campaign landing pages, event sites, product launch pages, and pitch decks-as-URLs are the obvious first targets. These are low-complexity web properties that studios currently rebuild in separate tools, often spending four to eight hours per project on setup alone. Figma Sites collapses that to minutes.
Where It Fits in a Real Agency Stack
Figma Sites is not a replacement for full CMS platforms like WordPress or Contentful for large editorial properties. It does not have native e-commerce, complex form logic, or database connections. What it does well is cover the 60 to 70 percent of agency web deliverables that are essentially static or near-static publishing jobs dressed up as design work. For those projects, it removes a tool license, a developer handoff, and a deployment step from the process.
The Collaboration Angle
Because Sites lives inside Figma, clients can review a live URL that is also still an editable design file. A creative director can make a copy change, hit republish, and the live page updates in under 30 seconds. This closes a loop that has historically required a ticket, a developer, a staging environment, and a review cycle. For account teams managing fast-turnaround campaigns, that compression matters considerably.
Custom Code as an Escape Hatch
The custom code injection layer is a smart piece of product thinking. It means Figma Sites does not wall off developers; it just moves them downstream. Junior designers handle layout and content. Developers drop in tracking pixels, animation libraries, or API calls where needed. The tool earns adoption from both sides of the discipline without asking either to give up control entirely. This mirrors how Figma's Dev Mode established itself as a shared surface rather than a designer-only or developer-only feature.
Pricing and Plan Implications
The inclusion of Sites in existing Professional plan subscriptions is a clear land-and-expand move. Figma does not charge more upfront, but the high-traffic pricing tier means successful campaigns, the ones that actually get traffic, will generate incremental revenue. For agencies running dozens of short-lived campaign sites per year, the math on that tier will need scrutiny before they commit fully.
Initial reaction from the design community has been enthusiastic but measured. Several prominent Framer and Webflow advocates have noted that those platforms still offer deeper animation control and richer CMS capabilities. Figma Sites has not tried to match them feature-for-feature, which is probably the right call at launch.
The more interesting question is what Figma Sites does to the agency production model over the next 18 months. If the feature matures steadily and the performance benchmarks hold, studios will face a genuine decision about whether a separate web-building tool subscription is still worth the overhead. The companies that figure out the right division of labor between Sites and their existing stack early will move faster than those who treat it as an all-or-nothing replacement. Figma is not trying to own the entire web. It is trying to own the moment between design approval and first deployment, and that moment is worth owning.