Figma Config 2026: Code Layers, WebGPU Shaders, and what it changes
Florent Dabernat
July 14, 2026
5 min read
In this article
Figma announced several features in late June 2026 that bring design even closer to code. Beyond the announcement effect, they say something about where the craft is heading.
At every Config edition, Figma sets the tone for the year. The 2026 edition confirms an underlying trend: the boundary between design and code keeps blurring.
Code Layers: code on the canvas
The most structural new feature is Code Layers: import a GitHub repository directly onto the canvas, edit the code as you would edit design frames, then resync to the repo. In closed beta from July 2026, this feature tears down one of the last walls between the mockup and the implementation.
WebGPU Shaders and Weave Tools
Two other announcements deserve attention:
- WebGPU Shaders: the design agent generates parameterized shader programs from a simple text description.
- Weave Tools: more than 20 pre-packaged AI image workflows. Agency Taxi Studio, for instance, generated 3D product renders for Carlsberg in one day, where it used to take several weeks.
When code lives on the canvas, the design system stops being documentation next to the product: it becomes a source the machine can read.
Why it matters beyond the novelty
The point is not to chase every feature. It is what these announcements reveal: Figma is industrializing the same logic as a machine-readable design system. Design becomes directly usable data, not an image to transcribe. For a web project, that means an increasingly smooth design-to-development handoff, and one more reason to document your system properly.
Frequently asked questions
-
Is Code Layers available to everyone?
- Not yet. The feature is announced in closed beta from July 2026, with a gradual rollout afterwards.
-
Do I need to change my habits right away?
- No. What matters is understanding the direction: design and code are converging. Documenting your design system properly stays the best investment.