Skip to main content

Why is 1 AI Credit 6x more expensive than a Full Seat Credit?

  • January 21, 2026
  • 6 replies
  • 698 views

pipmo

With the strict enforcement of AI credit limits starting March 18, I’ve been looking at our organization's options for scaling usage. The current pricing structure for additional credits vs. adding new seats seems completely disconnected from reality for power users.

Let’s look at the numbers for a Professional Plan (2026 pricing):

  • Option A: Add a Full Seat.
    • Cost: $16/mo.
    • Cost/credit: ~$0.005
    • Cost for 3,000 credits: $16
  • Option B: Pay-As-You-Go (Overage).
    • Cost/credit: $0.03
    • Cost for 3,000 credits: $90
  • Option C: Shared Credit Subscription. ​​​​​
    • Cost: $150/mo for 5,000 credits.
    • Cost/credit: $0.03
    • Cost for 3,000 credits: ~$90

The Result: It is 5.6x more expensive to buy official "extra" credits than it is to simply spin up a secondary "ghost" seat and use that account for AI generation.

The base credits for my team members who don't use AI are currently "locked" and wasted, while I’m expected to pay $90 for a 3,000-credit overage that could be covered by a $16 seat. We need a way to pool the credits we are already paying for across all seats before being asked to pay 6x the rate for "extra" ones.

Is anyone else finding this pricing logic impossible to justify to their finance departments?

6 replies

Jayse
  • New Member
  • January 21, 2026

Eeesh. 5.6x is crazy. 

“The base credits for my team members who don't use AI are currently "locked" and wasted”

Is that right? 

Ghost seats might need to be a thing indeed. 

 


Eddie Kassaei

The price model, is insane ! I think we won’t be able to use Figma make with this price !
a Simple prompt to modify a table cost me 341 AI Credit ! that means $10 !  not acceptable ! 


Juvon Ang
  • New Member
  • April 17, 2026

A change of button text for default model cost 60 credits.

That is absurd. I might as well edit it manually if there is option for me to do so.

I emailed Figma support and they said it in alignment with how AI credits are calculated.

I like using Figma Make, but it too expensive and their CS are apathy. Will have to look for alternative.

 

 

 


Mateus Godinho

A change of button text for default model cost 60 credits.

That is absurd. I might as well edit it manually if there is option for me to do so.

I emailed Figma support and they said it in alignment with how AI credits are calculated.

I like using Figma Make, but it too expensive and their CS are apathy. Will have to look for alternative.

 

 

 

Actually there is a way for you to manually change it...You see that arrow icon alongside the "+" icon on the prompt box? Click that and select the button you wanna change on the Live view. It will open some options, then you click one of the last icons that suggests code editor. It will open the code side of your app, then just look for the button text and change it manually, without spending any credits. If you know some HTML, you can change anything you want without spending credits.


Jorge_Montero_GFT

I just spent 82 credits on something as simple as telling it to change the copy of two buttons—which the selection tool wouldn't let me select specifically. So, I told Make: "Change the copy of the button texts within the selected DIV."

It wasted a massive amount of tokens just to understand me, only to end up asking if it should proceed with exactly what I had explicitly instructed.

It makes no sense.


[Selected DIV]

User: "The buttons contained in this div will have 'Modify' and 'Duplicate'."

Reasoning: "You have only selected a decorative border element. To change the button text to 'Modify' and 'Duplicate', I need to modify the button elements that are outside of the selected element.

What I need to do: Change the text of the buttons in this component to say 'Modify' and 'Duplicate' instead of what they currently have.

Can I proceed with these changes to the buttons?"

[Used 82 AI credits]”

I already know that. I already told you: it's the buttons contained within this div. You don't need to look anywhere else. I selected the div and told you it's for the buttons inside it. What more reasoning do you need?


 


Jorge_Montero_GFT

98 credits on do nothing