Skip to content
News Figma Sep 2026

Figma: Weave gets design file input and community tool publishing

Figma released two connected updates to Figma Weave across September 16 and 17, 2026.

The first, released September 17, is a Figma node that connects existing Figma Design frames directly to Weave workflows. Designers can copy a frame from Figma Design, paste it into Weave, and it becomes a configurable node in the workflow. Text and image layers inside the frame become inputs that can be varied across workflow runs — enabling the creation of campaign variations, localized versions, or new visual assets that inherit the styling of the original design.

The second update, released September 16, extends publishing: custom Weave tools can now be shared to the Figma Community, making them accessible to any Figma user directly from the canvas in Figma Design. At launch, the direct-in-canvas support covers image and vector generation tools; other tool types can be published to the Community but are used through Weave rather than from within Figma Design.

Together, the two updates close a practical gap that existed since Figma introduced Weave. Previously, workflows had to be built from scratch using media sources, text inputs, or URL references — design assets created in Figma Design were not directly connectable. The Figma node closes that loop, letting existing design work serve as the brand anchor for a generative production run rather than requiring designers to re-upload or re-specify visual inputs separately.

For design systems teams, the Community publishing feature is the more structurally significant change. A team that builds a reliable on-brand image generation tool can distribute it across the organization or externally, rather than rebuilding the same workflow in each context where it is needed. The mechanism also means that well-built Weave tools built by external practitioners can spread through the design community the same way Figma plugins have — through community adoption rather than organizational deployment.