Suggest a Feature

Managing local variables is pretty cumbersome and buried in menus. Bringing over the variable window found in Figma, would be big help in managing local variables.

Our organization is growing, and as result we are letting more and more folks into Figma. This is becoming increasingly difficult to manage.I would love to see some updates added to the people page to be able to manage users more effectively.One idea is to just add a “tags” column. This would be sufficient for my needs.Need:I want to be able to know what department/role a user belongs to in my organization so that I can ensure everyone has the right access based on their specific department/role.I imagine that I am not the only one with this issue, not sure how other people that are operating at a larger scale are currently handling this.My current workaround, which is terrible. Is to open up rippling in one view, and Figma in the other and compare individuals across tools to understand what access they need.

Hi,The addition of annotations and measurements to Design mode is such a great decision.However this is rendered almost useless if the annotations and measurements can’t be made visible to View Seat users.Often annotations are used for communication with a range of stakeholders, not just designers and developers. It’s not viable to upgrade every stakeholder to a Full or Dev seat to engage with this content.

I was super pumped to start using grids for my layouts until I learned of one fatal flaw that killed my excitement :(  The inability to set a row height to hug is simply a deal-breaker for me. Also no variables support for gaps? really?

During client presentations, we typically showcase the prototype and capture feedback through comments added directly on it. However, while implementing these changes, we observed that the comments move along as the prototype is scrolled. This makes it difficult to accurately track which comment corresponds to which element.It would be highly beneficial if the comments remained anchored to their respective positions on the prototype, rather than scrolling with the frame. This enhancement would ensure better clarity and efficiency during the review and implementation process.

Please… PLEASE! For those of us with lots of simultaneous projects and heavy deliverable schedules, tab browsing in Figma needs some LOVE! Now, I’m not one of those psychos that keeps 300 tabs open in their Chrome browser, but I do, at any given time, need access to multiple projects simultaneously. If I could easily group those tabs together in Figma and give them a nice, friendly name, maybe an emoji, or… dare I say… a color, I’d be a really, really happy camper.  

Hello! 🤠I was very excited to see the addition of Auto Layout Grid today! Having flexibility for both Rows and Columns at the same time is a game changer.That said, I immediately ran into not being able to set a column width to “Hug” within a table, which is a bummer. In the attached video, I want the “Audited By” column to Hug to the longest table cell content. I show both the current solution today, and what I am trying to do with Auto Layout Grid.I can manually adjust the width of the column, I guess, but as you can see, it makes it hard to ensure correct padding without a lot of careful tuning of the width. Anyone have any solutions? Will this be coming as a fast-follow feature? Thank you!

A few years ago there was a fix - The icon on the instance inherit color override, imposed by main component, when swaping icon or changing variant. Great!but… Problem If I modify the icon color on the main component - change color style or manually pick new one, doesn’t matter. The instance with swapped icon doesn’t notice the change! Steps to reproduce:Place an instance Swap the icon on instance Change variant's (main component) icon color Instance's icon color will remain not updatedNote: Of course, all layers properly named to keep the naming integrity. The example: Current, far from being perfect, workaround:If you change an instance to a different variant and change it back, the color will update. Obviously, a lot of effort when you have 15k instances of the modified badge. Use unique variable (semantic). Modify value but don’t touch the name! Sounds nice but be real, semantic naming for each element is an overkill for 80% of the products. Hated but still working - color overlay

I am using Figma from almost 2 years. It’s a great tool. Previously I was using Windows 10 yet recently switched to Linux(Ubuntu). Figma doesn’t have any official release for Linux. There are some Unofficial desktop versions but they are “BUGGY”. I request you guys to release an official Figma desktop app for Linux.

Let us be able to add audio to the slides to give it more life. Imagine that after creating a presentation with your prototype embedded into it and some animations. You can finish it up with some amazing audio!

Clicking between two pages is inconvenient – there should be a hotkey for that. Context — I have components in Page A and need to see the changes I make on Page B. I make lots and lots of small iterations to my design and want to swap between Page A and B quickly to see results. Solution — A back and forward button (or hotkey) that let’s you jump between pages you’ve last visited and forward again.

Hello. I was wondering if it is possible to have percentage values in variables, like setting percentage value for frame widths or shape sizes (etc.) that have variable modes applied to them? Percentage values could respond better to content that varies within a frame or frames within frames.

It would be great to be able to seperate the visibility objects beyond just the layer. To be able to associate a boolean variable to the visibility of; Layer Fill Stroke Effects Would make it more effective when putting together a design system. This means that you could effectively determine that all buttons have outlines, or drop shadows or both right across the whole design. See examples below. Thoughts?

I would love to be able to create one prototype across the pages in a file that resembles an actual website. This would be ideal for bigger projects and would be easier to maintain as well. We can connect the component libraries across all the pages anyways. A way to connect the prototype would be great in my opinion and that will give Figma a big leg up on other platforms. What do you guys think?

Hello, I really would love a setting that would make the new layers, freshly duplicated layers, etc, appear downwards - on the bottom of the list if nothing is selected or underneath the currently selected layer. In other words, to change the general direction of layer stacking - to go from top to bottom, instead of bottom to top only, as of now. This is very logical, isn’t it? We create pages in figma and they go from top to bottom, most designs are created from top to bottom, most content flows from top to bottom. Then why do layers go freaking upwards? 😀

Can we have an option stop syncing while in view only mode at least? I don’t need the latest version all the time for visualization and to keep loading every time I focus back on the tab is very annoying.I’m keeping it in offline mode for now by using dev tools to prevent loading but something a bit smarter would be better.Reloading should be an optional action.

When presenting screens, we want to show the work within a phone. Right now we go to prototype mode, take screenshots of the prototypes, then remove the backgrounds in photoshop. Please let us export screens with the phone like it looks in a prototype, so we can add to slides. 

Hey Figma team, like a lot of design teams, we often add features over time.Sometimes, the feature adds are so large or disruptive to the current design that we need to overhaul it (and sometimes the project structure).Starting a new file is disruptive because we have a fair number of people who have relationships with the old file. Without a redirect function, getting all the stakeholders to find and start using the new file is an epic poem of a task.We want to minimize disruption to other stakeholders who may still need the older designs until the new one is agreed on and ready. The logical thing to do is work in a branch, right?The problem with this is that right now, branch merges require a complete review of conflicts - and this is a problem, because:I don’t want to review and merge conflicts one by one. I just want to completely overwrite main with my branch. Making me do this is the most unnecessary form of “are you sure” and takes forever. The merge tool has a stroke and basica

Hello there! I am new to coding, figma make, and github. I have a prototype designed in Figma Make. I am wondering if anyone can help me save my work to github? Starting from having a published prototype to commit work to GitHub. Here’s what I’ve done so far. 1. Created a New GitHub repository for my prototype I created in Figma Make2. Published my Figma Make prototype​​​​​​3. Downloaded the code to a folder on my local computerI appreciate any help! This is all very exciting stuff. 

Hey! How can I transfer the AI generated Prototype in Figma Make to Figma Design and continue editing it manually there?

I’d love for there to be a way, when working with overlays/modals, to be able to close the overlay so that when it closes, the screen revealed upon closing is different from the original parent screen. For example, on mobile I have a bottom sheet menu from which I can select an icon that allows me to navigate to a new page. This isn’t the same as swapping overlays or navigating within overlays. It’s that an action from the overlay results in the parent screen (screen under the overlay) changing. I’m able to do this with Smart Animate with just the menu component, but when I want there to be a dark background to overlay the parent screen, that messes the animation up and the behavior isn’t as one would expect. The animation with the overlay feature is perfect, except that I can’t control which screen the overlay closes on to.

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.

When creating tokens and working with variables Dev Mode generates code where the group name is included as part of the token name. Currently this doesn’t make too much sense (for me at least) and in Figmas own variables tutorial it would result in spacing tokens being called “SpacingSpacing-sm” if you would look at the tokens in Dev Mode. Can we please get an option to exclude the group names from the generated code? The groups as I seem them are for organising and not necessarily something we want to automatically include in the token name. Semantics are important for tokens so if I have to leave out part of the name and only have it as part of a group name it makes reading the token and using it correctly in Figma so much harder. Definitely interested in hearing others experience regarding this! Maybe i missed something or should rethink our structure.

We sometimes link component to another component in another page.On desktop app, it will be very convenient if we can go back to previous page instead of having to look for the figma page we came from manually.