Previous versions of Figma plugins: version history has arrived

What Figma just changed

As of October 27, 2026, Figma is adding a piece that was sorely missing from its generative tools: version history. In practice, every time you edit a generative plugin or a shader, Figma now keeps a new version instead of overwriting the previous one.

Even better, each version gets a description written automatically by an agent. That means you get a real changelog without having to maintain it by hand, and you can tell at a glance which version is currently published. The rollout is happening gradually this week across all accounts.

Why this feature is arriving now

Generative plugins and shaders were born alongside the Figma agent, the feature that lets you build custom tools directly from the canvas, through prompts. The problem: until now, editing one of these tools meant overwriting the previous version. One regression, one poorly worded prompt, and you had to start all over again.

With the rise of generative plugins (and their move to general availability in early October 2026), this gap was becoming increasingly frustrating. Version history is the logical safety net for tools that evolve at the pace of the agent’s iterations, sometimes several times a day.

Mazette.co’s take

At Mazette.co, we work in Figma every day, on product design and SaaS product design projects. And we can tell you one thing: the lack of version history on generative tools was the most obvious blind spot of this new generation of plugins.

A design system is built through iteration. You test, you tweak, you try again. As long as this logic applied to classic frames and components, Figma already had version history to save the day. But the moment you touched a generative plugin or a shader created by the agent, you lost that safety net. Quite ironic for tools designed specifically to speed up experimentation.

So this update fixes an inconsistency more than it invents a groundbreaking feature. Still, it is good news, and an almost essential condition for product teams to adopt these generative plugins with confidence, without fearing the loss of a version that worked perfectly well.

The automatic agent generated description is the detail that changes everything day to day: on a design system shared by several designers, knowing who changed what (and why) without opening a separate file is exactly the kind of friction we are always trying to remove from our own projects.

{{webdesign}}

What this means for your projects

If you already use generative plugins or custom shaders in your interfaces, this update requires no action on your part: it rolls out automatically to your account this week. That said, it is a good opportunity to revisit your team practices around these tools, much like you would manage versions in a classic design system.

• Document your major iterations, even though the agent already generates an automatic description.
• Always check which version is published before sharing it with a client or another team.
• Take advantage of restore to experiment more boldly with your shaders, without fearing you will lose work that has already been validated.

It is also a useful reminder: in a UX/UI and product design project, tracing decisions matters as much as the decisions themselves. A living design system is a history you can consult, not a black box.