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

thibaud conte
New Participant
March 19, 2026

 I’ve gone over the limit... Two days ago, I spent four hours sorting out a bug with the transitions... I must have asked him to redo it 30 times because he kept getting the colours wrong! It’s impossible to create a design with their new limit! 

Mike Hawbecker
New Member
March 19, 2026

I can understand implementing AI credit system, but what I can't understand is why it would be implemented mid billing cycle and also that it carried over the users existing Credit Usage pre the enforcement of AI credit limits.  As a result, many users woke up to being locked out of their Make files.  Why not implement it in sync with the monthly billing/credit reset cycle?   I knew this was coming but assumed users AI credit balances would be zero’d out upon initiating it.

Like others, I share concerns about the credit pricing model.  1000 extra credits for $25/mo seems like it will not go far, especially considering how many credits you eat up wresting with the AI agent to do what you ask.   It’s an amazing tool, but it seems if you are going to use MAKE in any significant capacity, that the AI usage will end up far surpassing the total license fee for everything else in figma limiting adoption, or leaving users to look for other alternatives.

ItzVicky111
New Member
March 19, 2026

Hi my friend,
Its too frustrating because I’m facing the same thing.

The issue is not the existence of an AI credit system. The issue is how Figma is enforcing it. In its current form, it feels unfair, badly balanced, and disconnected from how people actually use Figma Make in real work.

I’ve spoken to designers and project managers who feel exactly the same. The biggest problem is simple: the credits run out far too fast for the paid plan to feel reasonable.

I’m paying for a Full seat with 3,000 credits, but in real use those credits disappear shockingly fast. In another account, including my company account, I personally saw 150+ credits consumed for generating a single .md file that only contained a project or platform status and roadmap update. That is not sustainable usage. That makes the tool unreliable for real workflows.

So naturally the question becomes: what exactly are we paying for? Do i have to top up or get another seat for $16 with 3000 credits instead $25 for 1000 credits

If Figma wants to keep the AI credit system, then it has to make it fair. Right now, it does not feel fair at all. Either:

  • reduce the credit cost per task dramatically, or

  • increase the monthly credit limit for paid users to something that actually reflects real usage.

Because right now, 3,000 credits for a paid Full seat does not feel like a serious working limit. It feels like a demo.

The pricing logic makes even less sense when you look at the numbers. A Full seat is $16/month with 3,000 credits, but 1,000 top-up credits cost $24. How does that make any sense? Why are extra credits priced in a way that feels worse than just buying the seat itself? That kind of model does not encourage adoption where it punishes the people who are actually using the product.

And that is the most frustrating part of all: Figma Make is actually good.

It made work faster. It made certain tasks dramatically easier. It felt like one of the most useful things Figma introduced in a long time. But now, because of this credit enforcement, it feels like Figma took something powerful and pushed it back to the stone age. The users who embraced it the most are now the ones being restricted the hardest.

Nobody is asking for free AI. People are asking for something much more reasonable:
fair pricing, fair limits, and fair value for paid users.

Another issue is that the Full seat is not equally useful for everyone. As a designer and developer, I mainly use Figma Design and Figma Make. The rest is honestly 100% useless to me. So why am I paying for a broader seat structure and then still being blocked on the one AI feature that actually matters to my workflow?

That is where this starts becoming more than just a pricing complaint. It becomes a workflow problem, a planning problem, and a trust problem.

Teams are already building timelines and deadlines around tools like Figma Make. When the feature suddenly becomes impractical because credits vanish too quickly, it directly affects delivery. At that point, there is no time to sit around debating loyalty to a platform. Deadlines still exist. Work still has to move.

And that is why this is so disappointing.

A lot of us genuinely love Figma. This is not coming from people who want to attack the product. It is coming from people who actually use it heavily and want to keep using it. But if this unfair credit system continues, then of course teams will start looking elsewhere. Whether that alternative comes from a big competitor, from China, from open-source, or from closed-source tools does not matter. People will move to whatever is more fair, more practical, and more reliable.

That is the reality.

If this continues, I genuinely believe Figma’s user base will gradually decrease — not because people suddenly stopped liking Figma, but because the current AI credit model makes serious usage hard to justify.

I really hope the Figma team takes this seriously and responds with an actual solution:

  • fix the credit consumption,

  • make top-up pricing logical,

  • increase paid limits to something realistic,

  • or offer a better plan for users who mainly need Design + Make.

At the very least, users deserve a clear response so we can decide whether Figma is still something we can continue relying on or not.

Because right now, for many of us, this does not feel like a fair paid system. It feels like a very useful product being made unnecessarily unusable.

ItzVicky111
New Member
March 19, 2026

The problem is not the AI credit system itself. The problem is how Figma is enforcing it. Right now, it feels unfair and does not match real usage at all.

I’m paying for a Full seat with 3,000 credits, but those credits disappear way too fast. In my case, I even saw 150+ credits used for generating a single .md file with just a project status and roadmap update. That makes Figma Make hard to rely on for actual work.

The pricing also makes no sense. A Full seat costs $16 per month with 3,000 credits, but 1,000 extra credits cost $24. That feels completely unfair. It almost looks like active users are being punished for using the product more.

What makes this worse is that Figma Make is actually very good. It really helps speed up work. But with this credit system, it feels like something useful has been pushed back to the stone age.

Nobody is asking for free AI. We are asking for fair pricing, fair limits, and something that actually makes sense for paid users.

