Figma drops executable code into the design canvas, enabling code-layer workflows at Config 2026

Figma used the opening keynote of its Config 2026 conference on Wednesday to unveil a feature called code layers. The headline promise is simple but pretty disruptive: it brings executable code directly onto the collaborative design canvas. Instead of treating design and development as two separate worlds that teams pass files between, code layers aim to make the canvas a place where code can actually run, or at least be tested, inside the design workflow.

Here is the practical shift teams get right away. With code layers, teams can clone repositories and extract flows from code into design layers for testing. That matters because the current “hand-off” workflow between design and development often introduces friction, latency, and translation errors. Figma is explicitly targeting that handoff step, describing code layers as a way to collapse the step that has defined design-to-development for over the last few years (the source text frames it as a workflow “for over […]”, indicating long-standing process inertia).

If you are an executive, the immediate question is not “can designers run code?” It is “what happens to throughput when the boundary between design iteration and engineering validation gets thinner?” In most product organizations, design teams iterate rapidly on visuals and interactions, but engineering validation often waits until later stages. Code layers change the shape of that timeline by letting teams pull real code flows into design layers, then test earlier. Even if you assume the feature does not eliminate engineering involvement, it can reduce the number of times teams have to re-explain behavior after the fact.

There is also a workflow incentive to watch: the more design teams can work with flows that originate in repositories, the more likely those flows become standardized inside design artifacts. That can be a big deal for complex products where teams rely on shared components, interaction patterns, and consistent behavior across platforms. When code enters the canvas, consistency is no longer only a documentation problem. It becomes an operational pipeline problem, and pipelines typically reward teams that can automate extraction, testing, and updates.

The source also ties this to collaboration, which is where Figma’s business advantage usually comes from. The canvas is built for teams working in parallel. By putting executable code into that same shared space, Figma is effectively moving part of the engineering feedback loop into the collaboration layer that product teams already use. That can change how reviews happen. Instead of reviewing static designs and then waiting for engineering to implement and test, teams can test flows as part of the design layer work.

From a governance perspective, executives should think about what “executable code on a design canvas” implies for security and compliance, even if the source does not detail the controls. In regulated or risk-sensitive environments, teams typically need visibility into what code runs, where it comes from, and how changes are tracked. The capability to clone repositories and extract flows suggests a tighter integration between engineering sources and design artifacts. That can improve auditability if the system tracks provenance, but it can also raise the bar for identity management, access controls, and change management. The strategic point is that code-layer adoption will not be only a UX decision. It will be a process and policy decision.

Then there is the competitive angle for product organizations that are not only using Figma. If the design-to-development boundary is shrinking, tools that rely on that boundary as a revenue layer (for example, by selling handoff or translation services, or by positioning themselves as the “bridge”) could feel pressure. Meanwhile, other design tools and developer workflow vendors may have to respond by tightening their own integration story. Figma’s Config 2026 keynote makes it clear it sees the canvas as an execution environment, not just a drawing board.

Strategically, code layers land right where most leadership teams feel pain: coordination across disciplines, faster iteration, and fewer costly misunderstandings between what designers specify and what engineers build. By enabling teams to clone repositories and extract flows into design layers for testing, Figma is making testing earlier and handoffs less central. For executives, the opportunity is speed. The risk is rollout complexity, because the feature touches both design collaboration and engineering source workflows. The organizations that treat this as a workflow transformation, not a feature toggle, are the ones most likely to turn Config 2026’s announcement into measurable product delivery gains.