Budget Figma Make prompts before AI credits disappear

Figma has updated its AI-credit documentation with concrete examples for Figma Make and ChatGPT-generated Figma files. Confidence level: confirmed for the documented credit rules and examples, approximate for the per-prompt numbers because Figma says agentic AI consumption varies by model, task complexity, and context. Teams using Figma Make should now treat prompts like a budgeted production resource, not a free design experiment.

What changed

Figma's Help Center now gives example AI-credit ranges for agentic design work. The page says Figma Make prompts can vary, but lists examples such as roughly 30+ credits for changing a font, 75+ credits for making an attached design interactive, and 100+ credits for generating an app from scratch.

The same page says generating a Figma Slides presentation through ChatGPT uses roughly 28-72+ credits, while generating FigJam diagrams through ChatGPT does not consume Figma AI credits at this time. Figma marks these rates as current as of July 2, 2026 and warns that costs can change as models and features change.

Why this is early

This is not a splashy product launch. It is an operational billing signal inside Figma's support documentation, which makes it easy to miss but useful for teams rolling AI features into design, prototyping, and slide workflows.

The strongest source is Figma's own AI-credit help page. The billing and seat-management page explains the broader shift to admin-controlled seats and prorated billing, while a public Figma Forum answer shows a practical edge case: credits are tied to the individual user's editor seat, not a transferable seat slot.

Key takeaways

• Figma Make is now easier to budget because Figma gives example credit ranges for common agentic tasks.
• Plan mode can consume credits before the build step, so approval-heavy workflows need room for both planning and execution.
• ChatGPT-to-Figma Slides generation consumes Figma AI credits; ChatGPT-to-FigJam diagrams currently does not.
• Credits do not roll over, do not stack across plans, and cannot be refunded by undoing an AI action.
• Admins should watch usage before broad Figma Make rollout, especially where multiple teams share paid seats.

Availability and access

Figma says AI credits are included with every seat on every plan, but feature access depends on plan and seat type. Users who run out of credits cannot complete additional paid AI actions until credits reset or an admin adds more.

Admins can purchase additional AI credits and track team usage from the admin dashboard. Enterprise customers also have an AI Usage API, which matters if design-agent work is moving from experiments into repeatable business workflows.

Practical LinkLoot angle

The useful move is to create a lightweight prompt budget before letting teams use Figma Make for production-adjacent work. Start by estimating credits for three common jobs: edit a component, turn a design into an interactive prototype, and generate a first app draft.

Then compare the cost with the old workflow. A 100-credit prompt may be cheap if it replaces a half-day prototype. It is wasteful if it burns through repeated correction loops because the brief was unclear, the model was overpowered for the job, or large context files were attached by habit.

For teams building repeatable AI workflows, pair this with a broader automation checklist from LinkLoot's AI workflow automation guide.

What to verify before you act

• Check your plan and seat type before assuming a user can run Figma Make or other paid AI actions.
• Review the current AI-credit table because Figma says consumption can change as models and features change.
• Confirm whether a workflow uses plan mode, since planning and build steps can consume credits separately.
• Track actual usage after each prompt instead of relying only on example ranges.
• For agencies and rotating teams, verify how credits behave when paid seats are reassigned.

Source check

Confirmed by: Figma's AI-credit documentation, which lists current example consumption rates and explains Figma Make, ChatGPT-to-Figma generation, resets, rollovers, and admin controls.

Billing context: Figma's pricing and seat documentation explains the broader seat model, admin approvals, and prorated billing rules that affect how teams manage paid access.

Operational context: The public Figma Forum thread is a practical support signal, not a policy page. It helps illustrate how seat transfers can affect AI-credit expectations, but teams should still confirm account-specific billing details with Figma support.