Suggest a Feature

I’m sick of this feature i just want to past objects in a different layer why can’t I do the most basic feature in any design application. Please remove

Am I the only one that finds it annoying to access the Libraries dialog? Every time I need to access it — which is often —, I have to go through Assets → Tiny Libraries Icon or F menu → Libraries. B̶u̶t̶ w̶a̶i̶t̶… n̶o̶ s̶h̶o̶r̶t̶c̶u̶t̶ e̶i̶t̶h̶e̶r̶!̶ 🙈 🤷 Libraries are such an integral part of many working with Figma. When one is updating components, or publishing, or adding a library to a file, many use cases. 🤌 Is it to crazy to think it should have a shortcut and “upgrade” its icon position adding it to the main toolbar? Let’s make this unfairness stop right now! Help me out library peeps, we can stop this madness together! Please up vote and share 🫵 To Figma devs: this feature won’t disturb your next sprint! Surprise your manager, us and the world by correcting years of neglect. EDIT: As pointed out, there’s a shortcut. Changed the text to bump the icon to the main toolbar.

Hi. Every day, I use variables in my design. I spend a lot of time adding my variables to auto layout. It would be very useful if the variable name could be entered directly into the input field without selecting it from a dropdown menu. This would save a lot of time.

I have a design where I need to display prices with 6 digits. When I use the variable type numbers for this, prices appear without thousands separators. I would like to display 61,135.25 instead of 61135.25 Keep in mind that there are different rules for thousands separators and decimal separators in different parts of the world. For example, in Denmark it would look like this 61.135,25. For the clients, their prices shown correct is a big deal. So I can’t use variable numbers for this for now. Something like this would be much welcome 🙂

Hello! Is there a way where we can cherry-pick which changes made in the branch are going to be merged in the main file?

When publishing libraries, it would be cool to have option to “force updates across files” for updates that don’t break things and users don’t have to accept updates. It just updates when they open the file. Then an option to “prompt updates” for library changes that do break things. Users would have to review and accept updates. This would be perfect for string and color variable updates.

Hello. Currently, when dev mode is shared by iframes, it’s not possible navigate in the iframe as dev mode. It basically looks like a non-dev mode iframe. Would be nice have this stuff directly in the iframe instead to be forced to open Figma. Also, would be nice have iframe custom fields easier to use, add code like %26hide-ui%3D1 to any link is painful (and, I don’t understand why %26hide-ui%3D1 on dev mode links doesn’t work). Maybe add iframe options here? NOTE: options should be part of the link for maximise compatibility. Hope it would be considered. Thanks!

If the spacing variable is still connected, it would be easier to adjust it in the nested auto layout group

I wish FigJam AI could read all the content I have on the board or section, and summarise the content. And also to be able to use the AI as an alternative way to search for stuff that’s on the board. Kinda similar to the Notion AI.

Today I can version a full component library file, which is fine, but I wish I could version individual components and add notes for each update (just like a commit in github). I also wish semantic versioning was implement that could assist in building a history log, which in turn could be used to build release notes when the file is published. At the moment I’m highjacking the Component Configuration’s Description box to keep track of the changes. Craziness, right?

When nesting components, we’ve found that the Constraints on the nested component need to be set to Scale (Horiz) and Scale (Vertical), in order to size appropriately as the component dimensions change across devices. Does anyone know if it’s possible to set a default for the Constraints?

When arranging local styles in folders (using the / naming convention), expanding and collapsing them is very tedious due to a very tiny clickable zone, hardly larger than the visible arrow icon. In the screenshot below, the mouse cursor is outside the clickable zone. It looks like there’s enough space to make the clickable zone 30x30px, surrounding the actual arrow.

It would be amazing if users could record a prototype and have the option to export as a gif or video file, similar to Principle. This would be a fantastic tool for product designers creating assets for their portfolio.

