Suggest a Feature

Hi Figma It would be great to be able to show/hide component properties when using an instance. Some of my components are complex and having to scroll through seemingly endless nested components, variant settings and other props in order to access the design functions that live below them can get irksome quickly. Thanks

I’m using variables and modes to create multilingual prototypes, using a mode for each language (e.g., English, Hindi, and Korean). When designing, I can switch the language for the whole page easily which is great to create a multilingual prototypes. However, for testing I’d like to be able to provide separate links for participants to test the prototype in their own languages. This could be achieved if there was a way to set the mode for the page as part of the prototype url parameters. That is, having a link with the mode set to Hindi that I can share with Hindi speakers, and another link always set to Korean to be shared with Korean speakers. Currently, I had to duplicate the prototype page to create language-specific versions (setting each copy to a different mode). When there are changes I’ve been regenerating the copies which results in the previous links to the prototypes no longer being valid.

Please consider adding the ability to assign custom tab colors to individual files or projects. This small visual aid would make it significantly easier to distinguish between open tabs at a glance, especially when juggling multiple design files simultaneously. This feature would offer several key benefits. It would improve workflow organization by allowing users to visually group and separate project files. Navigating between files would become faster and more intuitive, reducing the mental load when switching contexts. Additionally, color coded tabs would help minimize the risk of accidentally editing the wrong file, a common issue when working across multiple projects. Overall, it would enhance focus and efficiency, especially for users who regularly multitask within Figma. Color coded tabs are a familiar and effective UI pattern in many tools, and I believe this addition would be a valuable quality-of-life improvement for many users.

This has been mentioned here: Hide layer using variables - #5 by Andreas_Braendhaugen1 Invert boolean variable for layer display - #14 by Desislava_Slavkova Inverted Boolean Property - #2 by drewcovi_usb but those topics are all closed. I am looking for the availability to HIDE a layer when a Boolean variable is TRUE and SHOW it when it is FALSE. So, the inverse of the default/current behavior. I want to do this without using components. Use case: When a variable is true, show one frame. When that same variable is false, show a different frame. I can get basically this by using two different variables: but it would be more convenient to be able to do it with just one. Just give me a Boolean toggle when the variable is used to say if the variable should be inverted or not.

Enhancing variables to have extra logic in place so that variables can be partially based off other variables e.g. Number new_variable = “{other_number_variable} + 4” String new_variable = “{other_text_variable} New Text” Colour new_variable = “{other_color_variable}, opacity 4” Boolean new_variable = “not {other_boolean_variable}”

Many people have said the same thing, but I’m here to recommend supporting percentages within auto layout. I’ve seen many people asking for the same thing. Percentage width auto layout would help us be more efficient. Auto layout “Fill container” is great for sections being sized equally (50/50 or 30/30/30). When we’re designing content with sections, the sections are generally not the same width as each other to indicate importance. Myself and many other designers would love to have autolayout support something like this: The main container has the same spacing all the way around Each section takes up a specifid percentage of the container (70% and 30%) When the modal grows and shrinks, those sections maintain their width of 70% and 30% Without spacing With spacing 800px wide 1000px wide This is what autolayout currently supports If we use auto layout, each section must be a specified width or the same width as the other sections. It makes it so we cannot use autolayout on re-usable c

Figma Team, Data Scientists like me are praying for you guys to develop a data visualization node! you’re missing so much by not providing so. Power BI, Tableau and the other softwares are so square in design and usability terms. I’ve been copy pasting my charts into Figma for the past month and you guys are definitely a level up if we talk about presentation.

As a designer I would like to record my prototype screen or export it as a gif so I can use it in presentations and send quick examples in the team group. It would be great to have the same feature then Principle to record or export the prototype to gif. Does anyone have the same need? Is anyone using a plugin or workaround to help solve this?

If you open a lot of projects the tab strip gets crowded. Chromium browsers solved this by allowing to group tabs, maybe Figma could do the same ?

In our current workflow, new changes to an existing file and/or library start with a branch. The branch allows for a staging environment, but unfortunately we are not able to run API calls to a branch to test before moving to a “production” state (merged to main and published libraries). Can we please make this possible?

I was going to praise how neat the new Annotation feature is, when I realized the content is only visible to Dev Mode accounts. Are you serious? I understand you want to limit creating annotations to certain seat types, but viewing annotations should be a viewer-level feature. Come on Figma, there are better ways to convince your users to pay for a subscription. This is such a crooked move.

One of the properties, very basic in CSS, that I miss most often in Figma is “background-color” for text. Would be awesome if you’d consider adding this feature on your roadmap, especially that you aim to become a competition for webflow.

Hello, I really wish UI3 made the invalid assets more visible when publishing the library. I keep having issues with components because I do not see that there’s an invalid asset.

