Suggest a Feature

Nowadays Figma shows a purple + (add variant) button underneath my selected variant. I keep clicking it accidentally and it’s really starting to annoy me that it was added for no good reason (there is a “add variant” button in the top bar where it’s not in the way of my regular clicking behaviour). My suggestion is to make it a setting to hide this button. But I have no use for it. So it might also just be reverted to how it used to be without that button, we survived fine without it.

Currently in FigJam, you can option-drag copy (MacOS) elements even when they are locked. This seems like intended behaviour, but it is really frustrating when running workshops. I create a lot of templates for people to work in, and then lock them. I expect those elements to be locked - meaning no interactions! Multiple times a workshop, I or a participant will accidentally copy the template we are working in, rather than a sticky note or other element. It’s confusing, takes time to trouble shoot, particularly when zoomed in, and happens all the time. If this is intended behaviour and it’s useful for others, then we need another solution to prevent unintended copying, maybe something like a template layer, or two-level locking (lock content, lock everything)

I originally posted this in the primary UI3 feedback thread, but it was suggested to me by @Leonel_Vitorino that it be it’s own topic as it had enough importance that it should be able to collect it’s own votes and such. It appears that inserting components from libraries is entirely driven by a “search” in UI3, in UI2 one could also “browse” for components by looking through a library. This was important to me in my workflow as I don’t always know exactly what a component is named. For example, inheriting a UI kit from a previous designer or using an extensive public icon library. To go a bit deeper, I use Material icons for many of our projects and I may not always know what the icon is named—but I generally know what kind of interaction I am wanting to represent and Material is organized in a way that appropriate icons are “discoverable”. Thus, in UI2

I get the minimized UI, but I can’t be the only one who finds it a nuisance to have to maximize the UI in order to change pages…

Hand-off of complex project can be quite tricky. Somehow a better export from Dev-mode, to maintain the autolayout constraints as media queries and make it easier for devs to replicate all the responsive behaviors created by a designer would be such a terrific feature! What do you think?

Hi there, I have been loving Figma Slides since the day it has been launched. But since I have been duplicating slides, I noticed how excruciating it is to change footer text to make sure it says “Design update August #3” instead of “Design update August #2”, and the different section titles. So I would love a feature in which you can create titles and other text values that you can connect to a text layer, then select that text layer, and edit that “variable” from any slide that has a text layer with that specific “variable” (thus decenteralised). Would love it even more if things like date and page nr. would be in there too.

It would be useful to be able to add a trigger to a frame that once it ‘loads’ some kind of interaction would kick-off. This would mean that not every prototyped action needs to be on click or on some clear action on the user’s part and would also allow for variables to be used to check what states components should be in so that we can have conditional logic per page.

It would be very useful if it were possible to set in the Color Scope of the variables the color value as text content, allowing you to select which value would be visible: Hex, RGB, HSL, etc. This would greatly help speed up the creation of a design system that contains hundreds of colors, making it easier to clearly visualize the variable name and its value, allowing for quick identification and improving the workflow, especially in collaborative projects.

Hi Figma team, When building prototypes with overlays, the “Reset scroll position” and “Reset component state” options currently apply to both the main page and the overlay simultaneously. It would be really helpful to have the ability to reset the scroll position and/or component state independently for the overlay and the main page. This would give us more control, allowing only one to reset when needed without affecting the other, which is particularly useful in more complex prototype designs. Thank you for considering this improvement!

Have you considered adding the ability to toggle the ability to follow on and off, as it’s been implemented in Sketch for a long time?

I love variables, it lets me create flexible design assets in all sorts of ways but managing variables is just such a pain in the ***. Just a simple thing as resizing the cells of the window would help me see the full name of the variables. Bonus, give me a way of exporting/importing/copying collections so I can move around my hard work to other files with ease.

I would like to easily copy a full collection, a mode column, some variable rows, and even some selected value cells from one file to another using simple cmd+C/V, like using google sheet. And because basically we are talking about tables — let me copy/paste cells between Figma and Google Sheet. In Google Sheet I can calculate values, scales and I could then easily update multiple values in just a few clicks.

I just began collaborating with a design studio that insists on managing to-dos in Notion, which basically lead to Notion comments. The manager is doing it manually, and boy, it‘s such a waste of time. This foolish management spark an idea: Would it be useful if there is a plugin that as people leave comments in Figma, those comments to be integrated into a Notion database, so a manager can organize it into a Kanban style? Do you think design agencies would find that useful, and time-saving? Any ideas are welcomed!

Using the Material 3 community library I created custom components using autolayout and the vertical or horizontal spacing. The community library allows you to turn a card or sheet into slot that will accept a local component. The problem I have is that if say I have 24px vertical spacing between items in an autolayout that spacing disappears once the component is inserted into a slot. Is this normal behaviour? I’m managing to work around this by adding padding to the items inside the layout but this is not ideal.

