Suggest a Feature

The Layout grid is one of the great innovations in Figma. However, little has happened to the feature for years. I’d love to see the following upgrades: Allowing variables for sizing and other settings. Being able to name the rows and columns inside a layout grid style for quicker reference. For example baseline, modules, etc. Allowing adding several grid styles to one frame. That way one could organize the grids into baselines, modules, spatial zones, etc, and turn them off and on depending on what you are working on. Being able to use percentages for margins.

I’m experiencing an issue with the ‘Section’ quick command… Problem I find that the quick command for this feature is being applied when I’m not intending it to be — It’s impacting workflow and causing confusion across our design team. My POV I feel like the quick command for this feature is less important as it’s required after exploration/discovery. Is anyone else having an issue with this?

I have a lot of working pages, they are named by the user story number. So in one design file usually I used it for some sprint, and inside of it, there are so many pages (user story with the number). So please, help me with this, I need to search file or name, or anything freely on search bar… so I mean, i can use search bar in the Homepage to search not only for files, teams, or people, but also for search what’s inside the pages. 🙏

I wonder if I would be the only one with this need, but I’me playing around with the variables and the modes. I’m using the to set up light and dark mode. And I have a specific case where: page frame - is set to light mode content black frame - is set to dark mode (you could name it inverted or dark variant) The need is to have an option where you can set to allow automatic changes to either: Option 1: page frame - is set to dark mode content black frame - stays in dark mode (previous preset) Option 2: page frame - is set to dark mode content black frame - is set to light mode automatically (as a result of the automatic switch) The need is to determine the dark variant behavior when switching from light to dark mode. Interested in your feedback on this feature?

Currently, exposed properties are not visible in the component playground of the development mode. Only the parent properties are displayed. This poses the risk of developers overlooking the intended capabilities of components. This is especially a problem with heavy nesting and when designers use the base component method. If nested components or their properties were visible, this would be a huge improvement in terms of usability, as developers would no longer have to select each nested element individually. Side panel in design mode:

Feature Request: Ability to turn off guides, separate from rulers of course. Hide guides Ask the community Figma should have a way to turn off / hide the guides, without having to deleting them overall

Same as in photoshop, fireworks, CSS. Being able to Skew an object has been industry standard for years… I remember it back in Adobe Fireworks CS4. Should be a simple implementation imo?

