Skip to main content

Figma Make Ai Credit Limits Not Feasible

  • March 10, 2026
  • 171 replies
  • 4674 views

Show first post

171 replies

Tidal Pull
  • New Participant
  • March 31, 2026

I asked for a usage report, but Figma Make can’t give me an accurate one for the day starting at midnight. I have run through three credit updates and there is no indication of how much was spent, where and why. What I can tell you is that it has spent the day on two problems with one not currently solved. So I’m spending credits into a blackhole right now without any assurances of a positive outcome. This is a horrible way to do things Figma! Either go back to flat rate pricing or provide full usage transparency. The way your doing it right now is rage worthy and a bad look for your business.

 

 

 

Credit/Usage Tracking

The platform (Figma Make's backend) tracks:

  • API calls made
  • Tokens used per request
  • Timestamps
  • Total session usage
  • Your account's credit balance

This happens at the infrastructure layer - completely separate from my conversational memory.

My Memory Limitations

I personally only see:

  • The current conversation (this one)
  • Messages from when you first said "Fix these errors"
  • I have zero access to:
    • Previous conversations
    • Historical usage logs
    • Your past sessions
    • System-level tracking data

The Worklog Problem

When you asked for a worklog "from 12am PST to now," I assumed that meant this session, but you're indicating there was substantial work done earlier today that I can't see.

What I need from you: Can you tell me what major work/fixes happened between 12am PST and when this conversation started? Then I can create an accurate aggregate worklog with proper timelines.

The system knows your credit usage - I just don't have visibility into past work sessions to document them.


Andrey Borisenkov

Same story for me. I’m working on a realtively small app prototype. It has quite a lot of screens which are basically quiz with just checkboxes/inputs and a button. But every small change applied to all of these screens means I’ll burn about 200 credits (just because of the logic of Figma Make) and this is usually a cost of 7-10 small but really meaningful changes to make product better.

My point is that the limit for a payed plan is very low because I burnt all the limits to make Figma change little details here and there and not really the important things for the app. There should be some way to make corrections cheaper after the new version was made by Figma.


Brian Horvath

The AI credit limits are way way too low. I built a prototype while Figma Make was in Beta with unlimited usage. Yesterday I blew through 3000 credits in less than a day. You would think Figma would do it’s research on usage before setting a limit. I must of used 500,000 credits while in Beta.

There should be a unlimited plan for enterprise users. If this isn’t resolved I am moving everything to Grok or Claude AI.

It would be nice if Figma allowed current AI subscription holders (Chat GPT, Grok, Claude) to use their API key’s like Cursor instead of going though Figma credits.


matteo hernandez

I understand that limits need to exist. My concern is with how they’ve been implemented.

My first prompt used about 85 credits, which is already around 2.4% of my monthly credits. For a tool designed for ideation and iteration, that makes the limit feel restrictive almost immediately.

I like the product and have been encouraging others in my organization to use it because it improves communication and speeds up early thinking. But once someone hits the limit, they’re effectively blocked unless an admin gets involved and more budget is added. In a real company environment, that means procurement, approvals, and delays — not a seamless workflow.

It’s even harder to justify if extra spend doesn’t roll over month to month. Meanwhile, many licensed users may not use their allocation at all, while the people who depend on the product most are the ones who get stopped.

The issue isn’t that limits exist. It’s that the current model creates too much friction for serious use and makes it harder to recommend internally. At minimum, there should be a much easier way to exceed the default limit without interrupting work.

As implemented today, this feels less like a guardrail and more like a blocker. If that doesn’t change, I think teams will increasingly look to other platforms with more flexible usage models.

Summarized: I understand the need for limits, but the current credit model is too easy to hit, too hard to extend, and too disruptive for real organizational workflows.


Travis M.
  • New Member
  • April 1, 2026

I agree with all of the sentiments shared. 3,000 credits is abysmally low. I’ve had to resort to downloading my file and creating a new team because I’ll use the 3,000 credits building out a single page. The cost for new credits is absurdly greedy. When one prompt can use 600+ credits, spending $100+ one two changes is downright thievery. Figma needs to fix the credit system or remove it entirely. Otherwise, Make will meet a swift death. 


Jess Darby
  • New Member
  • April 2, 2026

I literally had this experience yesterday:

Me:  *sends screenshot from my engineer* replicate this.
 
Figma: I can't read that, can you explain it to me?
 
Me: you just were able to see a screenshot a minute ago
 
Figma: OH! You're right! I can! Try again.

This is ridiculous. And then the credit burn while trying to get Make to do something it did 5 minutes ago. In addition to it just NOT doing things, and then charging additional credits to fix. I am working on being very judicious with my prompts, trying to do edits myself, and find other ways to conserve usage but even simple functionality like the option to upload an image from my desktop wont work so I am then forced to use AI to do it instead. This feels very… “ick” - is the only way I can describe it.

Eager to hear other people’s alternatives to this. I’m frustrated b/c I am stuck halfway in a process and then pigeonholed by this credit nightmare and it totally blocks my workflow.
  


Jess Darby
  • New Member
  • April 2, 2026

I got very close prototyping an animated hero interaction for a website, and with a single, very thoroughly worded prompt where the same wording got me very far in the previous prompts, Figma Make completely trashed the prototype.

The prototype literally went BACKWARDS to a state even worse than the original starting one in just one prompt. And it’s cost me hundreds of credits, down the drain. Completely unfair that I am paying for the poor outputs of the model, especially after I put so much time into figuring out how to have to word and prompt it as efficiently as possible to get where I did, and so that I don’t use up credits.

This stress doesn’t help me design—it distracts me constantly with a “game” of “am I asking this right/thoroughly/well enough to make this better for my users, or am I about to have another finger of my arm cut off until I slowly have no arm at all (no credits) to make this for them?”

The most effective strategy for prompting is unable to be trusted to return reliable results, even when the same exact wording worked before.

I have to 100% agree with this above statement:

“Charging users for this is effectively asking us to pay to troubleshoot the tool itself.”
 

To put it in different words, we now pay Figma to be their free QA labor.

 

Thanks for devaluing what we do, Figma, to the point where we have to fight even harder to prove the value of what design brings to the table in our work and the organizations. It’s way more than just “making things look pretty”, but now even that’s been made harder to do.



It’s down right offensive for them to provide such a terrible UX when their business is built on experience design… I recently moved over from Sketch for a lot of the work I do, and this just seems like a poorly thought out, half baked money grab where we’re doing exactly what you mentioned ‘paying the tool so we can trouble shoot it.’


Matt_Pearce
  • New Member
  • April 2, 2026

I’ve barely used Figma Make since they swithed on the AI Credit system, it’s woefully inadequate for requirements now. Even though my company pays for my account and had to ‘Top Up’ my credits I’m still looking for alternatives to Figma Make. I feel like i lack a certain amount of control relying too heavlily on Make (An other AI tools), sometimes i can spent 30 mins going round and round prompting and getting frustrated, where in reality i could probably have made that change quicker and easier in the old fashioned way.

The rollout of the whole process was poor in my opinion. Like a lot of people i’ve spoken to they weren’t aware that on the 18th March Credits used up to that point would be considered for their monthly limit, and resulted in no credits left from 18th March onwards, projects frozen until they could convince their company to buy more credits etc.

I fear this is a sign of things to come, even with other AI options. Where you become reliant on AI and then the prices just go up and up. I’ve certainly learnt a lesson to not rely on AI too much and reverted to more ‘traditional’ manual methods, especially for Hi-fidelity/Dev handover. I found Make was great for wireframing, lo-fi protoyping but never got me near where i wanted it to be unless i spent time prompting etc 

50 credits to move a button position, another 60 credits correcting errors and bugs isn’t sustainable with 3500 credits.

-------------------------------------------------------------------------------

Alternatives i’ve looked at are:

Google Stitch for idea generation, alternative layout options etc. Nothing more thant that at the moment.

Paper.design and Claude Code, I quite liking this so far but haven’t really had much chance to use it in anger yet.

Claude code and Figma (Design) I created a basic website and design system in Figma and created a site using Claude Code and Visual Studio, Created a Repo on Github, set up free hosting and a purchased domain name all using Claude code and had a website up and running in a couple of hours. (I have very limited dev experience and thought Claude was excellent at walking me through the process).

I found myself using Figma less and less thorugh this process and just using Claude to design with prompts and quick figma mockups.

Claude seems to be better value for money at the moment, and the recent Figma integrations and skills seem to be promising. But as i mentioned previously I’m becoming more and more wary of relying on AI


JF Boisvert
  • New Member
  • April 2, 2026

Hi Figma Team,

I wanted to share some candid feedback regarding the token-based pricing for Figma Make.

I’ve been actively testing the feature this month, and I want to start by saying that I genuinely like it. It’s powerful, fast, and aligns well with how I think and work as a designer. There’s real potential here.

However, the current pricing model is making it very difficult for me to continue using it in a meaningful way.

I work full-time in Figma, and I exhausted my initial credits in a single day. I then purchased an additional $120 in credits—those were gone quickly as well. I increased that to $240, and again ran out, this time with 10 days still left in the month.

At this point, my monthly spend on tokens has exceeded what my Figma seat costs for the entire year. That’s simply not sustainable.

Even when I try to be efficient—using tools like GPT to generate JSX foundations and reduce iteration cycles—I still exceed my credit limits. The reality is that for someone working deeply and continuously in Figma, this model scales too quickly in cost.

As it stands, I’ll likely have to abandon Figma Make for day-to-day work, or limit its use to very specific cases like hosting or presenting prototypes. That’s disappointing, because I do see the value in what you’ve built.

I’m sharing this in the spirit of helping you refine something that has a lot of promise. I’d love to see a pricing model that better supports heavy, professional usage—whether that’s through caps, bundles, or a more predictable subscription tier.

Thanks for listening, and I hope this feedback is helpful.

Best regards,  
Jean François Boisvert


Justin Ryea
  • New Participant
  • April 3, 2026

Hey everyone. I want to share some feedback on the current Figma Make credit system, and provide a literal step-by-step escape route for anyone else who feels trapped.

I absolutely love(d) Figma Make for the initial 0-to-1 build. Figma successfully built "vibe coding" into their platform, which is incredibly cool. But what isn't cool is blocking users from actually using it that way. The entire value proposition of Figma is rapid iteration. Yet, I hit my third lockout this week after spending nearly 100’s on credit expansions in a two weeks.

Almost all of those credits were spent on debugging, QA, and fixing logic—not building new features. The usage-based pricing essentially acts as an "iteration tax" that actively discourages you from polishing your app.

If you are building a complex web app, you have to eject your code to finish it. I was intimidated by this at first, but Claude Code and Gemini (which gave me easy instructions) literally walked me through the entire process. It was shockingly easy—mostly just clicking "Next" and signing up for a few free accounts.

Here is exactly how I escaped the credit burn and took my app (which uses Supabase Postgres, Paubox, OpenAI, and Claude APIs) fully local for a flat rate - it took me 15 minutes total to move this and i am NOT an engineer.

How to Eject and Keep Building

Step 1: Download your code Go to the Code tab in your Figma Make project, click Download code in the upper right, and unzip the file on your computer. You now own your source code.

Step 2: Open Claude Desktop If you have a Claude Pro account, you have access to the Claude Desktop app and its autonomous Code agent. Click Select folder and point it at your unzipped project. (Tip: Set it to "Ask permissions" so you can approve its changes).

Step 3: Connect your APIs securely Tell Claude: "I just exported this from Figma Make. Tell me what environment variables it expects for my database and APIs, and help me create a .env.local file." Claude will find exactly what Figma named your variables. You just paste your live keys for Supabase, OpenAI, Paubox, etc., into that file and save it.

Step 4: Run it locally Ask Claude to run npm install and start your development server. Your app will now run on localhost in your browser. You can now prompt Claude to fix bugs, refactor 100+ files, and vibe code endlessly without a meter running.

Step 5: Host it on Vercel Once it works locally, you need a place to host it so others can see it. Claude walked me through deploying to Vercel. You just connect your GitHub account, click "Next" a few times, and Vercel gives you a live URL and free Preview URLs every time you update the code.

The Cost Reality Check

Staying in Figma Make (The Walled Garden):

  • Figma Pro: ~$15/mo

  • Credit Expansions: ~$500/week (if you are aggressively debugging/QAing a complex app).

  • Result: Constant anxiety, blocked workflows, penalized iteration.

The Ejected Local Workflow:

  • Claude Pro: $20/mo (Flat rate for the Desktop Code agent).

  • Supabase (Postgres/Auth): $0/mo (Free tier handles the prototype phase effortlessly).

  • Vercel (Hosting): $0/mo (Hobby tier is free and handles deployments automatically).

  • External APIs (OpenAI, Paubox, Claude): ~$5-$10/mo (Pay-as-you-go API usage costs literal pennies compared to visual builder block credits).

  • Result: ~$30/mo total. Total code ownership, secure API handling, and unlimited iterations.

To the Figma team: The engine you've built is incredible. But until there is a predictable, flat-rate tier that allows developers to QA and debug without financial anxiety, ejecting to a local environment is the only viable way to finish and iterate on functional prototypes.

After providing this exact feedback in the forum multiple times over the past two weeks with zero replies from the Figma team, I am officially done using Figma Make for iteration. Moving forward, Figma will strictly be used for our style library (and honestly, maybe not even that).

If anyone else is bleeding credits right now, grab your .zip file and open Claude. It is so much easier than you think to take your code back!


Dave Cowing

We are a small agency, that makes use of Figma.  We’ve started using Figma Make and have seen great benefits.  However, the credit consumption is really high and the model, with a very low monthly pay as you go limit, doesn’t work well for us, given significant variability in need month to month.  As it is, we’re forced to commit to much higher subscription to monthly AI credits to meet our needs and I see us having many months where we don’t need that amount.  I’d rather pay slightly more for the flexibility.  

Figma, can you get rid of the $2K cap on the pay as you go and let organization subscribers set that as they see fit/need?

 

Anyone else struggling with this or have answers?  For us, this may push us to other tools for vibe designing, and utilize the Figma MCP server for when we need to hand design elements.


Viktors
  • New Participant
  • April 8, 2026

I would like to raise a concern regarding the credit system used in Figma Make AI.

Currently, the way credits are consumed feels disproportionate to the actual value delivered per interaction. A single prompt can consume a significant number of credits, even when the result requires multiple iterations to reach a usable outcome.
 

AI-assisted design tools should encourage exploration, refinement, and iteration. However, the current credit model discourages this behavior by penalizing users heavily for each prompt, regardless of output quality or usefulness.

It would be much more reasonable if:

  • Credit consumption per prompt was lower, or more predictable
  • Credits were tied to successful outputs rather than attempts
  • Iterative refinements (small changes) consumed fewer credits than full prompts
  • Users had better transparency on how credits are calculated before execution

At the moment, the system feels restrictive and misaligned with real design workflows, where multiple iterations are the norm rather than the exception.

 


Octavian_Dumitrescu

The Figma product is fantastic, but even if they gave you 10,000 credits instead of 3,000, it would never be enough! In just three days’ work, you easily go through 10,000 credits (so 50% of that goes on fixing bugs and dealing with the content they add without asking). I’d rather stop using figma because it uses up too many credits, and so under the new system it’s financially unsustainable. What a shame.

 

i used 300000 when it was free but i built something cool


Amr Mahmoud
  • New Member
  • April 8, 2026

Hi Figma Team, I’m really enjoying the new 'Make' features, but I’ve found that the 3,000 credit limit is quite restrictive for a professional workflow. In a single productive day, it’s very easy to exhaust that amount.

I believe increasing the limit—perhaps to 20,000 or more—would make the tool much more viable for power users. Currently, the pricing feels a bit high compared to other specialized AI tools on the market. Would love to see more flexible options for high-volume users!


Dave Cowing

Completely agree with everyone about the credit model.  1. work consumes far too many credits, 2. the limits an organization user has are not feasible for complex work - have topped out the pay go and the monthly numbers, and now have to talk to sales??  As an admin, I should be able to set my users up for success. 

Recommendations:

  1. Make the platform more efficient from a consumption POV
  2. allow a much higher ceiling on PayGo → our needs are lumpy, so paying high annual fees for a heavy month just doesn’t work
  3. allow a much higher monthly number that admins can set without sales.
  4. Lack of a decent rollback mechanism is a real issue, please add bi-directional connection to github.

 

For our next project, we’ll look at other models - to be honest there’s no real benefit of Figma Make over other models/platforms.   


UserFiore
  • New Participant
  • April 9, 2026

I just spent about 500 credits trying to add an SVG file.

 

70 credits just to confirm “Yes I want to add an SVG File”

and 166 credits to “upload it”

then another 70 to “fix it’

and another 166 to try and upload the SVG file again.

 

AND IT STILL DIDNT WORK LOL.  File still won’t show after spending 500 CREDITS!!! THIS IS A SCAM!


Manoj S
  • New Member
  • April 9, 2026

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.  

Figma Credit scam. Earlier there were 86 credits. Then I gave prompt. Usage credit for said Prompts were 40. & then it shows 0 credit left


Dave Cowing

I am so frustrated right now - Figma Make credits are the worst.

 

I have an organization license and 1 user doing a complex project in Figma Make.  We’ve burned through the per seat credits, maxed out the $2k paygo credits, maxed out the monthly credits and are now stuck - they want you to send a note to sales after this point.  Sales hasn’t contacted me in 18 hours and we have a major project bottle necked by this.

I’ve had to go an create a whole new account to have new limits and will have to move the project over there.

 

On top of extremely expensive credits, Figma is not letting me buy more that I’m willing to.  This is the absolute worst setup.  We will probably not use Figma Make for future projects, as this lack of control is not acceptable to my business.


Arun Subramanyan

Hi everyone,

We’ve been using Figma Make for the past one year, and one key concern has become more serious after the shift to token-based pricing.

When this was a free feature, we didn’t mind occasional errors or inconsistencies. However, now that it’s priced, every issue directly results in token loss—and that’s a problem.

There have been multiple instances where tokens were consumed, but the expected output was either not visible or not usable in the UI. In such cases, we end up bearing the cost for issues that seem to be on Figma Make’s side.

What makes this more challenging is the lack of a clear or reliable escalation path for these situations. There’s no straightforward way to recover tokens or get timely resolution.

This raises serious concerns around:

  • Cost accountability
  • Reliability of the system
  • Support and escalation process

For product teams, this makes it difficult to rely on Figma Make for long-term workflows. If this continues, we may have to gradually move away from using it.

Would like to understand—are others facing similar issues? How are you handling token losses in such cases?


mbanks
  • New Member
  • April 10, 2026

Any one find an alternative? These new limits are way too low… As a PM, I am now just starting to design/build else where. I’m cancelling my subscription and moving my team to something else.  Any recs?


Justin Ryea
  • New Participant
  • April 10, 2026

@mbanks very easy to eject your figma make projects locally and use claude code which is an order of magnitude more powerful - or just use figma for the first few design screens  - get that dialed in and switch over.  I find claude code to be equal and in some cases superior when it comes to design and much faster when it comes to resolving bugs. I put some instructions a few rows up but all depends on what you’re trying to do. in order to share designs i did need to figure out a solid hosting solution so setup a git, vercel, and supabase account (all free for light usage) - claude code walked me through it all.  Very easy. 30-60 minutes and you’re off to the races.  Also using Codex a bit now too connected to the same project.