Skip to main content
EmeseB
New Member
May 28, 2026
Solved

32 Credits Deducted for Empty Prompt Output

  • May 28, 2026
  • 7 replies
  • 96 views
Hi Figa Team,
I submitted a prompt yesterday in Figma Make. The AI finished the process and deducted 32 credits, but it did not deliver any results. Please either refund the credits used or make the prompt work, as it is not acceptable to pay for nothing.
Thank you!
Best answer by djv

Hi Emese, thank you for reaching out!

I completely understand your frustration. It’s definitely not expected to run a prompt and not see a result.


Credits are consumed based on the AI process running, which can vary depending on prompt complexity and the model used. Most importantly, credits are not charged if an action fails with no code output generated, so if credits were deducted, it typically means the AI completed some level of processing, even if the visible output wasn't what you expected.


That said, our technical quality team would be happy to look into this further for you. I saw that you’ve also reached out to support directly on ticket #1930128. Your case has already been escalated, and thank you for sharing your prompts and screenshots with the team directly. 

This will help us determine why this is happening for you. Thanks for your patience!

7 replies

djv
Figmate
djvAnswer
Community Support
May 28, 2026

Hi Emese, thank you for reaching out!

I completely understand your frustration. It’s definitely not expected to run a prompt and not see a result.


Credits are consumed based on the AI process running, which can vary depending on prompt complexity and the model used. Most importantly, credits are not charged if an action fails with no code output generated, so if credits were deducted, it typically means the AI completed some level of processing, even if the visible output wasn't what you expected.


That said, our technical quality team would be happy to look into this further for you. I saw that you’ve also reached out to support directly on ticket #1930128. Your case has already been escalated, and thank you for sharing your prompts and screenshots with the team directly. 

This will help us determine why this is happening for you. Thanks for your patience!

EmeseB
EmeseBAuthor
New Member
May 29, 2026

Hello,

thank you for your reply.

The technical team helped me out with this, and everything is working fine, as expected. All is good now.

Best,

Emese

djv
Figmate
Community Support
May 29, 2026

So glad to hear that, ​@EmeseB! Thanks for closing the loop with us here. 

bpanks
New Member
September 1, 2026

hi ​@djv
I am also in same boat. I am loosing tokens but not getting the desired result.

Pls check attached Prompt and Result .. it’s not matching as requested. This is one of the example.
Let me know if you need any more information from me.

 

Best,
Pankaj

 

 

djv
Figmate
Community Support
September 1, 2026

Hi ​@bpanks, thanks for chiming in here! 

I understand your frustration. What you're describing sounds different from EmeseB's case. They had a prompt that returned nothing at all, while it sounds like yours is producing output. It's just not matching what you asked for. Is that right?

Credits are consumed based on the AI process running, which can vary depending on prompt complexity and the model used. Credits will be deducted, when the AI completed any level of processing, even if the visible output wasn't what you expected from your request. 

Two things worth trying: use point-and-click for smaller targeted adjustments rather than re-prompting, and add a guidelines file, so Make has consistent styling and structure to follow. Both tend to cut down on the back-and-forth that eats credits. This Help Center article also breaks down how consumption is calculated. Let us know if these help! 

bpanks
New Member
September 1, 2026

Thanks ​@djv for quick reply. Really appreciate it.

I will try what you have suggested. If you look at the prompts and rendered output is different. So, again n again try/error prompts killing my credits.

djv
Figmate
Community Support
September 1, 2026

Thanks for trying my suggestions, ​@bpanks! 

A few more things that may help reduce the retry loop you’re experiencing:

  • One change per prompt. Bundled requests ("update the nav, fix spacing, change the palette") give the model more room to drift. Smaller scoped prompts are easier to land and cheaper to redo.
  • Revert before you retry. If a result comes back wrong, re-prompting on top of it means the model is now working from the broken state. Restore the last good version first via version history, since that doesn't cost credits.
  • Point at the thing. Again, instead of describing which element you mean, select it with point-and-click, so there's no ambiguity about the target.
  • Skip the model for small edits. For typos, colors, spacing, etc. edit the code directly, no credits used.

More info available here: 8 essential tips for using Figma Make. That said, repeated attempts at the same task with no resolution is worth a closer look, and I don't want you to continue burning credits on trial and error, if something else is going on. To help us investigate, please let us know:

  • The link to the Make file and roughly when you ran the prompts
  • Which model you had selected
  • Whether this happens across files, or mainly on one
  • How many credits the affected prompts used (hover the AI credits icon under each response for per-prompt usage)

With these details, we can help connect your our support team to investigate further.