Skip to main content

Figma AI se volvió demasiado cara e inconsistente para tareas simples de UI

  • May 8, 2026
  • 1 reply
  • 8 views

Carmina

He estado usando Figma AI intensivamente para trabajo de UI/UX, especialmente en dashboards SaaS y sistemas enterprise, y últimamente la experiencia se ha vuelto extremadamente frustrante.

Solicitudes simples como:

  • cambiar estilos de inputs,

  • ajustar espaciados,

  • refinar tipografía,

  • actualizar badges,

  • o modificar layouts

están consumiendo una gran cantidad de créditos, incluso cuando el cambio solicitado es mínimo.

Lo peor es que muchas veces la IA cobra los créditos pero NO aplica realmente el cambio solicitado.

Esto obliga a repetir exactamente la misma instrucción 3, 4 e incluso hasta 5 veces para que finalmente aplique la modificación, y cada intento vuelve a cobrar créditos como si fuera una solicitud completamente nueva.

El resultado es:

  • créditos desperdiciados,

  • comportamiento inconsistente,

  • iteraciones poco confiables,

  • y un flujo de trabajo extremadamente caro para usuarios profesionales.

Figma AI tiene muchísimo potencial, pero actualmente se siente poco confiable, demasiado costosa e ineficiente para trabajo iterativo de diseño UI.

Por favor mejoren:

  • la comprensión de prompts,

  • la consistencia de ejecución,

  • las ediciones parciales,

  • y la justicia en el consumo de créditos cuando realmente no se aplica ningún cambio.

Los diseñadores profesionales iteramos constantemente. Cobrar créditos completos por acciones fallidas o ignoradas simplemente no es sostenible.

1 reply

djv
Figmate
  • Community Support
  • May 11, 2026

Hi ​@Carmina, thank you for taking the time to share such a detailed breakdown of your experience using Figma AI!  

I do not speak Spanish, so I hope it is ok that I reply in English. This is incredibly valuable feedback. What you’re describing, especially around repeated prompts, credits being consumed without changes being applied, and the need to retry the same action multiple times, is a real point of friction. I can understand how frustrating that is, particularly in a professional workflow where iteration speed and reliability are critical.
 

Please note that if a prompt fully fails and no work is performed (meaning no output is generated); then, credits are not deducted. But your concern about credit usage is heard. When simple, incremental updates like adjusting spacing or refining typography end up consuming a disproportionate amount of credits, especially when the result doesn’t reflect the request, that creates an experience that feels both unpredictable and costly. Here are a couple of things that may help reduce some of this friction:

  • Break requests into smaller, single-action prompts
    This can sometimes improve consistency and make it easier to verify changes before moving forward.
  • Ask the AI to confirm intended changes before applying them
    For example, prompting it to describe what it will modify first can help catch misinterpretations early.


That said, you shouldn’t have to adjust your workflow this much just to make the tool usable. If you have specific examples where credits were charged but no meaningful changes were made, I strongly encourage reaching out to support with those details. You can contact support via the Support Hub → click Start a chat → type “Report a bug,” and share your impacted file with support-share@figma.com (set to “Can View”), so the team can try to reproduce the issue. This will allow our team to investigate more closely and helps drive improvements.