Figma Weave: internal tool publishing is finally here

What this Figma Weave update changes

Figma just announced, in its latest release notes, a feature that will speak directly to well organized product teams: internal publishing for Weave tools. In practice, organizations can now build their own tools based on Figma Weave (Figma’s generative AI building block for images, video, audio and more) and publish them so the whole team can use them, without going through the public Community.

Once published internally, the tool appears in Figma’s Tools tab, in exactly the same place as Weave tools built by Figma itself or shared via the Community. The difference: it stays confined to the organization that created it. Nobody outside has access to it.

This feature is only available on the Organization and Enterprise plans. If you are working on a Starter or Professional plan, you will either need to upgrade or keep relying on public Weave tools or ones shared manually between colleagues.

Why Figma is introducing this now

Since its launch, Figma Weave has positioned itself as Figma’s generative AI hub: image and video generation, soon audio too, powered by models like Seedance, Kling or Nano Banana. But a Weave tool built for a specific purpose (generating visuals in a given brand style, for example) remained either personal or public if you wanted to share it.

Internal publishing fills that gap. It follows a logic already familiar from component libraries or Figma design systems: you build something internally, publish it so the whole team benefits, without exposing your work to the rest of the world. Figma is applying that same mechanic to its AI tools.

It is also a way for Figma to strengthen the appeal of its Organization and Enterprise plans on the AI side, a compelling argument for product teams that are scaling up and looking to industrialize their generative AI usage without losing control over governance.

Mazette.co’s take

We use Figma daily on our product design projects, and this announcement speaks directly to us. Weave’s promise was never to replace your design tools, but to enrich them: generating a test visual, an illustration variant, a texture, without ever leaving Figma. Until now, the problem was that every Weave tool built internally stayed a bit orphaned, shared by hand or left sitting in some file.

With internal publishing, Figma finally treats Weave tools the way it treats design system components: you build them once, document them, publish them, and the whole team finds them in the same place. For a product team working with several designers under strict brand guidelines, that is a real win: it avoids homemade AI tools that end up producing off brand results.

Our only reservation: this feature is still limited to Organization and Enterprise plans. Smaller teams, often the most agile when it comes to adopting new AI uses, are excluded for now. We understand Figma’s business logic here, but we hope to see this feature trickle down to Professional plans eventually, since it is exactly the kind of work organization we recommend to our product design clients.

{{webdesign}}

What this means for your projects in practice

If you work with a product team that already uses Figma Weave to generate visual assets, here is what is worth testing right away:

• Identify the Weave tools your designers have built on an ad hoc basis and see which ones deserve to be standardized for the whole team.
• Check that your organization is on an Organization or Enterprise plan before looking for the internal publishing option.
• Use this centralization as an opportunity to document your internal AI usage, a task often left aside for lack of time.

This new feature fits into a broader trend at Figma: turning one off, individual uses into genuine team processes, whether for components, guidelines or now AI tools. It is a direction consistent with what we see among our fast growing clients, where design system discipline becomes a real speed lever.