Code moves onto the shared canvas

Code layers is now in open beta, letting teams prototype and build directly with code on the Figma canvas. If everyone tests ideas in separate coding tools, the work becomes isolated and hard to share or compare. Code layers brings that exploration into Figma Design, so a team can build visually in code and still use the canvas's collaborative tools.

Working with code lets you judge how an experience behaves — micro interactions through full flows. With code layers, teammates can place prototypes side by side, leave feedback on them, or duplicate a layer to try their own variation. It also works as a starting point for several kinds of existing material: turning designs into working code, importing a coded prototype, or capturing a live site with the Chrome extension.

Building from what already exists

Starting from scratch is sometimes right, but when exploring a feature or flow it's often faster to reuse the codebase. Code layers accepts several entry points:

  • Import a lightweight prototyping codebase from GitHub or a local folder; GitHub imports stay linked to the repository.
  • Bring in a prototype built in an IDE through the Figma MCP server.
  • Capture a live web page with the Figma Chrome extension and keep iterating alongside the original.
  • Turn a Figma design into an interactive code layer.

Figma designer Maria Gaston imported an IDE prototype into a code layer with the MCP server so her team could review it. "Working in the coding tool made it hard to share work and iterate," she says. "It was a very isolated environment. Now, everyone else who has access to this file can easily go in and play with it."

At Cox Automotive, senior product manager Lindsay Brechler brought an existing HTML prototype into code layers to align stakeholders on a new feature. Because each version remained on the canvas, she could continue from any version. "From iteration to iteration, code layers holds every screen and interaction together very well," she says.

For early concepts, Derek Onay, Lead Product Designer for Design Systems at Rocket Money, builds a design into an interactive code layer. During foundational screen component work, the team needed interactions and accessibility settled before they reached users, and the code layer carried the discussion. "With code layers, the real value is in having the ability to better communicate ideas and gain stakeholder alignment," he says. "I can share a working prototype and meet my team where they already are, in Figma."

Comparing directions in parallel

Agents in an IDE can make a first idea feel final before alternatives get a look. Code layers lets several versions of a prototype live on the canvas at once, so a team can duplicate one, change the approach, and compare both without switching tools. Miguel Wermuth, a product designer at Dell Technologies, works on account experiences for enterprise customers and dell.com shoppers across mobile, tablet and desktop. He uses code layers to bring conversational AI prototypes — a stakeholder types a question, the prototype returns the matching screen — onto the canvas. After designers approve a flow, he builds it in a code layer for business sign-off, since stakeholders follow a working prototype more easily than static screens. He duplicates code layers side by side to compare versions. "With code layers, I can work with code while designing on the canvas," he says. "It's really powerful to have more back and forth between design and code."

Keep exploring your live web experience on the canvas with the Figma Chrome extension.

The canvas also supports a wider view. Matt Davey, Chief Experience Officer at 1Password: "The real superpower of Figma has always been the canvas. It's like when we used to print out all the pages of a website and stick them on a whiteboard. Being able to look at these UI elements together is incredibly valuable."

Editing, prompting and shipping changes

Refinement can run through the Figma agent. At Superside, motion design lead Leonardo Rica prompted an agent to build a credit card wallet code layer — cards scroll, a tapped card comes forward and flips — and when cards briefly stacked in the wrong order, a single precise prompt describing the cause fixed it "like magic." Make design adjustments and apply them to the working prototype, or use Extract designs to turn a screen or flow from a code layer into editable Figma layers.

Kris Murphy, Senior Product Designer at Checkout.com, had about a week-long proof for a prospective client: asked to demo products businesses embed in their own customer experiences, he built it in code layers. "Code layers helped me build the demo about 50% faster, and that's with a tool I'm not entirely familiar with yet," he says. Before sharing, he extracted every screen from the code layer onto the canvas, reviewed them side by side, sent the edits back into the code layer, and the team could see the full flow of revisions. "Code layers feels like a proper bridge between design and development. It's helped me ideate and deliver at speed," he says.

Other options: comment directly on a prototype, annotate frames to point the agent at a needed change, inspect or edit code directly, or use the updated fullscreen experience to run multiple agent threads for different parts of the work. Versions can also be merged — if a team prefers one version's layout and another's interactions, the agent can combine them into a new version to test.

When a prototype is ready to share, push the updated code to a branch for teammates to build on, and open a pull request so the team reviews changes before merging into the shared project.

Availability and cost

Code layers is rolling out in open beta starting today and uses AI credits. On paid plans, creating and editing inside code layers is free through November 4, 2026.