Skip to main content
Zohra0419
New Member
March 10, 2026

Figma Make Ai Credit Limits Not Feasible

  • March 10, 2026
  • 187 replies
  • 9321 views

I’d like to share feedback regarding the implementation of AI credit limits in Figmake. As a designer managing multiple complex projects, I believe credit restrictions would greatly undermine Figmake’s usefulness in real-world design and prototyping workflows.  

1. Most AI usage is for fixing bad or incomplete output, not luxury use.  
In practice, a large percentage of AI prompts in Figmake are iterative—used to correct layout issues, rebuild misinterpreted elements, or align behaviors with visual intent. Each refinement quickly consumes credits even though the output quality depends on that iteration. Penalizing iteration limits the model’s ability to produce accurate prototypes, especially when the AI output is imperfect through no fault of the user, making credit usage really unfair and frustrating.

2. Predictability becomes impossible, discouraging adoption.  
With a credit cap that no one knows how to predict and calculate ahead of time, I can’t plan how far my Figmake usage will take me in a given project. Credits could run out mid-way, forcing me to manually rebuild AI-generated prototypes and creating major inefficiencies. For example, if I spend a week using Figmake for an interactive prototype and then hit a credit limit right before stakeholder review, I’d end up having to redo everything by hand including component mapping and manual prototyping—rendering the AI tool more of a liability than an acceleration.  

3. I actively use Figmake for time-intensive, pixel-perfect projects.  
I currently have five ongoing projects that rely on Figmake’s automation to achieve understandable prototypes across varying layouts, dynamic conditions, and complex component interactions. These require functional, clickable prototypes that would otherwise take hundreds of manual steps. To give you a sense of credit usage to achieve a prototype, each project reached hundreds of versions within a week of creation. AI limits directly restrict my ability to complete these on schedule or maintain parity between design and prototypes.  

4. Prototypes must stay updated and accurate.  
Projects evolve rapidly across teams. If AI updates become throttled because of credit exhaustion, Figmake prototypes drift from reality—outdated screens, missing conditional flows, untested interactions, and inconsistent visuals make it impossible to keep stakeholders aligned. Designers would revert to traditional Figma, eliminating Figmake’s intended value.  

5. Figmake bridges a huge gap with non-designer stakeholders.  
Stakeholders don’t want to learn how to use Figma’s preview tools—they struggle with finding files, switching flows, adjusting zoom, or enabling hotspots. Figmake solves this by letting me send a simple link everyone can understand without training. Credit limits would prevent consistent sharing of working AI-powered prototypes, creating friction in alignment and communication with non-design teams.  

6. Credit-based systems penalize professional users.  
Professional users already pay for Figma Organization plans come with the expectation of scalability and reliability. AI credit limits undermine that—power users end up penalized, while lighter users are unaffected. Enterprise workflows require consistency, not unpredictable usage caps. Requiring designers to repeatedly request additional credits from admins adds unnecessary friction, forcing us to justify needs and placing stress on teams with little control. 

7. Creativity and exploration get stifled.

Part of Figmake’s value lies in exploration—testing concepts, states, and flows in seconds. Predictive anxiety over “credit drain” limits experimentation. Designers will stick to safe, minimal use rather than exploring variations that lead to innovation.  

8. AI credit management adds unnecessary overhead.  
Tracking remaining credits adds cognitive and administrative burden. Instead of focusing on design, we’d have to monitor dashboards, request top-ups, or pause work mid-flow. This complexity erases the simplicity and joy that make Figma tools beloved.  

Recommendation:  
Instead of credit limits, please consider providing unlimited AI usage under paid plans with limits only for automation abuse.  
- Allowing local refinement of previous AI generations without repeated credit consumption.  

Pinned Reply By ksn

Hey ​@baewadalmaster ​@DonDesigns ​@JaredSF - we have been consolidating similar threads so conversations and updates around the same topic stay in one place. In this case, we’re merging related discussions into this thread. This makes it easier for people to quickly find answers to their questions.

When topics are merged, some threads may be closed or redirected, which can make it seem like things have disappeared (especially from older links).

If one of your posts is merged into another topic, you can always find it through your profile and see where it now lives.

If you have any other questions, let us know.

187 replies

Ryan_Stiers
New Member
March 18, 2026

