Prefer English?
Prefer English? Switch the website language for a better experience.
On June 24th, Figma published a sprawling changelog summarizing everything unveiled at Config 2026. And this time, it's not just another comfort update. It's a rethink of what you can actually do directly on the canvas.
Three major workstreams stand out:
In concrete terms, here are the updates that strike us as the most significant for an agency like ours.
Until now, prototyping a smooth micro-interaction often meant stepping outside Figma entirely, heading to After Effects, Principle or Framer, and then trying to translate that back into CSS or JS on the dev side. Figma Motion changes the game: you can now build precise, expressive animations directly in a timeline, or let the Figma agent generate them from a text prompt.
The big idea here: build reusable animation systems (the same way you'd build a component design system) and hand developers animations that are ready to ship.
3D transforms let you add depth to your designs and images, and combine them with Figma Motion for a result that moves like it would in real life. Shaders, meanwhile, work through description: you tell the agent what you want, and it generates the texture, ready to share and drop straight into a file.
Both features are currently in invite-only beta.
This is arguably the biggest shift of the bunch. The Figma agent can now be given "skills" (added capabilities), attachments and connectors that give it more context to work the way you do. It's also making its way into FigJam and Slides, where it can generate tables and diagrams, or edit decks in bulk.
And the cherry on top: generative plugins. You describe the tool you need, and the agent builds it for you, on the fly.
| New feature | What it changes | Status |
|---|---|---|
| Figma Motion | Animate directly in the canvas, reusable systems, dev-ready export | Available |
| 3D transforms | Add depth to designs and images, combinable with Figma Motion | Beta, sign-up required |
| Shaders | Generate textures from a description, shareable and ready to use | Beta, sign-up required |
| Customizable Figma agent | Skills, attachments, connectors, now in FigJam and Slides | Available |
| Generative plugins | The agent builds a tool on the fly from a description | Available |
{{webdesign}}
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:
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.
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.
| Before this update | After this update |
|---|---|
| Static shaders, generated once | Animated shaders that react to the mouse |
| Effect visible only within the file | Community or organization publishing |
| Invisible code, to be recreated manually | Code you can view and download |
| Code export sometimes approximate | Faithful React output via the MCP server |
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.
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. This update is the logical, expected continuation of the Config announcements covered above.
Let's start with the good news. Figma Motion is a genuinely great addition. At Mazette.co, we regularly hand off fine-tuned interactions to our Webflow developers, and the gap between "what we imagined in Figma" and "what's actually technically feasible" has always been a source of friction. Being able to prototype an animation right in the canvas, with a reusable system and dev-ready export, closes a real pain point. We see it as a concrete boost to our Figma-to-Webflow workflow.
3D transforms and Shaders look appealing on paper, but we're staying cautious here. These are beta features, heavy on creative flair but not necessarily essential for 90% of the projects we run. We'll keep a close eye on them without rushing in.
Where we're most torn is on the customization of the Figma agent. Giving it "skills" and connectors so it better understands a project's context is a smart move. But let's be honest: the more autonomous and connected to our internal tools the agent becomes, the more questions arise around governance and quality control. An agent that generates mockups or slides from your documents is a real time-saver, provided a human still keeps an eye on it. At Mazette.co, we treat AI as an accelerator, never as an autopilot.
Our overall verdict: this wave of updates confirms a trend we've been tracking for months, Figma is aiming to become the single platform where design, motion, code and AI all coexist. For an agency like ours, working across both design AND Webflow implementation, that's good news overall: fewer back-and-forths between tools, more context preserved along the way. It remains to be seen how these beta features hold up once they roll out widely, before we fully fold them into our migration and production processes.
Code
Over 120 companies have already stepped out of the shadows with us.
A tool that lets you build precise animations directly in the Figma canvas, closing the gap between prototype and Webflow implementation.
No, both features are still in beta, sign-up required.
The ability to add skills, attachments, and connectors that give it more context to work the way a specific project needs.
Impactful titles, polished meta descriptions, sitemaps, Schema.org, Hn structure, and audits: these are the SEO foundations that make your content readable by both Google AND generative AI. We cover both simultaneously.
With over 180 clients, our agency is one of the few in France to hold the Webflow Premium Partner label, supporting you in every area, including custom web design, sophisticated automation, conversion optimization, and SEO and GEO visibility.
We create bespoke web designs focused on performance, user journeys, and conversion. Join over 180 clients who have trusted us to elevate their brand.
