Suggest a Feature

I really love FigJam! Would like to see some more facilitator oriented features, like a stopwatch/timer. Also possibility to set number of votes together with color for users to use at certain stages in a workshop.

In the pre-update version Publish Library was always enabled. This way if Publish did not detect any changes I could open it, click “Update all pages”. This would trigger it to detect changes. With the new version enabling/disabling is not working. If I make changes to the library, publish the changes, there is a 50% chance of the Publish ‘blue dot’ showing up and Publish menu item becoming enabled in a file. If I switch pages then sometimes it forces the changes to be detected. Why not keep publish enabled all the time. at least that was a sort of workaround that I could live with. This new behavior is harder to live with. Would be nice to have a keyboard shortcut for publish - I publish many times a day to many files.

In 2019, Figma released a feature that allowed users to copy the link of a history version of a design file and share it with others. However, it seems like the link is not working now? I’m only able to link to the page, but not the exact version of the file…Anyone else experiencing this issue?

When you click to set a max/min height, the field to input the number shows up below the max/min width. This is awkward as you expect it to show below the height field

Hi, What about including other formats but devices in the prototype settings? Such as social media formats? This would aid the community to showcase work on platforms such as LinkedIn etc. in the quest standing out in the professional market. Cheers! mol.

Would be nice that clicking the + sign on a sticky would move subsequent ones. User could define how they are organized (columns or rows) I’d imagine many would use sticky in an organized order. Adding a new idea in a specific spot is common, having to manually rearrange a whole board is tedious.

Hello, Figma community! I would like to raise the issue of the ruler in Figma, as I consider it an important tool that I use regularly. What is wrong with it and what is it missing? In the new Figma interface, the vertical ruler has been shifted to the left of the screen, which, in my opinion, causes inconvenience and makes it difficult to use. I suggest that developers return the ruler to the left side of the interface, but inside the block, and not next to it. This concerns the inconvenience of using the ruler. Now let’s talk about what this tool is missing. It would be useful to add interaction with the rulers on Alt to determine the exact distance between them, rather than using a calculator or creating a block, as I do. A ruler would also be useful for creating footnotes with the dimensions of the interface elements. There are plugins that solve this problem, but I think that such a function should be built-in and more convenient. A little from myself, you made an awesome to

I would love the feature, that when you double click a frame, that the resize options of that frame shows up. Sometimes I have really long frames when I am designing for mobile. When I want to make the frame longer to add more content I have to scroll up and click on the name of the frame. Double click to resize frame would be a little time saver

Thanks to the developers from all the left-handed people in the world who, like me, cannot change the keys to ungroup. Previously, Ctrl + Shift + G worked great, now when ungrouping every time it is very difficult to press Backspace + G

I work alot with the comments panel open and use Esc to exit editing of text layers but esc closes the panel and I have to go find the comment and open and reposition again. It’s very frustrating

Hey everyone ! I love Figma, but i have a problem. I can’t save a custom frame size. It would be great if we can save our own custom frame size for different projects. I don’t think it’s “hard” to implement, but it would be very useful. Thank you by advance !

You have several modes, the first is to add a comment, the second is to select something to add a comment to it, for simplicity you can select a group by selecting it in order to add a comment to the group, and simply click on the nested layer to bind the comment to this layer now the situation looks like this: with the ungroup option all comment bindings are lost, also if an option is added to the layout and so on, this is very inconvenient, it is not possible to use comments in conjunction with groups and autolayout, and everything is built on this… binding a comment to a group without selecting a group is an incorrect binding

Hey Figma Community! I’ve been thinking a lot about responsive design workflows lately and how we can make them more dynamic and flexible. Specifically, I want to talk about the resizing options we have today—those trusty hug, fill, and fixed values we use for horizontal and vertical resizing. While these are solid, they could be even more powerful if we had the option to tie them into variables. Why Variables in Resizing? We already love using variables for colors, spacing, and typography to keep our designs flexible. So why not extend this logic to resizing? Imagine if we could define a resizing behavior not with static values but through variables that can adapt as our design scales. For example: • Instead of setting a button width to fixed or hug, what if we could create a variable like buttonWidth and set its value dynamically based on the context (e.g., screen size, container, or content)? • You could have a layout that resizes fluidly based on conditions defined by your variabl

