Suggest a Feature

For example, let’s say that I have a design system with the following color configuration: If I wanted to change the hue for my “secondary” color, I have to manually go inside all of them and change their hue, individually. I’d love to be able to set a variable “secondary-hue” as for “255” for example, and if I used that in the color picker hue field, I’d just need to change my “secondary-hue” variable and it would apply across the whole variables using that. If you have a technique that functions in current Figma settings, I’d love to hear. Thanks!

UI3 is missing go to main component button is missing, and leads to mistake of creating new component. Can yall bring back the Go to Main component button in the UI? instead of hiding it? This is useful when making updates and refining my designs, where I make updates to main component, then look at locations where it’s applied. I can no longer quickly reference main component.

It would be helpful to have a history view of a particular object/asset in a design file where I can right click on it and see that objects history only.

Hi! This might be overreaching and quite niche in its application, most probably only effective for centered-but-truncated Texts like Material 3.0 Tabs (but not limited to it)… Is it possible to add another setting for Height/Width that allows the said object to show a behavior close to ‘Flexible’ encapsulated Flutter widget inside Autolayout? This might be a bit contradicting, but it behaves like Hug and Fill at the same time. When the Autolayout resized from its inherent Hug size, it has two behavior: If the Autolayout size is reduced and the object’s size is also reduced, the object behaves like Fill, as in it will resizes itself according to the space left inside Autolayout. If the Autolayout size expanded, the object behaves like Hug, as in it will retain its inherent (or fixed) size and let the Autolayout’s alignment do its work. As far as I explored, the behavior is exactly like when you set an object’s Max Height/Width to its inherent/initial fixed size (like Hug) but also se

I have built a simple plugin for my organization to generate our best practice Figma file boilerplate. I would love to be able to take advantage of the new page dividers feature, but if I use the API to edit the name of the page to something like ‘—’ it doesn’t turn into a divider like it would from the UI. Feature requests Add ability to create dividers — Figma.createDivider()? Turn pages to divider if name is changed to “—” or similar like in UI

Hello, Currently, when I connect blocks with straight connection lines in a way: Line from D to H overlaps G block. There is no option to connect to a specific side of a block (top, bottom, left, right), like it is with curved connection line: <An error occurred: Sorry, new users can only put one embedded media item in a post.> I propose to add an ability to connect straight lines to points on the each side of a block rather than to the center of a block to avoid overlaps and to better manage connection with straight lines. Please consider this request.

Would be great if I could add a sentence or two of context to files so that, when I’m looking at the thumbnails in the Recents list or looking at files in the sidebar, I had a little more information to help me determine if “that’s the file I need”. Right now, it’s a lot of squinting, opening files, realizing it’s not the right file, going back to the list, rinse and repeat. Little snippet of text would help a lot.

When I upgraded to macOS 15.1.1, I noticed that the plugin area became very small. It seems to be caused by a web adaptation issue, as it cannot stretch to the bottom.

When building components, there are certain properties that I do not want users to modify themselves. For example, in the case of a Button, I only want users to change its state or style by toggling the properties I provide, but I do not want them to directly modify the Fill, the Stroke and so on. Is it possible to add a style locking feature during component creation to restrict users from modifying the styles?

