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

JaredSF
New Member
March 23, 2026

I’ve spent the morning looking at Claude Artifacts and am getting very acceptable results for prototyping and in some cases better than in Make. For the max tier package, pricing is more than a monthly make subscription, but its predictable (budgetable) and would still come in at much less than what we estimate we would need to spend with Make. 

It looks like with MCP that you can go back and forth so I think thats the way we are going to go, so we can go from design to code with a single tool.

Olivier15
New Participant
March 23, 2026

The limitless capacity was amazing and now they just provide us with a mere 3000 credits (which is enough for 1h prompting or less) and it’s also shared usage or what? lol - 1 member of the team just used up all our credits in no time. And on top of that, there is no roll-over like in other tools like UX Pilot. I think Figma will lose a lot of AI users very quickly this way. I will use Claude & UX Pilot now more than I will use Figma, and potentially this will just make Figma redundant anyway, so why not just go to Pencil or Paper, or Subframe. They offer better code too. 😄 So, Figma please, don’t dig your own grave, by forcing us to leave for alternatives.

Joris Re
New Member
March 23, 2026

Check guys, great posts here! 
My Figma usage and figma workflows are ending as well, with ai being able to design in code directly with openAi or claude, there is less need for Figma design to exist. 

Just my fair notes on using Figma Make in the trail period,... it was great!, but the sudden enforcement of AI credit limits basically froze my workflow mid‑stream. I’m already paying for a full Figma seat, yet I’m now metered and blocked precisely at the moments when I need to explore, iterate, and refine... the core of how real product design works. Worse, I’m burning credits not just on meaningful work, but also on reruns and fixes when the AI ignores my design system or produces unusable output. It feels like I’m being charged twice for the same outcome, and the result is “credit anxiety” instead of creative flow.

AI in a design/product creation tool should amplify creativity, not punish it. Please rethink this model so we can iterate without fear: don’t charge for failed or clearly broken generations, make refinement of existing results far cheaper, and offer a true exploration or sandbox mode where we can design freely and only pay when we decide to commit something into production work. Right now, the pricing structure is actively working against the way good, thoughtful design gets made.

New Participant
March 24, 2026

Hello,

I am a user of Figma Make and would like to share my feedback regarding the recent credit-based usage model.

First, I want to emphasize that I consider Figma Make to be a highly innovative tool. The ability to rapidly transform ideas into structured UI and extend them toward implementation represents a significant shift in how digital products can be created.

However, the introduction of the credit system has significantly changed my workflow.

Previously, my process relied heavily on iterative exploration—quickly generating, modifying, and refining ideas within Figma Make, often progressing in a near one-step flow toward frontend output. This allowed for high-speed experimentation and creative discovery.

With the current credit limitations, this approach is no longer sustainable. As a result, my workflow has shifted toward a more structured pipeline:

  • Pre-planning and structural design through notes or sketches
  • Generating only finalized UI concepts in Figma Make
  • Using external tools such as GitHub Copilot or OpenAI Codex for backend implementation

This shift has clearly improved the precision and structural quality of my outputs. However, it has also significantly reduced my ability to rapidly explore and iterate on new ideas.

As someone who is not a professional designer or developer, experimentation and trial-and-error are essential parts of my process. Limiting this exploratory phase makes it more difficult to learn and create effectively. I also believe that professionals in design and development may experience this constraint even more strongly in their workflows.

In my view, the core strength of Figma Make lies in enabling fast exploration and iteration. The current credit model, however, restricts this key value.

I would greatly appreciate it if you could consider improvements to the credit system, such as:

  • Providing a more flexible or reduced-cost structure for early-stage exploration
  • Lowering the credit cost for iterative edits and minor changes
  • Introducing a lightweight credit model for simple or incremental requests

I strongly believe in the potential of Figma Make and hope it can evolve in a way that continues to support creative exploration while maintaining efficiency.

Thank you for your time and consideration.

Best regards,
A user

Iikka Koistinen
New Member
March 24, 2026

I’m in the same boat as you. We have someone from Figma coming to talk with our organization about leveraging AI, and I’ll definitely be bringing up this credit issue right away.

That 3,000 credit limit is frankly ridiculous. As mentioned, it lasts only a couple of hours at most and a significant portion of it ends up being spent just fixing bugs.

Kyle Martin
New Member
March 24, 2026

Pricing is ridiculous. We’re going to use Claude Code to extract the code from our Figma Make prototypes and then completely move over Claude.

You guys have failed and lost many customers.

wilderlovedesignco
New Member
March 25, 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.

Justin Ryea
New Participant
March 26, 2026

Figma Team,

I'll keep this concise because I suspect you're hearing versions of this more often than you'd like.

Three times now, I've been locked out of designs that errored out on your end — not mine. Each time, credits burned while I tried to fix problems your platform created. That's not a pricing model. That's a penalty for using the product.

Our admin is in Europe. Time zone gaps make resolving access issues even more painful. The friction is compounding.

So here's what's happening: I'm evaluating Stitch for web app prototyping with Firebase integration. Not as a experiment — as a migration plan. And here's the irony you should be losing sleep over: you're the ones pushing your customers toward these alternatives.

The macro picture is even worse for you. AI is compressing the cost of creation at an extraordinary rate. I can generate a 25-page research paper in 20 minutes with a subscription I'm already paying for. The same compression is coming for design tooling. A competitor who undercuts your pricing by 70-80% isn't a hypothetical — it's an inevitability, and the only question is timing.

The seat model is breaking because organizations need fewer seats. Pivoting to value-based pricing while your product burns credits on its own errors is a catastrophically bad look. The stock is reflecting exactly this.

There's still time to get ahead of the exodus. But that window is closing faster than your quarterly reports suggest.

Regards,
Justin

thibaud conte
New Participant
March 26, 2026

I'm in the middle of deploying my Figma site and I've realised there's a mistake with all the buttons – he's got them all mixed up...! More errors! Do we have to pay for this!!!!!!

Missssss
New Member
March 27, 2026

Hi everyone,

I’m experiencing an issue with my Figma AI credits and wanted to see if anyone else has noticed something similar.

I used to use Figma AI quite heavily, and my credits would last much longer. Around 30–40 days ago everything was working perfectly. I even completed several projects during that time without running into any credit limits.

However, recently my AI credits seem to run out much faster. Now I can hit the limit with only about half a day of use, which never used to happen before. Previously I was using it much more heavily without any problems.

The only change on my side is that I switched from using Figma on a MacBook to using it on a Windows machine. Other than that, I’m using the same account and working in almost the same way as before.

Has anyone experienced something similar? Or could this be related to a recent update or a change in how Figma calculates AI usage?

Thanks!