The way “on mouse leave” behaves is a bit problematic in some cases. Let’s say i have a component that has two states. Default, Active. Active leads to default on Mouse Leave. If i set the component to active on a page, as soon as i move the mouse around without even reaching that component the mouse Leave will trigger. I imagine that it would be more logical given the name of the interaction that Mouse leave triggers only after my mouse was on the component. Since i haven’t “left” the area because i was never on it. May be two separate interactions would be interesting : On Mouse out (triggers all the time when you’re not on the element) On Mouse leave (only triggers after interacting, leaving, with the element). Right now we’re paining our head on a projet because of this with menu elements that need to be opened and reduce in size after the first interaction. The way it works now forces extra (unnecessary varian

Please create a shortcut to center multiple layers to their frame

Problem: A big list of options in the “Assign Variable” dropdown menu with different collection lists. Idea: Add the ability to show/hide a collection from assigning at the right sidebar, local variables. So Primitives collection will be shown only in Local variables (in Theme collection) and in the right sidebar in the “Assign Variable” dropdown menu, I will see only the list from my Theme collection.

Hi! I have a long-running pain point with Figma—I work on pretty complex flows and like to organise screens into flows by putting frames within larger frames. I run into a problem with the eng team I work with because links to the individual frames nested in the larger frame don’t work and just point to the parent frame. Is there any way to link to subframes?

Please give precision size and angle control for Curvature control handles

Just widget improvement and idea hopefully a Figjam Timer can add background music for example (lofi.co or spotify playlist) Doing a workshop like wireframing and ideating ideas with almost 10 to 20 mins it’s helpful to add background music.

When I use the copy svg function in order to bring my prototypes into Figma, functionality breaks, icons also and images disappear. Adobe XD allows working with Figma but Figma doesn’t . ie cross working from adobe xd, illustrator and photoshop copy paste and contrl v don’t work. Since Figma is now owned by Adobe, I’d think you would make it adaptable with all the other adobe software. Please change

I love the new feature that allows multiple prototypes per page. One issue I’m having with it, is it assumes I want everything to be a new flow starting point each time I don’t link something from the first flow starting page. It has a very linear mindset. When I work/prototype I tend to work on a section, then link it back and that creates many flow starting points on accident and I have to delete them. It’d be nice if either - it only created the first one, and doesn’t assume you want many or there’s some kinda preference/setting where I can turn it off. Do other people delete starting points or have work arounds? Or is there a preference/setting I’m missing where I can turn it off?

Hi all. Managing variables can be challenging when you deal with huge design systems that involve tokens. One challenge I’ve been facing is to identify which variable ( from which collection ) has been applied to an element, as they look all the same on the ‘‘selection colors’’ panel and names are always trimmed due to limited space available. I’m wondering if assigning a color to a variable collection that will reflect on the ‘‘pill’’ background on the right panel would help to visually identify which collection has been used.

Hello everyone. I’m working on a complex color tokens system which needs a lot of collections ( Primitives, System, Modes, Themes, Components ) and the variable panel gets so big that it covers 80% of my workspace. It would be good if we could drag the panel outside the workspace ( more or less like we manage file tabs ). Also, browsing the panel is quite hard as it resizes randomly hiding relevant elements, does not scroll properly at times, and names are often trimmed due to limited space allocated ( token names are likely to be quite long so I think this issue will remain ). Just a bit of feedback on an otherwise brilliant feature! Thank you!

The original post timed out after 3 months, but I still think this would be very useful. I want to be able to open any file that I have open in the Figma Chromium app in my browser. A simple “Open in Browser” command under File would be welcomed for various reasons. Use Case: I need to be able to open a desktop file quickly in a new browser client tab for comparisons, viewing prototypes like our UXR customers are going to see them, and other tasks.

I have the organization plan. I’ve created a shared library to be used across the org with multiple teams. When I go to settings per Team to enable libraries for all team files, it does not appear. This is true for all the teams. I’ve checked to make sure that access to the Team is set to Open and that the library set to All Files (and even Design). The stranger part is that this works with other libraries, but not the new one I’ve created. Also, I am able to enable the library one by one per Figma file which is very tedious.

Currently Drop Shadows don’t have access to the Colour Libraries. Would be convenient for quick iterations if this feature was added.

The purpose of this linkage is to make it convenient to make alterations or modifications when necessary, all without the need to update the primary or main component separately.

I am working on a huge project with a very large number of layouts. We are required to have many pages within one project. The problem is that when a new team member arrives, he has to explain everything and review dozens of files and pages inside them in order to figure out where and what lies. We create separate documentation for all files and pages with descriptions for them. This makes the process as difficult as possible. I would like to just go to the File and read its description. Go to the page and read a short description to quickly find out what and where. It would be cool to have something similar to the description in Prototype->Flows

This topic has been apparently discussed before, but i want to make a post to emphasize the importance of this issue. Detaching nested components inside components, breaks all overrides on the parent component instances. I claim this is a major problem, as it makes it really hard to migrate a design system to use properties instead of a vast amount of variants. As an example, i work in a large company, that a lot of materials in Figma. The design system has been initially created a vouple of years ago, and at that point, we had to rely a lot on component variants that very often utilize nested component instances. Now with the new Figma properties, and the apparently upcoming improvements on them, i could quite easily reduce the amount of variants by 80% in general, and make the components much more simple and foolproof. However it would require detaching a lot of the nested components, but it is practically imp

A real quality of life update would be to change the way Undos and Redos work. It’s clear that there are about 100 steps I believe, but this is every single mouse click, selections, repositions, change of everything. It would be amazing to: Track only major changes i.e. styles applied, variables applied, repositioning, increment and decrement of size for fonts and images Have a separate instance for the undos and redos for components, would be great if each component had their own instance or even their own minified version control Obvious buttons for Undo and Redo with a drop down with last actions upon keeping the button pressed for 2 seconds. Just a couple of thoughts. Thanks.

Hey there, I scoured the forum for “spline” but came up empty-handed in terms of topics. 😕 Anyone out there aware of whether Figma plans to add native spline support to their roadmap? Tools like Webflow have nailed it with their implementation, so it would be awesome to see some spline love from Figma too! Cheers, Sanny