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

March 17, 2026

Im out, moved all front-ends to vercel, kept the supabase backends, GitHub holds the repos, and im using opencode to do the prompts, its quick, accurate and i have made 10 times the progress in 24 hours then what i did with Figma, there are alternatives, the cost point is very different as well as the ability to use any models i want without restriction. Its actually made the deploys much more efficient with extended error checking.

@kitwalker14   I was planning the same.. how do you manage the image bedding issue from Figma? the links in repo apparently will never work if directing to figma still.. 
 

I just got opencode with the models in github to prepare the repo for vercel, it did the whole job from start to finish, once done, get the step by step from opencode for the deploy in vercel, deploys in seconds

martijnmartens
New Member
March 18, 2026

Figma: 

I think you just killed figma make with this ai credit pricing model...

I’m a huge fan, now it’s a hug dissapointment and my company needs to pivot ASAP.

I blast through the credits in 1 hour using figma make doing pretty basic stuff (deleting sections, adding some). Buying credits is crazy expensive compared to the output you can achieve with it. We now have 2 / 3 big projects relying on figma make for design. I now have to find a replacement ai designer tech stack. Going back to tinkering with regular figma designs is not really an option given the time saved with ai tools.

Honestly, you need to fix this ASAP or my prediction is you will loose all your users from figma make. 

[Moderator note: This post was merged from “AI credits: what happens when we reach the limit?” into "Figma Make Ai Credit Limits Not Feasible" on 23-Mar-2026.]

New Participant
March 18, 2026
  • Previous usage: ~200,000 credits / month

  • Current allowance: 3,000 credits / month

  • Reduction: ~98.5%

This is not a marginal adjustment.
It effectively makes the previous workflow non-viable.

Additionally:

  • Average generation cost: ~100 credits per run
    → Current allowance supports ~30 generations per month

In practice, this means:

“Even basic iteration and experimentation are heavily constrained.”

2. The Core Problem: Not Cost — But Loss of Exploration

The value of Figma Make is not just generation. It lies in:

rapid iteration → comparison → selection → refinement

However, under the current system:

  • Failed prompts = immediate cost loss

  • Iteration = expensive

  • Exploration = discouraged

As a result:

“The process required to reach a good outcome is effectively blocked.”

This is not just a pricing issue.
It is a fundamental UX constraint.

3. Practical Impact (Real Workflows)

This limitation is especially critical for:

  • Admin dashboard design

  • Repetitive UI structures

  • Multi-variant exploration

  • Rapid MVP prototyping

These workflows inherently rely on:

“Generate multiple options → choose the best → refine”

The current credit model makes this process impractical.

4. Implicit Assumption in the Current Model

The credit system appears to assume:

“Users will generate correct or usable results in a single attempt.”

In reality:

  • Most outputs require iteration

  • First results are rarely production-ready

  • Prompt refinement is part of the workflow

Therefore:

The current system does not align with real-world design behavior.

5. Suggestions for Improvement

Rather than simply increasing credit limits, structural adjustments would be more effective:

1) Credit Rollover

  • Allow unused credits to carry over

  • Enables batching exploration when needed

2) Low-Cost / Low-Fidelity Mode

  • Provide a cheaper “exploration mode”

  • Supports rapid iteration without high cost

3) Team-Based Credit Pooling

  • Shared credit allocation across teams

  • Reflects actual collaborative workflows

4) Experimental Free Tier

  • Limited but repeatable testing environment

  • Reduces friction for iterative use

6. Outcome of the Current Policy

The current structure leads to:

  • Light users → minimal impact

  • Heavy users → reduced usage or churn

In other words:

“The users who extract the most value are the ones most likely to disengage.”

7. Closing

Figma Make is a powerful capability with clear potential to improve productivity.
However, the current credit system significantly limits its practical usability.

This is not about cost sensitivity.
It is about alignment between product design and real workflows.

I’m interested in hearing how other heavy users are adapting to this change.

New Participant
March 18, 2026

AI-generated output is inherently iterative, not deterministic.
Charging per attempt assumes correctness on the first try — which contradicts how generative systems actually work.

Figma Make is positioned as a tool for rapid, natural-language-driven creation,
but the current credit model penalizes the very iteration that makes this possible.

This isn’t just a pricing issue.
It’s a misalignment between product design and real-world usage.

New Participant
March 18, 2026

Figma Make currently allows users to select different AI models, but there doesn’t seem to be any meaningful difference in how credits are consumed based on that choice.

If model selection is exposed to users, it would make more sense for credit usage to reflect that — allowing users to balance cost vs. quality depending on their needs.

Introducing a transparent, model-based credit structure could improve both usability and trust, while giving users real control over how they use AI features.

JaredSF
New Member
March 18, 2026

Hi,

cant agree more on this.  We are have been actively hammering make before the credits were counted.  But the majority (40%) of credits are to either fix issues cretaed by make or where it says its done something and hasn’t.

 

There doesn’t seem to be a credit refund system so this as a business model doesnt make sense.  We would be more than happy to pay a larger amount for and all you can eat subscription with reasonable daily limits (500?)  much like Claudes subscription model.

 

That being said we are now seriously considering the viability of make for even basic wireframing

UserFiore
New Participant
March 18, 2026

3,000 is too low. It uses up credits just asking “would you like to implement” and then I have to respond “yes” and then it uses even more credits to implement. 

 

So why are we being charged twice just for replying “Yes, implement the change”?

 

 

Jeff_Hart
March 18, 2026

Well that was fun while it lasted. Great job, Figma! You managed to build up a huge customer base just so you could piss them off and destroy you business in a single day. Kudos, if that was your goal. Mission accomplished.

On the day you started counting credits, I burned through my monthly limit within 5 hours. Your model is completely unrealistic and downright greedy. Either you wait until you’ve perfected it to launch such a feature, or give us 20x the credits, or significantly lower the price. Until you address this, it’s on to better things for those of us with a big to do list and no bottomless pot of gold to draw from. You’re not the only game in town.

Eutimio Garcia
New Member
March 18, 2026

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.  

Patrick Thommen
New Member
March 18, 2026

We’ve been running a test phase beforehand, and while Figma Make is powerful, its limitations significantly reduce its potential for long‑term use. During this roughly two‑week test period, a single person using it on a normal daily basis consumed around 269,000 credits.

For comparison: the highest available credit package offers 15,000 credits for about $350. It’s easy to estimate what 269,000 credits for just one person would cost.

In short: extremely expensive.!

Usage of about 2 weeks...
Highest pack is 15k credits for 351...