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

Pat5
New Participant
March 9, 2026
  • I can say is that will never never be any unused credits.
  • I just did a prompt to move a toast message down 50px - this cost 64 AI credits!!!!!
  • I would have coded this but interested in credit usage
  • 3500 AI credits is no where near the ball park to create a prototype to test on. 
  • I have my team looking into Claude Code and MCP now, to see if this will be a viable option
  • We have been very impressed with FigmaMake in creating fantastic prototype for testing
  • BUT unfortunately - Hiring a fulltime dev will be cheaper than using FigmaMake


 

[Moderator note: This post was merged from “Figma Make: 3,000 AI credits/month isn’t viable for iterative product work” into "Figma Make Ai Credit Limits Not Feasible" on 12-Mar-2026.]

m1n3g
New Participant
March 10, 2026
  • I can say is that will never never be any unused credits.
  • I just did a prompt to move a toast message down 50px - this cost 64 AI credits!!!!!
  • I would have coded this but interested in credit usage
  • 3500 AI credits is no where near the ball park to create a prototype to test on. 
  • I have my team looking into Claude Code and MCP now, to see if this will be a viable option
  • We have been very impressed with FigmaMake in creating fantastic prototype for testing
  • BUT unfortunately - Hiring a fulltime dev will be cheaper than using FigmaMake


 

 



 

I’m only halfway through my portfolio showcase project. I just modified and checked for errors, and a single prompt cost more than 600 credits. How is 3000+ supposed to be enough haha?

[Moderator note: This post was merged from “Figma Make: 3,000 AI credits/month isn’t viable for iterative product work” into "Figma Make Ai Credit Limits Not Feasible" on 12-Mar-2026.]
 
 
IanM
New Member
March 10, 2026

100%. Couldn’t agree more. This issue also affects a well known whiteboarding app.

March 11, 2026

100% Agree, 3000 credits is about 45 mins usage, this has made the platform, which has JUST begun to be useful with the introduction of the more advanced models completely unsustainable from a usability perspective. I will burn 180 credits asking it do do a simple task, the requirement to use a advanced model is basically mandatory as the lesser models just wont get the outcome, The AI agent will forget the context within a prompt or two and will activity LIE to you on the lesser models. I believe the platform has become extremely usable now, but the credit system needs to be reviewed urgently as this is a deal breaker for everyone trying to use it as a actual tool-set. There are alternatives, i suggest everyone start voting with their feet.

March 12, 2026

Hi Everyone, the new credit system is a massive concern, 3000 credits is about 45 mins usage, this has made the platform, which has JUST begun to be useful with the introduction of the more advanced models completely unsustainable from a usability perspective. I will burn 180 credits asking it do do a simple task, *which will still need to be reiterated 5-6 times to get it right” the requirement to use a advanced model is basically mandatory as the lesser models just wont get the outcome, The AI agent will forget the context within a prompt or two and will activity LIE to you on the lesser models. I believe the platform has become extremely usable now, but the credit system needs to be reviewed urgently as this is a deal breaker for everyone trying to use it as a actual tool-set.

please institute unlimited plans, it doesn't matter if the base price increases significantly, but the method in which this will be rolled out is going to kill the reason why any of us are using it. its a shame as many people have built workflows and processes around the Figma Make platform, but this is platform destroyer as its simply not going to be workable post these changes,

There are alternatives, i suggest everyone start voting with their feet. Can everyone please start adding their 2 cents in?

 

Save your work to GitHub guys.

[Moderator note: This post was merged from “Figma Make Credit system needs immediate remediation” into "Figma Make Ai Credit Limits Not Feasible" on 12-Mar-2026.]

March 12, 2026

I believe the most fair way to handle this, Figma Make team, is to allow the user in the admin settings to enter their own API keys for their own models, that way the burden of AI model cost is not on you and you will get a recurrent income form supplying the platform, the burden of consumption will then fall upon the consumer as they consume.

[Moderator note: This post was merged from “Figma Make Credit system needs immediate remediation” into "Figma Make Ai Credit Limits Not Feasible" on 12-Mar-2026.]

March 12, 2026

I've just done 5 Prompts to fix a dark mode/Light mode issue and its exceeded 5000 Credits, this is non-workable

 

March 12, 2026

to illustrate my point, single prompt

 

Ryan_Anderson
New Participant
March 12, 2026

100% the limits will make it unusable for power users in Enterprise licensing where our companies build complex software.
Even just focusing on building up the complexity of a feature component by component to limit hallucinations sans visual design, I have over over 13K of credits used compared of the 3.5k limit that will be implemented. And that is all for ONE PROJECT where I generally have 3-4 items to be working on in parallel.

Meantime, the bulk of our seats have sub 100 credits used.

There likely are a few things needed.

  1. Increase limits
  2. Allow credits from 1 seat to be leveraged / moved to another by admins, or at least to a pool that can be opened to power users
  3. We also have Claude licenses at work, allow those credits to be used as Claude is the engine behind your Make files, etc…

 

Otherwise us power users (at least those of us with code experience) will be forced to shift to building in more of a Claude Code model and you’ll lose more users and seat income as we opt for productivity.

Maxter
New Participant
March 12, 2026

I would like to iterate on the previous comments. I am a solo product manager who uses Figma Make extensively since January, and it allows me to not just create a design for my developer, but basically build the frontend code. Without the limit enforcement, I find it extremely useful tool which allows us to ship fast. But the estimated cost is ridicously expensive. If Figma won’t change either the included credits or the credit price, I am definitely looking for a new tool. Even the well-known pricy claude code is much less expensive.