As a designer and developer, I mainly use Figma Design and Figma Make. The rest of the Full seat is honestly not useful to me. So paying more and then still running into heavy AI limits is frustrating.

If this continues, many teams will start looking at other tools, whether they are open-source, closed-source, from big competitors, or even from China. That is not because people want to leave Figma. It is because they need tools that are fair, practical, and reliable for real deadlines.

I really hope the Figma team takes this seriously and gives users a fair solution. Right now, this system makes Figma Make much less useful than it should be.

Seems like the Figma Make is just a showcase that as for fun we can use it but not fit for individuals and the startups who cant affort, this is completely unreliable feature. 

Kenny W
New Member
March 19, 2026

REALLY HOPE, They’re still testing the waters, but that’s exactly what makes the pricing strategy problematic. When models and workflows are still experimental, introducing strict credit limits creates friction instead of adoption. Offering something for free and then pulling it back risks undermining trust, since the experience becomes inconsistent and dependent on each individual’s usage patterns.

 

That said, I also see designers using AI inefficiently. Managing credit consumption has a learning curve, and the biggest pain point is the unpredictability—there’s no clear way to estimate how many credits a prompt will consume before sending it. I’ve had single prompts cost 700+ credits, which effectively limits usage to just a mere 5 prompts per month.

 

Overall, the cost feels disproportionate to how design teams actually use AI. Pattern generation is useful, but it’s inherently exploratory and often wasteful by nature. If pricing remains this way, it makes more sense to adapt workflows around these constraints rather than rely heavily on the tool.

P.S. I think 35k is more reasonable amount, up the price or what ever.

Kenny W
New Member
March 19, 2026

Critical bug, no way to fix, 100+ hours of work gone to trash. 
 

I've exhausted all file-level approaches. The error is a sandbox environment issue@vitejs/plugin-react@6.0.1 in the pnpm store requires vite/internal (a Vite 7 export), but only vite@6.3.5 is installed. The sandbox's vite_runner.ts auto-injects this plugin regardless of project configuration.

This cannot be fixed through code/config changes. The fix requires either:

  • Resetting the sandbox environment to get fresh, compatible dependency versions
  • The sandbox infrastructure being updated to handle this version mismatch

Would you like to try creating a completely new project from scratch, which might trigger a fresh sandbox with compatible dependencies?

Niels Hunefeld
New Member
March 19, 2026

Exactly this Martijn, same issue here. As Design Lead I’m currently the only one using the credits. I’m the Figma Team Admin but can not redistribute the credits from my PM’s (that don’t use Figma Make, but do have a full seat) to my seat when it runs out. This is going to turn sour pretty quick.

It’s also exposing how vague credit calculation is (https://help.figma.com/hc/en-us/articles/33459875669015-How-AI-credits-work#consumption)
 

Simply renaming a label took 14 credits… why? Trouble shooting a messed up date picker took well over 100+ credits, after 5 fruitless attempts, I just asked to scrap and rebuilt from an industry standard react component. 

It’s mildly helpful to see how much credits your prompt used after it’s finished, but If this is my future I think I’ll start using Claude + Console MCP a lot more again. Also makes me wonder how I’m already running Claude Pro but then pay for credits using Claude in Figma Make. Surely there’s improvement possible there as well, connecting your external AI plan?

Guillaume Panot
New Member
March 19, 2026

Yep, they just killed themselves. I am super angry to wake up seeing that. I got a yearly plan which is now becoming useless, as you can see on the screenshot they more than double charge credit to you and I. 

“Hey Figma CEO and CRO, INSTEAD OF INCREASING THE REVENUE by highjacking your customers to compensate your stock market drops when goolgle announced new design tool...you better look at how to give us smarter tools…..LLM cost is going down...not going up! “

They just give a free highway pass to Google Stitch (not yet at Figma level but it s a matter of time), V0,… Claude generates finally nice looking UI , which you can pass to Claude code or cursor. I do the same as Niels .

 

Michelle Buggy
New Member
March 20, 2026

 I got this too! I was out of credits right away, it’s like they went back and took credits for what I did right before the switch!

Ok so i woke up today and can not work on my app due to credit limits.  Figma said they will start to enforce credits on the 18th .  But to my surprise they already enforced all the months credits,  so now i have to wait 8 days to do anything again.  

And yea 3k credits a month is a joke.   I guess Figma going public made them only think about investor and not users.  And yea i am both investor and user.   Today i will short everything a have on Figma cause i see no future in this kids toy.  
 

8% is just the beginning

So Figma has lost 8% in value just today. i guess this is just starting.  

 

Michelle Buggy
New Member
March 20, 2026

I have to agree with everyone. Because it’s iterative, and because you don’t know how many credits each prompt will use ahead of time, it’s impossible to work with. I have used Figma Make to create an incredible app, but now that the credits go so fast, I can’t iterate and fix problems it created in the first place. It should be higher cost of credits for the first creation of the app, then lower cost per iteration of that app going forward. I ran out of credits before I even started. had to buy more, and 30 prompts is not enough when you’re creating an app. I wish there was a cost (like $50/mo) to work on one app, have as many prompts as I want if it’s on one url. 

Also, there’s no clear credit price per AI Model. So, how do I save on credits if I don’t know how much each model will cost?

I have faith in Figma, come on guys, this is not the right amount of credits or credit cost. Not the right way to go about this.