Enterprise power user here. Agree with everyone that the current credit limits are laughably low, and will be the end of Make in our org(hundreds of users).. it only makes sence as functionally unlimited for Enterprise or allow us to connect to models we are already paying for to do the processing...

As of today I am critically blocked by the token limits on several large prototypes… and our enterprise thinks Figma is already expensive, so I guess this is how it ends for Make if not Figma as a realistic option, and we are never going back to manual prototypes due to credit limits… we will move to other workflows, and fast..

Also worth calling out that the current models are no where near good enough to cap usage so aggressively, like everyone else noted, most of my credits are spent fixing issues caused by Make in the first place..

Massive strategy failure from the Figma team…

Patrick Thommen
New Member
March 18, 2026

@Ryan_Stiers, let me know if you find anything comparable to it.👌

Arnold Daniels
New Member
March 18, 2026

I just cancelled. Too bad.

Josh22
Active Member
March 18, 2026

My AI credits were exhausted just one day into the new billing cycle. As a result, I am now in a position where I have to tell PMs that I can’t deliver interactive prototypes for user testing or feedback anymore.

Because of this, the team is actively looking to move away from Make and evaluate alternative tools. While AI prototyping isn’t the main purpose of design work, AI tools (like Make) get us closer to real, functional product experiences and improve UX decisions and UI design. They are more efficient than manually building a prototype in a vector-based tool like the main Figma product, which is limited, slow, has ongoing bugs for YEARS, and is harder to create the same level of interactivity as Make would. Especially with regard to enterprise-level products. I am not designing landing/marketing pages or a small mobile app here. Unlike the yearly Config event where they would show of “look you can click the plus and minus button on this numerical counter for a mobile app and it just works!” (remember that presentation, oooooh! /s)

The pricing model for additional AI credits is not a viable option. Given current budget constraints in the overall market at software companies, it’s unrealistic to justify ~$2,880 per user annually. With my current team size, this is not a cost-effective solution.

It’s hard enough for designers to justify their jobs (and salaries) at non-design-lead companies (most of them are like this), then justify the cost of the main Figma tool. Now we have to justify the cost of AI-driven tools at a very steep price. At once point I was asked “what’s wrong with Adobe products?!”, yeah...

Justin Ryea
New Participant
March 18, 2026

Figma Make is incredible. Now let's talk about the credits problem.

I'll set the scene: I'm a super user, long-time Figma fan, and over the past month I've been building complex prototypes in Figma Make — the kind I need to put in front of real users to validate with the market. Not toy demos. Real, layered, interactive prototypes.

In the span of about 2 hours, across 3 prompts, I burned through my entire month's worth of full-seat credits.

I'm now sitting here waiting on a response from your Head of UX about getting more credits, which gave me just enough time to write this.

The usage math is hard to ignore

After looping in our rep, I learned I'm apparently in the 10-15x monthly usage category with my current design file burning up 50,000 credits— so, not exactly the median user. I get that. The options on the table are a higher-priced pooled plan across our org (genuinely appreciate this option existing) or pay-as-you-go top-ups. Given that I burned a month of credits in 2 hours, pay-as-you-go would be financially catastrophic for how I work.

Here's the thing that's hard to shake though: what's being sold as credits is, at its core, token throughput — the same commodity I can access through OpenAI, Gemini, or Anthropic APIs directly. My rough estimate puts the markup somewhere in the 50–100x range? Am I off? That's a wide margin, and it's the kind of margin that historically invites disruption from a competitor willing to let users bring their own API keys with a higher flat seat fee.

Some thoughts on where this could go

I'm not here to tell Figma how to run a business — clearly you've built something people (including me) are genuinely addicted to - it’s absolutely incredible. But I do think about pricing and usage design in the products we build, and one principle I keep coming back to: don't put a wall between your users and the behavior you want them to have. Usage limits do exactly that.

A few models worth considering:

  • A power user tier — something in the $200–300/month range for unlimited or very high usage, similar to what GPT Pro, Gemini Advanced, or Grok Heavy are doing. For users like me, that's a real option.
  • Bring-your-own-API-key — let advanced users connect their own keys. Charge a premium seat fee for the Figma layer on top. This actually creates a higher willingness-to-pay ceiling, not lower.
  • Ecosystem monetization — integrations with the likes of Supabase, data layers, or tools that bridge design to real software creation could open up entirely new revenue streams without throttling core usage.
  • A tier aimed at real software creation — because that's the direction this is heading and we all know it.

