Figma pushes its generative plugins and shaders further: what really changes

What Figma just announced

At Config, Figma had already surprised everyone by letting people build their own generative plugins and shaders just by chatting with the Figma agent. An impressive technical feat, sure, but one that still felt somewhat static: you generated an effect, admired it, and that was pretty much it.

With this new update, Figma moves things forward. Concretely, four new features change the game:

• Animated, interactive shaders that can react to mouse movement
• Publishing to the Figma Community, to share your creations with the whole world
• Publishing within your organization, reserved for Organization and Enterprise plans
• A code viewer, to inspect and download the generated code

Nice bonus: the MCP server updates now let you evolve your plugins and shaders through a third-party agent, and even better, when you copy a frame with applied shaders into an external agent, the generated React output stays faithful to the visual effect. No more bad surprises at implementation stage.

Why this is not just a creative gadget

You could think: just another nice-looking effect to impress people in a demo. Except the real story here is the bridge between design and code. Until now, a shader generated in Figma often stayed a pretty static image, great to show off in a meeting, much trickier to keep alive once the project landed in developers hands.

The code viewer changes that equation. A designer can now generate an effect, test it, animate it, and hand the code directly to their technical team. No more guessing or manually recreating the effect: the code exists, and it can be viewed and downloaded.

Community publishing plays a different but equally structural role: it turns every great shader created by a designer into a reusable resource for the entire Figma community. Much like components or classic plugins, but applied to generative effects that used to be reserved for a handful of procedural visual creation experts.

What this actually changes on a project

Picture a designer who wants a slightly interactive animated background on a landing page, reacting to hover. Before, that would have meant calling in a creative developer or spending hours manually tuning CSS or WebGL. Today, the Figma agent can generate the effect, animate it, and hand over workable code almost directly.

This does not replace the expertise of a development team, but it massively cuts down the back-and-forth between creative intent and technical feasibility. A real time saver during the exploration phase, exactly where most energy usually gets lost iterating between design and dev.

A strong signal of where Figma is heading

This announcement fits a clear trajectory: turning Figma from a design tool into a platform that generates functional code. After Figma Make and the first agents able to prototype interfaces, generative shaders and plugins confirm that ambition. We already touched on this around the Config announcements in Figma Motion, shaders, and the agent stuck in permanent beta, and this update is the logical, expected continuation of that story.

{{webdesign}}

Mazette.co take

At Mazette.co, we use Figma every day to design interfaces before bringing them to life on Webflow. So naturally, we follow these developments with a very pragmatic eye: does it save us time, does it improve the final quality, or is it just a shiny demo that ends up gathering dust?

Here, we clearly lean toward the good side. The code viewer, in particular, strikes us as the most useful addition. On our projects, we regularly spend time manually recreating effects we had already "almost" designed in Figma. Being able to access the code of a shader directly, even if it often needs adapting for final integration, is a genuine shortcut.

The animation and interactivity side of shaders also speaks to us a lot, since this is exactly the kind of detail that separates an interface that looks "nice" from one that feels alive. We already made that point in our article on the subtle art of breathing life into interfaces: well-dosed motion changes everything in how a product is perceived. Being able to generate this kind of effect directly in Figma, without depending on a creative developer from the ideation phase onward, is an agility boost we are not going to complain about.

One caveat still, and an important one: the fidelity of the generated output needs checking on a project-by-project basis. A shader that works nicely in an isolated demo can behave differently once integrated into a real production context, with constraints around performance, accessibility or browser compatibility. On Webflow especially, we stay careful about the weight and smoothness of these effects, which should always serve the experience rather than the other way around.

Still, the direction Figma is taking makes sense, and for an agency like ours that pushes its designs all the way to production, it is rather exciting. Less friction between design and code is always good news for our clients, who get faster websites without compromising on quality. If you want to see what this kind of tool can concretely bring to your project, our Webflow expertise is precisely built to turn these advances into visible results.