Share Your Thoughts

We noticed that starting March 18, Professional plan seats will include 3000 AI credits per month.After testing Figma Make, 3000 credits feels quite limited. In practice, this equals roughly 50 to 70 prompts per month depending on usage. When building and iterating on prototypes, especially during exploration phases, this amount runs out very quickly.For teams that rely heavily on AI to generate, refine, and test ideas, the current default credit allocation makes it difficult to maintain workflow momentum throughout the month.We understand that additional credit packages may be introduced in the future. However, the base 3000 credits per seat feels insufficient for serious prototyping and experimentation within the Professional plan.Would it be possible for Figma to reconsider increasing the default monthly credit allocation to a more practical amount for active users?Looking forward to hearing thoughts from the community and the F

With slots and composable components, I would love a feature that allows me to create some ready made examples of the slotted components, and have them available in the Assets. For example, our card component with a composable “content” slot; we have 3 layouts that are common in our experience for that slot; ready made patterns. We can make those layouts “components” and have them vended as “preferred instances”… but that seems like a workaround, since these layouts aren’t really “components”… For now, we’ll have a separate Patterns Library, and the designer will just copy-paste those ready made cards into their design. But I think it’d be slick if they can just be available in the Figma UI.

Hi Figma team, Since the recent updates, it’s no longer possible to easily change image fills inside a frame by simply selecting the parent frame.Previously, selecting a frame allowed us to quickly replace image fills contained within its child elements, which made workflows much faster — especially when working with templates, cards, or repeated layouts. Now, the Fill panel only shows the frame’s own background color, and we must manually drill down into each nested element to replace images. This adds unnecessary friction and slows down production. It would be extremely helpful to bring back the ability to:• replace image fills from the parent frame selectionor• provide a quick “Replace image inside frame” actionFigma version 126.1.2 MAC OS This was a very efficient workflow for designers working with visual templates. Thank you 🙏 

In my organization, we have enterprise level Figma or something like that and we use branching.So, without adding too much info, the situation is: The design file linked with library file.And in the design file we have stuff going on.And then we have branches from the design file. The scenario I had this week which cost me sleepless nights and two days of headaches, plus additional work on cleaning the mess out:And yes, I know, I’m partly responsible for that but I will add my conclusion in the end. So one day it was decided in the team that we need to alter one input in the input component (one variant). I made the change. Unfortunately, forgot to first train on a branch, but I thought “hey, it’s just one input, just adding some element to it” (let’s say it lacked an asterisk to be obligatory as a feature of the component).I rolled the change to branches and I think I just updated one of the branches as I

I genuinely don’t understand how Figma continues to dominate given how hostile the experience has become — for both users and developers. The UX is chaotic and non-intuitive: layers buried under layers, controls hidden behind inconsistent interaction models, and navigation that feels designed to fight the user instead of helping them. For many people — especially neurodivergent users — the interface can feel actively exclusionary rather than empowering. It’s hard to shake the feeling that usability is no longer the priority. From a developer perspective, the situation is even worse. The platform is effectively closed. The MCP integration with Claude is read-only, and meaningful mutation requires plugins running inside Figma’s sandbox. There is no serious external API for programmatic design updates. That makes modern workflows — automation, CI-style pipelines, integration with engineering systems — far more difficult than they should be.

After a late switch from Sketch to Figma about six months ago, here is my conclusion regarding the UX of Figma:While Figma has many great features that Sketch does not have (dev mode, way more capable prototyping, variables,…) the general UX of the tool is just sooo bad! Here are the things that annoy me most:Visibility of functions: There are so many functions hidden below a small icon that has no label. Much stuff is hard to find. And what drives me really nuts: When a function is not available, then its UI element (or entry in context menu) is hidden – not disabled! I’m using Figma for UX Design, and it just feels so wrong to use this tool that does not handle UX basics correctly itself.   Library management – publishing components: You can do this from the book button on the top left where you usually update components from other files, but publishing is mixed in here if you click on “This file”. But then you can only publish all cha

Hi there. It would be cool feature like truncation for auto layout. When you do narrower the line (horizontal or vertical) of a layout truncate excessive elements. It’s would be work good for element with set min width.For example, this two last elements truncate, and the other ones fill the space with the rules of layout for this box

