Suggest a Feature

Hello I am one of the admins for my organisation. We work with a consultancy to build a product so we have many participants from that organisation as guests. It is difficult for me to manage those guests and I would like to make one of their team an admin. Unfortunately this is not possible because Figma model is a close between organisation and teams. Obviously I cannot claim the consultancy domain as one of my own and add it to my organisation… I am sure that ours is not the only organisation that works with consultants. It would be good for Figma to have a more flexible management that does not necessarily equate products and teams with a single organisation/domain. Best regards –ben

Need swipe gesture (left and right) instead of drag on #prototyping, so i can present the exact micro interaction between each card on onboarding screen.

Very strange bug. I can’t add interactions to some objects, and I can’t see any reason why. Basically I have a group with a couple of shapes in it, and when I am on the Prototype tab, it doesn’t show a “+” to the right of “Interactions” and it doesn’t show the link handle in the main area. Above: a normal selection that I can link Above: an abnormal selection that I can’t link. The only other differences between the two selections that I can find are in the Design panel: This is the normal one And this is the abnormal one. Any ideas?

A shorter version could be: "Figma’s new UI is hard to use; hopefully, the official update brings improvements.

It is tedious changing the scope and other attributes of a variable within the Local Variables UI. The panel would be easier to use if there was a right-hand sidebar with the details pre-expanded rather than having to click on the edit button, and then scope.

With UI3 steadily approaching, can we please have the Create Component Set option more accessible? Currently, it’s nested in a dropdown with union and other shape merging tools, but it’s one of my most used buttons. In the current version of Figma, this action is achievable with a single click. Ensuring similar ease of access in UI3 would significantly improve efficiency. A potential solution would be to keep Union and similar tools in the dropdown since they have multiple options, but have Create Component Set next to the other component options. Thank you.

I’ll be straightforward and concise here, as you’ve probably seen in the title. My idea is to have a new option for the Frame size, where it resizes to fit the device screen. The options would include ‘Resize Height Only’ , ‘Resize Width Only’ , and ‘Resize’ (which adjusts both height and width). This feature is useful for testing responsiveness across different devices and platforms (such as mobile apps and desktop). You’ll find this option in the prototyping tab alongside ‘Custom Size’ . Perhaps we could call this option ‘Auto Size’ . Resizing only the height or width is beneficial when the page has vertical or horizontal scrolling.

Hi, our file names often start with 2 or 3 relevant issue numbers, it looks like “UX-1234, UX-456 | And only there the actual name starts”. It was absolutely fine when the name was on the top of the page, with many symbols visible. Especially when you switches between files often, when you see the difference between them somewhere in the end of the file name. But with the name on left panel it’s super uncomfortable and you’d need to go to the cover or wait for tooltip. Well, another example of ruining what works for the sake of… The sake of what, since the toolbar still takes this space?

I would love it if there was a global setting ‘All new component variant groups use auto layout’ or similar and then you can set what the default settings for these are. 99% of the time I am manually adding ‘auto-layout’, ‘fixed width’ on the component group and then ‘fill’ on all variants inside. I am manually doing this with every single component variant group I make.

It would be great if, in addition to defining the scope of the variable properties, you could define the scope of certain variable collections only to the specified components, that way, those variables would not be shown in all scenarios.

Currently, the settings for export in Figma are limited and in turn, limiting. Mobile banners and ads would export to a crisper, higher quality if given the option of exporting at DPI of 300 and/or 450. Right now, having no options other than 72 dpi for teeny tiny ads that are 300x50 and 320x100, means the quality suffers.

When using FigJam, our team are constantly organising post-its so they’re all visible. It would be really useful to create a post-it area where post-its are added automatically, rather than manually placed, into a grid. This would be a time saver and just generally more helpful.

UI3’s Return to instance button is too similar visually to the new toolbar, situated at the bottom as well. I found myself missing the filled style for the Return to instance button, it was easily identifiable and now I had to think for a second what I was clicking. 😵‍💫