Hi Figma Team I have been recently updating my Library and specifically my Color System. The library is quite big and there are a lot of components that use the color system and you can see how it can become really hard if you start changing the color system structure by either removing or renaming colors. This will also make it much easier to see if there are colors that not in use and can be removed without any issues. I made an example below for reference

When exporting PNGs with alpha from Figma, the RGB channels do not undergo padding/dilation operations. This results in UI elements without padding sampling black edges when subjected to trilinear or bilinear sampling. In contrast, PNGs exported from Photoshop automatically perform padding calculations, which avoids this issue. I would like to ask if Figma plans to support this in the future.

Hello Figma! The new UI3 component search is not good. When I use the actions/assets/plugins search, the vast majority of times is to find components (e.g. button, logo, input field, …). Now, when I search for e.g. “button” the first option is “Compute published statuses of soft deleted components”… The second is “Republish autolayout components”… seriously? 😃 There’s no button components I can immediately drag into the canvas. I have to manually click onto “Assets”. Please make it so that either the “All” tab is smarter in suggesting assets, or default me to “Assets”.

For developers, the most crucial aspect of exploring designs is not just how they look but how to implement them. To do this effectively, they need to understand the overall box model and layout logic. While there are many browser extensions that serve this purpose, Figma’s existing Outlines mode could be very helpful. However, it’s currently buried within the interface and feels more aligned with vector editing for designers than with developer needs. I suggest improving its visibility and integrating it more directly into dev mode for a smoother workflow.

I remember being able to connect a variable to a variant, but we changed how things work and want the same for instances (swap instance). This would make prototypes more realistic and flexible.

I am creating a bunch of tweaked interactions for a prototype with lots of buttons with unique values. But every time I type a new value for a string, a spacebar is being seen as cue that I want to close it up. But I don’t want that, I want to be able to keep typing until I hit enter (as enter closes it up as well).

Use case I have a button component which for different colors we use different text styles (one is bold the other is regular). Solution It would be great if I could just add to the button variables table a String field where I say which style to use based on the mode and bind that String to the text style of the label.

Does anyone so disappointed when we’re no longer can create a section by select multiple frames, then press the section button? Now we have to drag the section area instead of auto creating section (with padding) by default as it is in UI2.

It’s currently in the bottom right corner which frequently blocks text and frame options. A recent update moved the toolbar to the bottom of the screen, and I think the help and resources “?” makes more sense to be near that instead of blocking vital functions of the program.

I would like to ask if it’s possible to add a function for prototyping with a string variable .length method that calculates the number of characters in a string. Additionally, it would be helpful to allow setting the string.length to a specific number to split or truncate the string. This would greatly enhance the functionality of our prototype by enabling features based on string length. I also created a plugin called Input Fields to create input fields in Figma prototypes using variables. However, without the ability to split the string, implementing a backspace functionality isn’t possible.”

The main reason why the is so productive while we are building the UI going back and forth to another brainstorming application such as FigJam is takes a lot of time. So please bring sticky notes to Figma as well

It’s extremely frustrating, when enabling autolayout on a frame that already has a few elements composed, that it instantly changes the dimensioning mode (from fixed to hug or fill) without the user’s consent. This often completely changes the look of the design and requires the user to go back, re-enable “fixed” mode and set the pixel value back to what it was This always disrupts the dimensioning mode of child elements as well, causing a cascade of manual changes the user must make to reset the design to what it was. Expected Behaviour: enabling autolayout affects the positioning of the direct children of the frame to which autolayout has been applied, without changing the dimensions of the parent element Observerd Behaviour: The parent element’s dimension mode is changed (to “hug” or “fill”) the moment autolayout is applied, effectively changing its height and width from what the user set it at previously. This breaks the contract between you and the user, since the user expli