Dear Figma,I wanted to bring to your attention that we are in the 21st century, and there are devices specifically designed for designers, such as tablets. I own an iPad, which has an amazing display and can be used with a keyboard and mouse. However, I currently use it only for viewing my designs because Figma, the professional tool I rely on, does not fully function on my iPad. This leaves me with a few options: sell my expensive iPad to buy a PC or laptop, which is less comfortable for me, wait for an iPad update from Figma before GTA VII, or use it solely for watching movies. I wanted to remind you that tablets exist for a reason, and it would be beneficial if Figma could support them more fully.

I’ve already started using the new slots and I find them amazing, but I think it’s very limiting to prevent the use of grid layout. 

I think it would be very helpful to add select funtionality like selection colors for slots in the component instance panel.This would make it easier to quickly target the slot to use the repeat control, and also save library consumers from having to dig through the layers panel to find the slot on more complex components.

Firebender is a coding agent, that many android engineers use. Currently the Remote Figma MCP does not work whenever I configure it. Is there any way to get this to work? I tried:https://docs.firebender.com/context/mcp{"mcpServers": { "figma": { "url": "https://mcp.figma.com/mcp", "type": "http" }}} and I get a message saying to reach out to Figma support to allow Firebender MCP client use OAuth scopes with the Figma remote MCP

It would be really useful to be able to create a branch or a fork in a Make file that can be merged back into the original. Similar to how engineering branches their files. This would allow someone to iterate on an idea without disrupting a prototype that is being used for feedback/testing/presentation.My current workaround is to duplicate the file but the problem is that creates multiple links. I want one link to share with stakeholders/testers that doesn’t change.Thanks for your consideration!

It would be amazing to see if there could be a native figma built-in Bento grid generator with sliders. I know we have the grid function, but this plugin from Akriva is wicked simple to use and would really improve workflows. Would love it if you could select frames and have Figma AI automatically create a campaign ready bento with images.The simple, random, centered and sliders make this such a great easy to use feature that would be awesome to have in Figma. https://www.akrivi.io/presenta

One important feature is missing = Merging cells 😦 Is this feature included as an improvement in the near future?

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’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

Hi Figma team,I’m working with a central design system library that uses variables for colors, typography, spacing, etc. The challenge I’m running into is how to customize those variables per project/client without editing the library file.Here’s the workflow I’d love to have: In the library file, components are built using semantic variables (e.g., Brand / Primary, Text / Default). In a project file, I create local variables with the same semantic structure but mapped to project-specific brand values. I want to be able to relink or remap library variables to my local variables, so that when I update the local variable values, all linked components automatically update. Right now, even if I duplicate the variable structure locally, components still reference the library’s variable IDs

I have a new branch and adding slots to some of libraries container components starting with modals. Set up and implmentation is fine but I added instructions to the slot description panel and I can’t seem to see how the designers are able to read them? When you select a slot in an instance you see two lines of text then it truncates, clicking the content does not open the rest of the instructions in a fly out and there seems to be no way to access the rest of the content. Am I missing something?  

Organization would be immensely helpful if we could create folders for our drafts. I want to be able to organize my drafts into different categories (such as UI kits, Ideas, Wireframe kits, iOS, Android, etc…) so I can find files easily. Right now, the drafts page is a huge jumbled mess and I can’t create Team pages for everything. Maybe something as simple as being able to add ‘tags’ to each file, similar to Zeplin.

Right now it seems like the ‘default’ variant is set based on which variant is ‘upper leftmost’ in the variant container frame. Instead, I suggest decoupling arrangement from precedence, and using the property ordering functionality to determine the default variant. The default variant should simply be the one with the first value for each property, regardless of where it’s placed in the variant frame. This would allow teams to set defaults directly from the properties panel, without having to move components around. See this thread for some more context: How to set defaults / precedence of variants with multiple properties?

If you open a lot of projects the tab strip gets crowded. Chromium browsers solved this by allowing to group tabs, maybe Figma could do the same ?

Figma Make is the best prototyping tool I have seen so far (yes, better, or at least more time efficient, than V0 and Claude Code for now). It also has an integration with Github, which is suuuper cool. Now… it would be REALLY gamechanging, if the connection with Github was a two way sync. If edited code could be pulled back into Figma Make, for team collaboration across multiple platforms. I understand that this is really tricky, because Figma Make can't interpret all types of code… but I'm putting it out there… 

Currently, annotation categories are defined per file.This makes it hard to keep consistency across team projects.It would be very useful to have option for team-level or organization-level annotation categories, managed centrally, so all files share the same list.This would help maintain alignment between designers, developers, and QA.Please upvote 😊