ByFigma Weave tools are AI-powered, node-based workflows built directly into the Figma canvas that turn a text prompt or reference image into on-brand icons, mockups, and image edits without leaving your design file. Since September 2026, Figma has let anyone publish these workflows to the Figma Community, so you can reuse a tool someone else built instead of starting from a blank node graph.
That shift matters because Weave used to be a solo tool: you built a workflow, used it, and it stayed in your file. Community publishing turns it into a shared library, the same way Figma plugins became a marketplace instead of a personal script folder. This guide covers what Figma Weave tools actually do, how the September 2026 Community update changes your workflow, and how to publish, find, and evaluate tools worth your time.
What Are Figma Weave Tools?
Figma Weave tools are reusable, node-based AI workflows that live on the Figma design canvas rather than in a separate app. Each tool chains together an input (a prompt, an uploaded image, or both), a generation model, and one or more editing steps, so the whole process can be saved, duplicated, and re-run with new inputs.
Figma introduced Weave at its Config 2026 conference on June 24, 2026, rolling it out to Professional plans and above with Full seats. At launch, Figma shipped more than 30 built-in Weave tools covering tasks like generating on-brand icon sets and transferring a style reference onto a new image (Figma Blog, 2026). The pitch was straightforward: instead of jumping between Midjourney, Photoshop, and Figma for one asset, you run the whole chain on the canvas you’re already designing in.
How Do Figma Weave Tools Work on the Canvas?
A Weave workflow is a small graph of connected nodes, not a single button. A typical chain looks like: an input node (your prompt or a reference image) feeds a generation node (which model to call and what settings to use), which feeds one or more editing nodes (upscale, reframe, style transfer, background removal), which feeds an output node that drops the result onto your canvas as a normal layer.
Because every step is its own node, you can swap one piece without rebuilding the rest. Change the reference image in the input node and the same chain regenerates a new icon in the same style. This is what makes a Weave tool reusable in a way a one-off AI prompt isn’t: the structure is saved, only the inputs change.
Figma’s own framing for this is “repeatable image generation tasks” — the same graph, run again and again with different source material, rather than a new prompt written from scratch every time (Figma Help Center, 2026).
Although most published examples so far focus on still images, Weave’s underlying platform is built to route to more than one type of model, covering image, video, audio, and 3D generation from the same node-based canvas. That means the image-focused tools available today are the first wave of a broader system, not the ceiling of what a Weave workflow can eventually chain together.
What Changed With Community Publishing in September 2026?
Before September 2026, a Weave workflow you built stayed inside your own Figma file. If a teammate wanted the same tool, you had to hand them the file or walk them through rebuilding the node graph. Figma closed that gap by adding Community publishing for Weave tools, letting builders push a finished workflow directly to the Figma Community from the design canvas.
Published workflows now appear at figma.com/community/ai-workflows and surface in Community search and feeds alongside plugins and widgets (Figma Blog, 2026). Early community tools covered room renders from a moodboard, image reframing to a new aspect ratio, sketch-to-render conversion, and even niche use cases like nail-art previews, proof that the format works for narrow, repeatable jobs as much as general-purpose ones.
Why Did Figma Build a Community Layer for Weave?
Figma’s plugin ecosystem is the closest precedent, and it’s instructive. Plugins started as a way for individual designers to script repetitive tasks in their own files. Once Figma opened a Community marketplace for them, plugins became a distribution channel: a solo developer could build one utility and have thousands of teams install it instead of rebuilding it themselves.
Weave’s Community layer follows the same logic, applied to AI image generation instead of UI automation. A designer who solves “turn a moodboard into a photoreal room render” once can publish that exact Weave tool, and every other team with the same recurring task skips the trial-and-error of prompt engineering and node wiring. For Figma, it also means the platform’s AI capabilities grow through its user base rather than through Figma’s own team shipping every possible workflow by hand.
There’s a practical upside for design leads too. If two designers on your team independently discover the same Figma Weave tools through Community search, you get consistent output across a project without writing a shared prompt guide. The workflow itself becomes the shared standard.
How Do You Publish Your Own Weave Workflow to Figma Community?
Publishing follows the same shape as publishing a Figma plugin, applied to a node graph instead of code. You build and test the workflow in your own file first, then push it live from inside Figma once it works the way you want.
- Build your Weave workflow on the canvas and run it a few times with different inputs to confirm it holds up.
- Open the publish option from the Weave panel once your graph is stable.
- Add a title, a short description of what the tool generates, and a cover thumbnail showing a sample result.
- Submit it — Figma reviews new Community submissions before they go live.
- Once approved, the tool appears under your Community profile and in the AI workflows feed.
Keep the description specific. “Turns a moodboard into a photoreal room render” tells a browsing designer exactly when to reach for your tool; “creative image generator” does not, and it will get buried under more specific listings.
What Are Common Mistakes When Publishing a Weave Workflow?
Most rejected or ignored Community submissions share the same handful of problems, and they’re easy to avoid once you know to check for them before you submit.
- Publishing a workflow that only works with one specific reference image instead of any input in that category.
- Using a generic cover thumbnail that doesn’t show a real example of the tool’s output.
- Skipping a written description and relying on the title alone, which hides the tool from relevant searches.
- Leaving default or placeholder text in prompt nodes, so duplicated copies produce inconsistent results for other users.
- Publishing before testing with at least two or three different inputs, which is often when edge cases surface.
The fix for nearly all of these is the same: treat publishing like shipping a small product, not saving a personal file. Test it the way a stranger would use it, not the way you built it.
How Do You Find and Duplicate a Community Weave Tool?
You don’t need to build from zero to use Weave. Browse figma.com/community/ai-workflows, or search directly inside the Weave panel in a Figma file, and you’ll see published tools with a preview of their output.
- Search or browse the AI workflows feed for a tool matching your task.
- Check the example output on the listing to confirm the style and quality match what you need.
- Click to duplicate the tool into your own file as an editable node graph.
- Swap in your own prompt, reference image, or brand assets in the input node.
- Run it, then adjust individual nodes (upscale strength, aspect ratio, style weight) if the first result isn’t quite right.
Because you get the full node graph, not a locked black box, you can also learn from tools you duplicate. Opening a well-built community workflow and seeing how someone chained reframe-then-upscale-then-style-transfer teaches you the pattern for your own future tools.
Which Weave Community Tools Are Worth Trying First?
Early Community listings cluster around a handful of repeatable, visual tasks rather than general-purpose “make an image” tools. These five categories cover most of what a working designer needs in a given week.
| Tool Type | What It Generates | Best For |
|---|---|---|
| Room render generator | Photoreal room mockup from a moodboard | Interior and product mockups |
| Image reframe tool | Extends or crops an image to a new aspect ratio | Resizing one asset for multiple social formats |
| Sketch-to-render tool | Turns a rough sketch into a polished visual | Early concept reviews with clients |
| Nail art preview tool | Realistic preview of a nail art design | Niche product and service previews |
| On-brand icon generator | Icon set matching a brand style reference | Building consistent icon libraries fast |
Notice the pattern: every one of these solves a job you’d otherwise repeat by hand a dozen times a month. That repeatability, not raw generation quality, is the actual selling point of a published Weave tool over a one-off AI prompt.
How Does Weave Fit Into an Existing Design System?
A design system lives or dies on consistency, and that’s exactly where ad-hoc AI generation tends to break things: two designers prompting the same model separately will get visually different icons, illustrations, or renders even when they’re aiming for the same brand look. Figma Weave tools address this by making the workflow itself the reusable asset, not just the output.
In practice, that means a design system owner can publish (or privately share) a single Weave workflow tuned to the brand’s exact style reference, color treatment, and output size. Every designer on the team then runs the same node graph instead of writing their own prompt from memory, which keeps generated icons, mockups, and hero images consistent with components already in the library.
This is also where duplicating a Community tool and modifying it, rather than starting from a blank canvas, pays off. You inherit a working structure and only need to swap the style reference node for your own brand assets.
Figma Weave vs Other AI Design Tools: How Does It Compare?
Figma Weave isn’t the only place to run AI image generation inside a design workflow. Canva’s Magic Studio and Adobe Photoshop’s generative fill cover similar ground but live in different apps, with different plan requirements and different strengths.
| Tool | Where It Lives | Best For | Plan Required |
|---|---|---|---|
| Figma Weave | Figma design canvas (node graph) | Reusable, chained image workflows tied to a live design file | Professional and above, Full seat |
| Canva Magic Studio | Canva editor | Fast one-off graphics and templated content | Canva Pro |
| Photoshop Generative Fill | Photoshop layers panel | Precise photo editing and compositing | Creative Cloud with Photoshop |
If your team already lives in Figma for handoff and design files, Weave keeps the AI step in the same place your components and prototypes already exist. If you need fast standalone graphics without a design file at all, Canva’s Magic Studio is still the quicker path for that specific job.
What Do Weave Tools Cost and Who Can Use Them?
Weave tools require a Figma Professional plan or higher, and specifically a Full seat rather than a Collaborator or Viewer seat, according to Figma’s own help documentation. Free-tier Figma accounts cannot build or run Weave workflows, though they may still view results shared into a file by a teammate with access.
For a design team already paying for Professional or Organization seats, Weave doesn’t add a separate subscription, it’s part of the plan you already have. That’s a meaningful difference from stacking a separate Midjourney or Runway subscription on top of your design tools, and it’s likely why Figma bundled Weave into an existing tier instead of selling it as an add-on.
What Are the Current Limitations of Figma Weave?
Weave is not a replacement for a dedicated image editor, and it’s worth knowing where it stops being the right tool. Seat requirements are the first wall: a Starter or free-plan collaborator on a shared file can view Weave-generated layers but cannot open the node graph or run the workflow themselves.
Generation quality also still depends on the underlying model a given node calls, so a Community tool built around one model’s strengths won’t automatically match a different model’s output style if Figma swaps providers later. And because Community review is manual, there’s a lag between a workflow being built and it becoming publicly searchable, so newly built tools don’t appear instantly.
None of this erases the core value: for teams already living in Figma, running repeatable image generation on the same canvas as the rest of the design work removes a real amount of app-switching, even with these caveats in mind.
Weigh the limitations against your actual workload before committing time to building a workflow from scratch. If your team runs the same type of image request more than a few times a month, a Weave tool pays for the setup time quickly; if it’s a one-off need, duplicating an existing Community tool or using a standalone generator may still be faster than building your own Figma Weave tools from a blank node graph.
Frequently Asked Questions
What is Figma Weave?
Figma Weave is Figma’s node-based AI workflow system, launched at Config 2026, that lets you chain image and video generation models with editing steps directly on the design canvas rather than in a separate app.
Do I need a paid Figma plan to use Weave tools?
Yes. Weave requires a Professional plan or above with a Full seat. Free and Starter plan accounts cannot build or run Weave workflows.
Can I publish a Weave workflow without writing code?
Yes. Weave workflows are built by connecting nodes visually on the canvas, so publishing one to the Figma Community requires no coding — you build the graph, add a title and description, and submit it for review.
Where do published Weave tools appear?
Published Weave tools appear at figma.com/community/ai-workflows and in Community search and feeds, the same discovery surfaces used for Figma plugins and widgets.
Is Figma Weave the same as Figma AI?
No. “Figma AI” is a broader umbrella covering features like the design agent and code layers introduced alongside Weave at Config 2026. Weave specifically refers to the node-based image and video generation workflows.
Can I use Weave tool output commercially?
Weave output follows Figma’s standard usage terms for AI-generated content in your plan, so check the specific model’s licensing terms and your Figma plan’s AI terms before using an output in a commercial deliverable, since terms can vary by the underlying model a tool calls.
Does Weave only generate images, or video too?
Today’s published Community tools are mostly image-focused, but Weave’s platform is designed to route to image, video, audio, and 3D generation models from the same canvas, so video-focused Weave tools are expected to expand over time.
Community publishing turns Figma Weave tools from a personal shortcut into a shared library, similar to what happened when Figma plugins first opened to outside developers. If you already build repeatable image workflows in Figma Motion or organize large files with nested folders, adding a published Weave tool to your kit is a small step. Pair it with the editing options covered in our guide to Figma’s AI image editing tools, or browse the wider landscape in our roundup of AI tools for graphic designers to see where Weave fits against the rest of your stack.
Subscribe for Newsletter