I'd even take ads in a free tier over a usage cap, honestly. At least that keeps people in the tool.

I want Figma Make to win. I want to keep building in it. But the current credit model will price out exactly the users who would be its loudest evangelists and most compelling case studies. That feels like a miss worth fixing.

Happy to talk through any of this further — apparently I have some free time while I wait on that email back. 😄

DonDesigns
New Member
March 18, 2026

But to my surprise they already enforced all the months credits,  so now i have to wait 8 days to do anything again.  

 

Mine for whatever reason won’t reset until April 7, twenty days from now. Plenty of time for us to find an alternative since my company isn’t going to pay what it’d cost for my normal usage when we can do similar for much less elsewhere.

Justin Ryea
New Participant
March 18, 2026

Figma Make is incredible. Now let's talk about the credits problem.

I'll set the scene: I'm a super user, long-time Figma fan, and over the past month I've been building complex prototypes in Figma Make — the kind I need to put in front of real users to validate with the market. Not toy demos. Real, layered, interactive prototypes.

In the span of about 2 hours, across 3 prompts, I burned through my entire month's worth of full-seat credits - to the previous users comments - i bet another user’s point,  i bet i used 3x this creating a light mode of my last protoype and far more credits seem to be used for fixing bugs and crashes vs actually designing prototypes.  I guarantee there are bugs that along took the entire days credits to resolve - one i was working on 

I'm now sitting here waiting on a response from your Head of UX about getting more credits, which gave me just enough time to write this.

The usage math is hard to ignore

After looping in our rep, I learned I'm apparently in the 10x monthly usage category — so, not exactly the median user. I get that. The options on the table are a higher-priced pooled plan across our org (genuinely appreciate this option existing) or pay-as-you-go top-ups. Given that I burned a month of credits in 2 hours, pay-as-you-go would be financially catastrophic for how I work.

Here's the thing that's hard to shake though: what's being sold as credits is, at its core, token throughput — the same commodity I can access through OpenAI, Gemini, or Anthropic APIs directly. My rough estimate puts the markup somewhere in the 50–100x range. That's a wide margin, and it's the kind of margin that historically invites disruption from a competitor willing to let users bring their own API keys with a higher flat seat fee.

Some thoughts on where this could go

I'm not here to tell Figma how to run a business — clearly you've built something people (including me) are genuinely addicted to. But I do think about pricing and usage design in the products we build, and one principle I keep coming back to: don't put a wall between your users and the behavior you want them to have. Usage limits do exactly that.

A few models worth considering:

  • A power user tier — something in the $200–300/month range for unlimited or very high usage, similar to what GPT Pro, Gemini Advanced, or Grok Heavy are doing. For users like me, that's a real option.
  • Bring-your-own-API-key — let advanced users connect their own keys. Charge a premium seat fee for the Figma layer on top. This actually creates a higher willingness-to-pay ceiling, not lower.
  • Ecosystem monetization — integrations with the likes of Supabase, data layers, or tools that bridge design to real software creation could open up entirely new revenue streams without throttling core usage.
  • A tier aimed at real software creation — because that's the direction this is heading and we all know it.

I'd even take ads in a free tier over a usage cap, honestly. At least that keeps people in the tool.

I want Figma Make to win. I want to keep building in it. But the current credit model will price out exactly the users who would be its loudest evangelists and most compelling case studies. That feels like a miss worth fixing.

Happy to talk through any of this further — apparently I have some free time while I wait on that email back. 😄

JobGhost
New Member
March 18, 2026

I have a lot of projects on Figma that now I am not sure I will ever finish. I am going to switch to v0 by Vercel since it costs significantly less, I usually have to do somewhere between 200-300 prompts for it to get things right. It makes mistakes a lot. It cost me 14 credits to change the color of a button. 134 credits to update colors on like two pages. They are out of their minds and going to lose so many customers because of this. 

Trent Oscroft
New Member
March 18, 2026

I Made 3 prompt burned  500 credits, going to have to use a new program because this aint it 

Peacemaker_Colt
New Participant
March 18, 2026

So for $16 a month I get 3000 points to use, but it then costs $24 to get 1000 more points? So $8 more more 66% less AI points? Why wouldn’t i just create dummy after dummy account, to get the 3000 points for 16$? That mentality is going to sink this company. and that is just my 2c. Talk about price gouging for AI points… Usually refills are LESS than the initial price, not here it appears.