Share Your Feedback

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

I’m building a stable prototype with Figma Make, and the credit model is a practical blocker. I’m already at ~500 prompts/executions on this project. Figma’s own positioning puts 3,000 credits/month at ~50–70 Make prompts (~43–60 credits per prompt on average). If my workflow needs ~500 prompts, that’s ~21,500–30,000 credits, or ~7–10 months of the included allowance. I’ve also seen 4,250 credits disappear without reaching a usable prototype outcome. The main problem is that because Make is agentic, the cost isn't fixed per prompt and you can't accurately predict it before running. What the agent chooses to do (actions, files, iterations, model) determines billing. Because you can't confidently plan or iterate, it's a budget black box.Make only seems feasible for small demos at the moment, or if you manage to iterate with almost no reruns. Sometimes it is not enough even for a small prototyp

Like many design systems, our current library uses placeholders + instance swap and we would love to switch to slots.The issue: While it’s possible to wrap placeholders in a slot to preserve content in existing instances, that content is no longer preserved when the instance swap property is removed from the original component. As soon as we remove the instance swap property from the parent component, all instances lose their swapped content.This means we have two options:Remove the property anyway and cause major breaking changes to hundreds of projects Accept redundant properties in the already crowded property panel for any component we switch from instance swap to slotsI’d be very happy if we could remove the property, or rather reassign its function to the new slot. 

I use figma for a lot of subtracting and a bit more complex workflows, i would love to use figma’s tool more but working with pages that lag each time i make a change, cause of figma using only a few gb of RAM (I have 32) and only a single core is really annoying. Currently i use figma to design for game interfaces games and changing softwares is really not an options for me so adding this would definitely help a lot.

This update is genuinely one of the most frustrating UX changes I’ve experienced in a professional design tool 😡 😡 😡The new left-hand navigation panel permanently steals ~60px of horizontal space on small screens, which is completely unacceptable. That space is my primary working area — the canvas. I am literally losing room to do my job so a panel can sit there doing nothing most of the time.Yes, Variables, Files, Assets, Find, and Library are important.No — they are NOT minute-to-minute actions.They do not deserve permanent, always-visible real estate. This panel is idle 90% of the time, yet it constantly punishes my workflow.On smaller displays, this feels especially hostile. Instead of prioritising the canvas (the entire reason Figma exists), the UI forces a bulky navigation column that adds zero value moment-to-moment and actively makes precision design harder.

Hello, good day.I’m experiencing serious issues with the new Figma UI update. Many essential tools — such as padding controls — are missing or hidden.Please do not enforce this new version. The previous UI was much better, clearer, and far more efficient for designers.This new version has no advantages, feels confusing, and makes our workflow significantly harder.

Hi all! The new Slot has just been released and I’m looking into replacing the selfmade slots in our library with the new released slots. But I’m already walking into my first problem with the new slots. I have a component where we have 2 slots with the same instance swap property. These slots have boolean variables added to them so they will be hidden/shown on different breakpoint modes.With the new slots I have not found a way to use the same slot property twice in the same component yet, other than keeping our current setup for now, does anyone have a good idea on how to solve this?

Hi, I just want to share a concern.Recently I came across the message of the Figma Make monthly limit, which I would have crossed (when it’s going to be implemented). I just want to mention that the limits are waaaaaay to low. Especially, prompting with AI requires a back and forth of conversation usually because 1) it’s better to ask 1 thing at a time instead of a bunch of things, 2) with 1 things fixed, it can break something else, and so another prompt is required to fix what the AI has broken.This way, creating a decent prototype to test some UX patterns can exceed the limit in just a day or few hours of prompting. Which is kind of not what we want as we might need it practically every week, multiple days. So increase the limit by a ten fold (10x) would be a more acceptable limit. Also, I would love to just pay a bit more every month to just have unlimited prompts. Imposing those current very small limits will not help us at all, i

So the conclusion of today's update is that it is not easy to use and is prone to component explosion. It is only used in specific scenarios and is not as comfortable as using large components and instances. If we add slot content for switching in the future, there may be many gameplay options. Moreover, it is interesting to convert slots into components without using them. However, the problem now is that if I create a slot, about 3-5 components will be generated, which will explode later on

Hi Team,Super excited about slots. I was at the Figma Sydney event yesterday, loved hearing Zoe talk about the process. I’ve been trialling it out today. I notice that we have started putting slots into some of our DS components, particularly helpful for the the input field component, which is roughly 44 px high.I notice that if I have an instance of an input field into my design and try and use the slot in the leading icon spot, if my browser or window is zoomed out too far, I notice that the pink ring shows up but the tiny plus in the middle to add the component. I have to zoom in in order to see the plus icon and then interact with slots, because I notice that the area around or the pink field itself is not directly interactable.  Loving it otherwise!

I have created some slots for columns in my table component and I cannot duplicate them from the parent component instance. Sometimes it works and sometimes it doesn't. To solve this, I have to add a duplicate using the + button, and then they can be duplicated without any problems.

Hello Figma team,I'd like to request the addition of spell checking support for the same languages that are already available in Figma's UI language settings.Currently, Figma only offers spell checking for English, which creates challenges for designers working in other languages. When creating designs with Portuguese content (or any other language), I don't get any spelling error indicators, making it easy to miss typos and grammatical mistakes.Interestingly, Figma already supports these languages for the UI/interface translation:• Japanese (日本語)• French (Français)• German (Deutsch)• Spanish - Spain (Español España)• Spanish - Latin America (Español Latinoamérica)• Korean (한국어)• Portuguese - Brazil (Português do Brasil)Since these languages are already integrated into Figma's interface, it would make sense to extend this language support to include spell checking in the text editor as well. This would create a mo

