Figma Weave and Figma Design: Choose the Right Connection

Back

Kevin Riedl

9 min read · 3 Nov 2026
Last reviewed November 3, 2026

Next

A campaign headline changes in Figma, but the next Weave run still uses the earlier frame. Meanwhile, a teammate runs a similar task against another credit balance. Choose the connection before handing off the workflow.

Figma Weave connects AI generation and editing steps into reusable workflows. Use a Weave tool inside Figma Design for a packaged image task, connect a Figma frame to a standalone workflow for controlled layer updates, or run an existing tool through an agent. Each route has its own access, update and credit rules.

A node is one step in the canvas; a workflow connects those steps; a tool gives someone a simpler interface to run that workflow. Figma’s Weave workflow explainer describes that distinction. Sources checked: 3 November 2026. This guide combines current documentation with a proposed handoff. We have not run a live Weave campaign or measured output quality, speed or spending.

Which Figma Weave connection fits your task?

Choose a Design tool for a packaged task, a standalone workflow to edit generation steps, and MCP for agent execution. A tool exposes selected inputs; its workflow author uses the Weave canvas.

For the first route, the Design-tool instructions require a Professional, Organization or Enterprise plan and edit access to the file. Open Tools, filter for Weave, choose a tool, supply its inputs and select Generate. Open the underlying workflow in standalone Weave when you need to change how it works.

How do you connect a Figma frame to Weave?

Copy a Figma frame into Weave, map the text or image inputs, then choose Connect and the destination file. Pasting alone leaves the original file unchanged. For an initial trial, we would connect to a new file.

The Figma-node documentation specifies the sequence:

1. Link your Figma and Weave accounts and confirm that you can edit the source frame.
2. Copy the frame in Figma and paste it onto the Weave canvas.
3. Add an Input Text or Image node, then map it to the intended layer. These are the supported input-node types for this connection.
4. Select Connect and choose the original Figma file or a new file.
5. Check the destination and mapped layer with one deliberate change before expanding the workflow.

The final check is our proposed acceptance step. Record the destination file and frame so a reviewer can find the result.

Do Figma and Weave update automatically?

A connected Weave workflow pushes its changes to Figma automatically; direct edits in Figma require Update in Weave. Before running a variation after someone edits the design, pull the updated frame into Weave and check the mapped layers.

These directions come from the current node instructions. Assign one person to reconcile the frame before the next batch.

Which credits does each route consume?

Tools run inside Figma Design use Figma AI credits; standalone and MCP runs use Weave credits. The balances are separate and cannot be exchanged. Record the execution route with each trial so you can identify the subscription and budget it consumes.

The current credit-update FAQ dates Design-tool general availability and credit charging to 6 October 2026. Older free-beta descriptions are historical. The Weave account FAQ also makes clear that a paid Figma subscription does not include a paid standalone Weave plan.

Figma’s credit-rate table, labelled 15 October 2026 and checked for this article, lists 19 Figma AI credits per run for its first-party Replace background tool. Ten runs therefore consume 190 credits. If six results pass your review, that particular step costs about 31.7 credits per accepted result.

The six accepted results are hypothetical. This arithmetic excludes other operations and human review; it is not a measured acceptance rate or a full campaign estimate. Community tools vary with their workflow, models and steps. A custom standalone background workflow has its own Weave cost, so the 19-credit rate cannot be transferred to it.

How do you publish a tool for the right audience?

Package the workflow as a tool, inspect the exposed inputs, and verify the publication audience before releasing it. Tool sharing and workflow sharing are separate. Decide whether a teammate needs to run the operation or edit its canvas.

The Weave tool guide starts with an Output node and the Tool tab. Nodes without incoming inputs become tool attributes; locking a node hides its attribute. That reduces the controls a user sees, but it does not certify the output’s brand accuracy.

Earlier tool versions can be viewed and shared, but not edited. The connected-plan routing and administrator controls are also covered in Figma’s publication instructions. A Figma Starter account’s publication route does not grant the paid-plan access needed to run tools inside Design.

Ask a second teammate to run the published version with the agreed inputs, then review the resulting assets together.

What can an external agent run through MCP?

An external agent can run existing Weave tools and supported system models through Figma MCP. It can inspect inputs, upload media, follow progress and cancel a run. The reviewed documentation does not support creating or editing workflows through MCP; author them in the canvas.

The MCP operating guide uses linked accounts and the existing Figma MCP connection. The active Weave workspace determines which shared tools an agent can find. Direct model runs support existing system models, not imported models. The current MCP developer reference requires a paid standalone Weave account.

The documented interaction quotes a cost and asks for confirmation; workflows with dynamic costs, such as a dynamic iterator, may not have an upfront quote. We have not tested that interaction across clients. Inspect the requested operation before approving a run, especially when its cost cannot be quoted.

What would an approved asset handoff include?

An approved handoff should identify the destination frame, tool version, credit balance and reviewed asset. We would attach an acceptance record so another person can see which workflow and design revision produced the approved result.

Consider a proposed desk-lamp campaign with one approved product photograph, three aspect ratios and four languages. That creates 12 layout targets, not a claim that twelve model runs will produce twelve usable designs. Start with one layout and one language before expanding.

Keep the logo, approved copy and product facts in controlled Figma layers. Generate or edit the intended visual region, then map only the chosen inputs. Review translated copy separately, including line breaks and crop changes. This is a proposed procedure, not a built-in approval feature or a reported Wavect campaign.

If the accepted asset becomes a reference for UI implementation, our Claude Code design-system files guide covers the repository rules, tokens and components that govern that later step. The visual workflow alone does not supply those implementation rules.

When would we use Figma Weave?

We would use Figma Weave for a repeated visual task with defined inputs and acceptance criteria. Expand after a teammate can run it, find the output and identify the version and credit balance used.

Start with a Design tool for a contained image operation. Build in standalone Weave when you need to edit and reuse the sequence. Add agent execution once the operation is clear enough to request and review.

For a deliverable that needs a coding-agent video pipeline, installation and rendering stages, our OpenMontage production guide addresses that different job. We have not established a direct integration between OpenMontage and Weave.

If your team needs help introducing this kind of repeatable internal process, our AI implementation and team enablement service is the relevant next step. Agree the asset, owner and acceptance criteria before expanding the tooling.