With increasing complexity in projects and design systems often distributed across multiple files I often find myself having many tabs open. In Google chrome, I highly appreciate the “Shift + CMD + A” menu displaying all the open tabs in chronological order, it would also be super beneficial to have this in Figma. This would allow to: Quickly switch between tabs that are the most relevant (most recently opened tabs at the top) Search for a tab Increase usability with keyboard only (current CMD + #number doesn’t scale as well) What do you think about this?

When working on frames containing scrollable content, I often end up having to toggle clipping on and off to switch between editing the content and preparing for prototyping. It would be amazing if we could have an option that made “Clip content” apply only in Prototype mode and not in Design mode.

Working with large design systems in Figma can sometimes lead to heavy memory usage and slower performance, especially in complex projects. To address this, I propose a Child File System in Figma, where child files are separate yet linked to a master file that holds all styles and variable declarations. This concept is similar to WordPress child themes and would enable better performance and management of large design systems. Proposed Features: Master and Child File Relationship: A Master File serves as the single source of truth, containing all styles, components, and variable declarations. Child Files link to the Master File and inherit its styles, variables, and components without duplicating them locally. Selective Syncing: Designers can choose which parts of the master file (e.g., specific components or variable groups) to sync with child files. Child files can override certain variables or components for specific use cases while maintaining the connection to the master fi

For components that have a lot of component properties, it can be a real pain when you add another variant later on. If you have already arranged your component properties into an order that makes sense, adding another variant to the component messes up the order of component properties. So please can Figma respect the existing (user-defined) order of component properties when you add a second variant to a component?

I’m in a position where I would really appreciate the ability to add meta-fields to objects that would transfer along with SVG exports. (Long story) You could write them under a specific namespace along with other SVG attributes. Besides string values, the ability to store a reference to another object in the SVG would be nice also (i.e. linking functionality between certain pieces) I’m now thinking of a naming scheme to implement these, but a native support would be swell.

Underlines have been broken since I started using Figma when it first came out. It is the only thing that frustrates me (this program is perfect in every other way, seriously). There have been several tickets opened about it that were auto-closed due to inactivity: Text underline "ink skip" Fancier underlines for links Type setting for underline to ignore descenders The basic problem (and I will re-use an image from that first link, thank you @jdb) is that descenders (seen on glyphs like “g” or “j”) are overlapped by the underline in text elements. The top example (without ink skip) is the way it currently works, and the bottom (with ink skip) is the default behavior in web browsers and is currently not possible in Figma: Is there a possibility that we can get a font option to allow for this behavior? As @Lino_Ramirez and @Gary_Tam have mentioned, this is a CSS option that can be configured. I understand that it’s most likely not as easy as adding an option to enable some CSS proper

We have a typography section when we want to scope variables. What about a Layout Grid section in Scoping mode? Here’s a simple Photo for maybe a better understanding: Wouldn’t it make the work a little bit easier/more comfortable/better? Even if it is just a 1% improvement.

The Interaction details modal is not very tall, making that extra scroll mandatory to set up custom bezier EACH time we create a Smart Animate animation which is probably 100000x a day . It would be a time-saver to just make that modal higher. We use very large screen in our office and this window could be at least 3 times higher and still have space under it 😅.

Allow users to toggle a setting for components to allow freely adding/rearranging nested contents instead of relying on the ‘slot component’ workaround or nesting a dozen possible UI elements with boolean toggle ‘Hide/Show’ variants. This would be especially helpful for container/sheet/section components that really only need to define radius/border/spacing/padding.

When exporting an SVG, a bug occurs: extra lines are added that don’t even exist in hidden layers.

I hate that when I’m switching between pages in a file, I am always seeing NOTHING. Could you take me to the top most artboard, layer, or a view where most of the artboards/content is so that I could know where to zoom in?

It’s frustrating how easily instances lose connection to their components, but more frustrating still is having to reset all, which happens often, because then you have to re-enter or paste in all of the text. Please add “Reset all but text” such that it recognizes your overridden text for what it is: an override.

My team and I have been working in Figma Slides and trying to see if we can convince our company to move off of PPT. To do that, I need this tool to be easier to use than PPT for non tech/design folks (sales and marketing teammates who are not familiar with Figma). That being said, we have a couple points of frustration: There might be a way to do this, but I can’t find it (and we’ve used Figma for years and years), but it’s driving me CRAZY that I can’t use variables or styles from our other libraries in Slides. It would save us so much time. Why do Slides create so many ‘libraries’/‘themes’ in a single file? How do we get rid of them? It happens when we paste things from another file (we often make assets in Figma files before pasting them into slides). This is also driving me crazy. I need ONE theme in these files. And I would like that theme to match the theme we’ve already created in Figma with our variables. Overall I don’t understand why theming a Slides file is so dang hard. I

TL;DR I want to select a variant by what it looks like, without needing to (mentally) translate it into words. Let me cycle through variants rapidly with a keyboard shortcut. Example: (exact key combinations flexible) Cycle to next variant: CMD + Ctrl + > Cycle to previous variant: CMD + Ctrl + < Press and hold either down to rapidly cycle through all Process steps (what I should be able to do): Select a component variant I’ve placed in a design frame. Use a keyboard shortcut to quickly cycle to the next variant. If I overshoot (cycle past it), use the related keyboard shortcut to cycle back one variant. (shortcut with “<” instead of “>”, for example) Benefits: My eyes stay in one place, instead of moving back and forth between the icon and the variant properties in the right panel. The eye-travel requires re-centering each time, to triangulate the correct drop-down. I don’t have to navigate several drop-downs, each with multiple options. A huge reduction in

Nested auto-layouts have a broken hierarchy. You may think that settings or properties applied to the outermost autolayout will be inherited down the line, but they are not. Take for example strokes or corner radius. Let’s say that you have a big auto-layout box (lets call it parent) with another 3 auto-layout boxes in horizontal direction nested inside of it (lets call them children). If I want to apply corner radius to the edges of the parent box and I do so in it’s settings it does nothing. The only way to do it now is to apply corner radiuses to the upper left and down left corners of the left child box and the upper right and down right corners of the right child box SEPARATELY. Imo this is insane. Same applies for applying strokes and many more settings and properties. Figma pleaaaase fix this. On the other hand if this is done by design please explain why. Thank you in advance!

J’aimerais avoir la possibilité de mettre le local variables panel dans mon deuxième écran pour ne pas a avoir l’ouvrir à chaque ajout de variable