Issue When performing user testing, the prototypes can look and function so real that users have tried typing into static fields. This can lead to problems if a user types a shortcut (ie “C” for comment) and a Figma login window pops up, or “R” and they are sent to the beginning of the flow. The main use cases I have for prototypes are: 1. General/Client Presentation Users: Only me This case is covered well by the existing functions. The shortcuts help the presenter navigate. However, a Table of Contents (TOC) is badly needed. Many prototypes are not linear so the forward and back button navigation is not very useful. 2. Client Handoff Users: multiple people who may have a wide range of interacting Figma prototypes Improvements: showing users shortcuts and a TOC upfront and letting them hide it if they want sometimes, especially in t

It would be nice if we could add more Code Syntax options than just Android, iOS, and Web. For example, Mac, Windows, or generally Desktop, and others. Tried adding my own to see what would happen… Uncaught Error: in setVariableCodeSyntax: Expected "codeSyntaxPlatform" to be one of the following, but none matched: Expected "codeSyntaxPlatform" to have type "WEB" but got string instead Expected "codeSyntaxPlatform" to have type "ANDROID" but got string instead Expected "codeSyntaxPlatform" to have type "iOS" but got string instead

When drawing a new element, I’d love the editing cursor to be able to snap to existing objects in my design. This is particularly useful when adding the first node/anchor. Something like this will speed up workflow and increase accuracy.

Older UI seems more easy to use from usability prespective

I just came across this issue again and thought it could be helpful to share the minor, but irritating UX flaw on the Figma community page. I think the UX changed here a little while ago, moving the Community link to the bottom left corner of the dashboard, instead of at the top, which I have gotten used to now, although I do feel like it could use more prominence on the page, as in the bottom left corner, it does feel hidden. Once inside of community, it becomes very hard to know how to get back to the dashboard to you just came from without hitting the back button in the browser, or clicking the dropdown in the top left and reselecting my account, which isn’t super obvious. Would love a back to dashboard or home type of button… Anyone else? 😅

I’d love a feature that allows for the automatic routing of multiple toggleable buttons within a component in prototype mode. i.e. I have a horizontal autolayout component with 10 toggleable buttons, and I want only one to be active at at a time. Currently, I need to create a component with 11 variants (1 being all buttons untoggled) and manually route each button push to the variant where each button is toggled. This means dragging over 100 prototype arrows! This is time-consuming and error-prone. The ability to define these interactions once and have the prototype automatically route for all instances within the component would greatly improve workflow efficiency. For example, instead of connecting 10 buttons to 11 components manually, the tool would recognize and route them after setting it up once. This would make prototyping faster and reduce the potential for human error.

Currently, when we publish updates, we can see that components have been modified, but there’s no clear indication of what specifically changed. It would be extremely helpful to have a feature that lets us compare changes and highlight differences before publishing. Many design systems must be struggling with this! In large, collaborative environments, we need better visibility into what’s being updated—real change logs with notes, version numbers, etc., for both designers and developers. With branching, we can review changes before merging, so why can’t we compare what a component looked like before versus its new modifications—such as variable (token) updates? The same applies to variables (tokens) and their usage. Figma’s current functionality feels limited, particularly because it lacks analytics. It would be invaluable to see where each token is connected and used, rather than relying on the knowledge of those who built it. A feature that provides this visibilit

SML won’t select identical children of the same component if they weren’t copied with frame or idk. In my workflow it does nothing at all. Completely useless feature to me. Right now I’m staring at 20 children of the same component and SML tells me “No matching layers to select on page” So you have “Select item using this color” for colors. Why not have the same for identical instances? Too straight forward and consistent? List can be expandable too.

The search icon currently replaces the whole “File” and “Assets” view in the sidebar. You can only get back to the UI by clicking the X icon. At the same time the search only searches through layers and content, to find assets you have to click on the “Assets” tab and use the searchfield inside this tab. It would be more intuitive if the search wouldn’t replace the whole sidebar content. It is also more consistent to have the searchfield inside the “File” tab. BTW: It is also counter intuitive that the search icon is replaced with the library icon, when switching to the “Assets” tab.

I wish the brightness / contrast / highlight / shadows functions in the image editing menu were a little more powerful. The range of which you can adjust brightness, contrast, highlight, shadows always feels like i need it to go just a little bit darker or brighter but i hit the threshold of the tool. More rich contrast values would help for adjusting fussy client .jpg logos against a dark gray background.

Why did the size of the cover image change again… This is too harmful to obsessive-compulsive disorder… In my memory, this is the third time the size has been changed…\