Having used App Generation with Claude AI, I know how powerful it is to add PDFs as references to inform the content of the generated output.So why is it not possible to do the same in Figma Make, given that it uses the same LLM? Ideally, I would like to be able to create a prompt such as: 'Analyse the attached PDFs (CV and portfolio) and create a portfolio homepage based on their content.'While the current image and Figma screen references are great for styling, being able to analyse and synthesise PDF content to generate an app would be awesome!

Hey @Figma, I've got a feature idea that I think could really streamline our workflow! Currently, when I select a frame, I can easily see and modify all the colors used within it from the Design panel. This is incredibly useful for making quick, global changes. My suggestion is to implement a similar feature for components. It would be amazing if, upon selecting a frame, the Design panel could display all the unique components used within that frame. Imagine being able to: * See a list of every component instance in the selected frame. * If a component is used multiple times, identify all its instances at once. * Quickly change the variant of all those instances directly from the Design panel, just like we can with colors. This would be a massive time-saver, especially when working with design systems where we often use the same component across many different parts of a frame. It would make bulk updates much more efficient. What do you think?

It would be great if the professional plan offered more than 4 variable modes. Right now I want to set up a mode for each component size-- XS - XL, 5 sizes all together-- which puts me over the 4 limit for pro, but well under the 40 limit for enterprise, which is a quantity I will never need. And there’s no use case for enterprise at all for a team our size. I think 10-12 modes for pro would be perfect to give small teams like mine room to grow before we reach the scale where an enterprise plan would be worth consideration.

Hello! I was wondering if I could request a more efficient rendering method for images in the canvas. I have noticed that when my file contains a large amount of any or a lesser number of high resolution images that performance of the file/canvas degrades significantly, sometimes debilitatingly so. I suspect that this is because the rendering engine is doing a couple things: Treating every instance of an image to be unique in terms of memory utilization (the more I add of a single image = more performance decrease) Rendering every image at 100% resolution despite the canvas zoom level or image size So I’m wondering if there are any plans for increasing efficiency of images/rasterized content for the canvas, this is pretty limiting right now in terms of my workflow and things are reallllly slow even though I have around 5 images that I reuse in my files. I’d really love a better raster image rendering method :)

When aliasing a color variable to another (img 1), or using it directly on an element (img 2), we should be able to override the opacity without the need to create a variable for each transparency variation: Cant override opacity in the alias: Example 2 Cant override the fill opacity:

Figma Make is a little bit slow right now, and I end up having to wait quite a while after I send it a prompt for it to perform the action. It would be great if we could have a tone play or some sort of indicator that lets the user know that Figma make is done with a task. This should only happen if Figma Make is not actively being viewed.

Hey Figma Community! I wanted to suggest adding keyboard shortcuts for “Hug content”, “Fill container” and “Fixed width”. With the new design, these options are now in a dropdown, and having shortcuts would save so much time—potentially making our workflow 30% faster! Imagine using these shortcuts on Figma Creator Micro or other external keyboards—how cool would that be? If you agree, please like this post so Figma can see the demand and implement this feature. Thanks for your support!

Fill container should be a button. Right now there’s a button and keyboard shortcut for hug, but fill is just as if not more important, yet it has neither a shortcut nor a button. If hug is a button, it also doesn’t make any sense for unclicking it to do nothing. You could easily add functionality to switch between states (either hug/fill or hug/fill/fixed) by pressing the button. Instead, currently you can click it once to hug, and then click again to do nothing. Please add a fill button or make the hug button more functional!

Please can we get percentages for variables? We can use percentages manually, but we can’t create a percentage as a variable. This would speed up my design to dev process tenfold, and considering we can already use percentages in the design, why disallow it in variables? An example is I want store values for line height and letter spacing as percentages which behave responsively/dynamically, so when creating type variables I don’t have to do manual calculations, store 10+ letter spacing/line height values based on which font size they will be used with and hope I never change the font size variable in the future.

These actions don’t have their keyboard combinations, which prevents me from assigning them from my Mouse keys. It’s one of the most used behaviours for so many people. Is there any way for me to assign them to a shortcut / mouse key?

Describe the problem your experiencing and how your idea helps solve this When we select a particular template or frame on Figma on the right side it will show all the colours did we used on that frame or template that’s a really good feature, Including that can you people also try to show us what all fonts that we used in that template or frame I felt that could be really great move by Figma if you people show the list of fonts that we used in that frame this going to be a great initiative by FIGMA. I’m really apologetic If that feature already existed in Figma I didn’t know where it was? I explored but I couldn’t find that feature. Add as much context as possible (screenshots, Figma files, mockups, etc.) Ask questions to bring the community into the conversation (e.g. Does anyone else experience this? Is anyone using a plugin or workaround to help solve this? etc. Does anyone else experience this? Is anyone using a plugin or workaround to help solve this?