Hi Figma, I need your magic. According to the update, when styling doesn’t affect the text style, I hope a future update could cover the cycle of weight. Currently, when I press ⌘+B, it switches to bold and vice versa. What I need is a cycling shortcut, so when I hit the shortcut, it cycles through the weights one by one. For example, if there is a medium weight, it will cycle from regular to medium first, then when I hit the shortcut again, it will go to bold, and so on.

In editor mode, the slice layer is at the top of the frame, but when switching to Dev mode, the slice will automatically be at the bottom. And the size of the material image will be selected by clicking the mouse directly, not the size of the frame. The problem is that it is difficult for developers to select the correct slice size. Because some icon slices are composed of one or more material combinations and attribute changes, especially in many places in the interface that need to be unified in size, the material sizes are different, and designers want to use slices to unify the resource size. After all, the working habits of engineers and designers are very different, and letting engineers manually select slice layers still has a great impact on efficiency. I don’t know how Figma considers the current design plan. It is very inconvenient to directly connect designers and engineers. I hope this problem can be solved.

Hi, since you added linking in Figma I use Copy Link constantly - is there a shortcut key for that or can you please add it to the wishlist? Thanks, Ben

Hi Figma team, I am heavily using the variables in one of my projects and i start to realize that in some interactions, i have more that 15 variable switches and i need to apply that on several actions. As you can imagine this quickly adds up in clicks, so i was thinking… How nice would it be if i can just copy/paste little code snippets… that would save me lots and lots of time in creating advancer prototypes… I am coming from the times when we were still using (adobe) flash and i could do soooo much with code which i would love to be able to do as well in Figma… maybe that is a bit too much asked but for now it would already be super nice to have a code view as well for prototyping so i can save lots of time creating complexer prototypes. Happy to even collaborate if this feature might be considered by the Figma team 🙂 thanks!!

I hope that the plug-in can add notes and custom label classifications, so that when we use the plug-in, we will not need to remember a large number of plug-in names and not know which one to use because there are too many plug-ins in our collection.

Please introduce prototyping components, like input fields that actually work. Ready made drop-down component that sets a selection variable per default, repeaters I can sync to a database or spreadsheet and so on. Please enhance they way we can build conditions and build prototypes with conditional logic.

Although this is a plugin api, in previous experiments it was possible to retrieve the figma object in the browser and perform the same behavior. But it doesn’t seem to be working now. Is it a proactive strategy or an inadvertent defect?

Hi everybody! BACKSTORY: I tried using new fill variable tables for Material design approach and created these variable collections: one for color palettes (e.g. primary90 or neutral30) and another for color roles (e.g. Outline Variant or Surface). I use Color Palette variable in Color Role variable. What I have noticed is that when I detach Color Role variable from a layer, it also detaches a Color Palette variable that was inside. IDEA: I think it would be very cool if the “detach variable” button would detach only outer variable and inner variable would still be attached.

Hello! I would love something similar to code where you can see who last edited a line but at the frame level. For example, if someone changes a gap size from 4px to 8px it would be awesome to know who did that. Even if it was myself and i forgot. lol

Tables and grid patterns are crucial for SaaS interfaces and are used very frequently. These elements are essential for displaying data in a structured and clear manner, which is particularly indispensable for complex applications. Currently, it is very cumbersome to build a manageable table from individual components. This is particularly challenging for those who utilize our design system, as they often need to detach components to expand the table and adjust it to respective data. This issue arises because we can only provide a limited number of columns and predefined table components. Additionally, it is very counterproductive to push components with hidden rows and columns in the layers list, as many of our users do not understand that this component can be expanded in this way. One should be able to add another row with a click, as a stackable component is simply loaded in the background. Proposal: A tool in Figma that functions similarly to an artboard and allows the creation of

Hello, that would be great to be able to add multiple devices to do a prototype (desktop, tablet, mobile) in one page. Currently, we have to create one page per flow, which is annoying as I often do proto on the same page. 🙃 (I can see that this idea has already been shared in 2021/2022 🫣)

This is the absolute worse place to put this think. I have nothing but problems exporting file formats because this thing is constantly in the way. CAN WE MOVE IT or perhaps allow the user to turn it off. Thx