If i select multiple layers (inside an Auto-layout) with width property set to “Fill”, and then add an Auto-layout, all the layers inside the new frame will have their sizes set to “Fixed”. I have to manually set the layers back to “Fill” every single time i want to enclose layers in an Auto-layout. This is something i run into every few minutes while working. This is because the new AL layer is automatically set to “Hug”, therefore the children must lose “Fill” property Wouldn’t it be logical, if i apply Auto-layout to layers that are already set to horizontal “Fill”, that the newly created AL layer is also set to horizontal “Fill”, leaving the children to “Fill”?

The UI to manage seats is trash. There is no clear way on how to remove seats. I am being charged to an extra design seat that no. one is using. This is pathetic. How could a company that makes a UI/UX tool provide such a shitty UI/UX for billing?

Dear Figma DX Team, I am writing to provide feedback on the requirement to load fonts asynchronously in order to changes the characters/text of layers with Figma plugins. While I understand the need for font management within plugins, this approach presents significant challenges (at least for me). As a plugin designer, I cannot predict which fonts end users will have in their Figma files. This unpredictability and the need to load fonts asynchronously adds complexity and uncertainty to the plugin development process. I suggest considering an alternative approach that allows plugin developers to handle fonts more seamlessly. For instance, providing a single function that analizes the layers that are going to be changed and loads fonts on demand. Thank you for your attention to this matter.

I was working on effects that all used different colors. I noticed everytime I switch to a new object I had to reopen the effects menu to adjust the color property. I’m curious if anyone else would find it helpful to have a menu persist as you change between like items. Is there a way to know “I want to do a similar action to my last on my newest selection”?

Please do not put toolbar in middle , it make me annoying and can not focus. Let’s keep old version layout. Please… And i pay for Figma organization why i have not AI tool ?

I really miss this group button for components; it’s convenient with a large click area, so I don’t mind misclicking. Especially the reset button, as I work with it every single day with a thousand clicks, so it’s kind of annoying when I have to click on the “more options” button and find the reset button.

I want the actions pop up to stay up even after I changed things inside like checking or unchecking some settings. It should only close when I click out of it

Hi Figma team, I love the “Simplify Instance” feature for helping to streamline complex designs. However, I think it could be even more powerful with some additional controls: Show/Hide Component Properties: The ability to toggle the visibility of component properties would be very helpful for focusing on specific attributes during the simplification process. Show/Hide Relevant Layers: Sometimes it’s useful to hide certain layers when simplifying instances, especially when dealing with deeply nested components. On/Off Nested Component Selection while Hovering: An option to enable/disable the selection of nested components while hovering would improve precision when working with intricate designs. These enhancements would give users more granular control over the simplification process and further improve the overall efficiency of working with instances in Figma. Thanks for considering this feedback!

As an Enterprise admin, I would love to be able to impersonate other members to understand and proof access levels and See how they access/view things. Alternatively, a tag within files or projects with “Admin view only”… something to give better clarity on access levels. Cheers

Currently when reviewing changes, there’s a “resolve all” option that applies to all pages and all changes on each page. However, it would be really great to be able to resolve for all changes on a single page because I might have 2 pages that I made branch edits on, and 17 pages that should maintain the Main file edits. Currently you have to manually select for every change on every page, if you can’t resolve 100% for branch or for main. Which is crazy. Going even a step further, within a page it would even be helpful to be able to select multiple changes and resolve those as a group, speeding up the 1x1 process but giving more fidelity than a “resolve all”. In general I find the UI of the resolve and merge somewhat confusing, and the new designers on my team who are using branches for the first time have come to me with questions about how the heck this works, and for help to make sure they won’t mess anything up when merging. I think this speaks to the fact that it’s fairly hard to

Right now when prototyping in Figma, if your screen has a component with a string in it (think an input field), you can’t set a text string variable on that component. Because components? It’s super annoying bc it means if I want a decent prototype for filling out a form, for example, I have to their break all my components, or make 109209 extra pages to link together in my prototype to show every field filled or unfilled. Would love a little more fidelity in the prototyping tools especially for super common software functions like typing in a field. But maintaining my component library while doing that.

When you’re binding a variable with multiple modes to a component property, the system/UI only reads the first mode as “working” and crosses out the other modes even if they still work. This creates a horror show for trouble shooting. You need some way to not flag items that would work when the mode is switched, or at the very least for it not to be crossed out when that mode is actually active. Binding variables to component properties needs review I think