Comments should be available in the hand tool mode.I don’t want to accidentally modify something so I use the hand tool (also to move through the pictures), but it’s frustrating that I need to switch to the selection tool in order to view and add comments.

I started using Figma Make for a project and the UX was super nice. Easy to switch pages in my react application. Now, the drop down selection button is gone and makes it very hard to navigate between pages especially when its not all connected yet. It was also nice visual to see holistically all the pages you created and can toggle back and forth and from a preview url you generated to within your app.

This is a small nit but please...i’m sure this was made for someone but can there be an option to make it so this button never appears? it adds an additional click, which is so annoying when i am trying to click between to components i am trying to compare the settings inside to. PLUS there is nothing below it! I’m all for whitespace but minimalism that adds work is worse. 

I create a lot of user flows every week in Figjam for my team. In Figjam, under Shapes, and then the “Flowchart” shapes, I can’t find the Delay (half pill) or Display (curved rectangle with a left chevron). Are there any plans to add those soon?

Hey everyone,This has been driving me (and apparently hundreds of others) crazy since 2021: there is STILL no native way to properly move or duplicate an entire page from one Figma file to another.Copy-paste or “Select All” destroys page background/grid/rulers, breaks prototypes, loses comments, turns library styles into local duplicates, and forgets locked/hidden layers. Duplicating the whole file then deleting pages is the only “workaround” — but it’s a nightmare with 50+ page files or design systems.I’m a fellow designer who’s fed up and seriously considering building a free Figma plugin called PagePort that would let you:Export any page (or batch multiple pages) with 100% fidelity (layers, auto-layout, constraints, page props, prototypes where possible) Import into any other open file in one click Choose Move (delete from source) or Copy Smart remapping for styles/variables/libraries + basic prototype r

Here’s an idea. When I open the variables modal window, it’s wide enough to show the little icon to assign another variable to my new variable. I literally, every - single - time - have to widen the modal window by just say 40 pixels maybe, to just be able to click the little hexagon control in the Variables’ value column. Has no one designing this tool ever assigned a variable before? And no, before you say “open it full screen” - I will never use the variables page in full screen unless I’m fully designing an entire token system with multiple modes… I just need to open the modal, assign a static variable to my dynamic variable and I have to move my mouse to the 3px wide spot to grab the window edge and move it just like - no kidding - 10 or 20 px… it’s pretty ridiculous PLEASE SOMEONE FROM FIGMA SEE THIS AND HELP. While on the topic of modal windows… why is the interactions modal designed in one way when it’s just action, but then it rearranges itself int

I had a page “Components” to manage all my local components. There are some new updates in the main file that require me to resolve the conflicts. When updating, it allows me to choose only Main or Branch for ALL COMPONENTS. But some components I need to update from the main file, some I need the current changes in the branch.  

Currently when you’re trying to select variables as an alias, you don’t get any indication of what the ‘value’ actually is. However if you were to head over to your designs/components, and began adding the same variable to the component, the ‘value’ is presented. Which makes it difficult to understand when making updates to variable aliases.In my mind these are using the same dropdown component, so confuses me that they don’t offer the same functionality across different areas of the app. See examples below.Is this something that could be added to the variable modal context? Is there any reasons why it wouldn’t have been added? Variable modal dropdown.​​​

We work on large display but Figma UI doesn’t adjust and shows minuscule panels for Text Styles, Library, Font lists, etc…. See related post below: 

Nested properties do not show up when selecting multiple instances of components Example when selecting 1: Example when selecting multiple: My expectation would be to also be able to set up the decoration left icon when I'm selecting both layers. 

One of the things I used to love about Figma was collaboration. I have a paid Professional plan and my partner has another Professional plan. The thing is that we cannot collaborate in a same file. If I want to do that I have to paid another seat for her inside my team which is ridiculous because she is already paying for Figma.With that beeing said, the first time I fell into the trap and added her to my project. Nothing in the UI told me that I was going to be charged with another full seat (really bad UX and dark pattern from you Figma). There is only a button saying ‘Approve’, that’s it! I lost almost $80 because I added several friends to that single file. Figma, you robbered me.So, Figma, you are losing us, I saw this several years ago with Sketch and the community choose Figma. Now I’m open to explore other tools that allows me to work collaborative with other paid members (I’m not saying that I don’t want to pay).I used to love you, you changed! :(

I personally abuse figma heavily, while I do use it also to create very rough designs for webapps that I build custom for our business. I mainly use it as a personal todo system. everything I ever do gets a small frame in figma where I collect knowledge I need to execute the small project. Now my question/idea is that figma can be used for so much more than design. For example I would love to have AI browse the web through hundreds of different sites and collect me vast amounts of information. And then I would love to have AI put that all into little text boxes in Figma. So I have a vast graph of information.I know figjam already kind of allows this but it’s a fraction of what I have in mind.I want vast agent networks to do extreme reasearch for me. And then on the graph I want to be able to say “lets continout to do research at this node of the graph” and then it would essentially allow me to brainstorm in various directions. For example I