Suggest a Feature

It would be great if apple users wouldn’t have to type whole Apple ID account every time they want to log in. I would love if you could login into Figma using your Apple ID as you’re able with an Google Account.

I noticed that in the Component description, there is a proper line break, but it is missing in the version history. It would be very helpful to have line breaks in the version history description, as it is used for the change log.

I’ve had the issue, that when sharing my Figma files with people who aren’t well-versed in Figma, such as clients. They often struggle to discover that they need to push down the divider line between the pages and layers to access all the pages. Additionally, the layers aren’t particularly relevant to them. In my view, there could be a more intuitive separation just like there is now between the layers and the assets, similar to how Framer accomplishes this, for better user experience.

Would be super helpful to also have the option to view the Color (SwiftUI) instead of UIKit. Sure it’s as simple as wrapping Color() around the UIColor, but why not 🙂

Because variables are set at a global level (using local variables), moving components or component sets from one file to another breaks everything, and the local styles must be recreated and relinked in the paste-to location. If Sections or Frames were used as the “owner” of the component variables and Local Variables could be used the same way they are today, plus aggregate all the “Section variables,” then managing variables would be easier, and moving components and their variables would be seamless. In addition to solving for broken variable references, this approach would help organize variables and keep them close to where they are being used.

I always find myself wanting to move my plugins out of the way from my tools. It would be awesome if I could just have my plugins open on my second monitor for use when i need them instead of having to close them and restart them whenever I use them.

Right now objects are updated one by one, so if I want to update 100 objects, the layer panel on the left is updated after every update/creation, and it’s suuuuuuper slow. If there was a function that I could give all my objects to, and then it would do work with all of them at once, and then update the layer panel once. That would be amazing. 🙂

Auto layout is great, especially with the new Wrap feature. However, I find it quite limiting still. It would be incredibly handy if you could add a logic or conditional to a frame with auto-layout. For example, if a frame is > 1366px to run horizontally, but for < 1366px for it to Wrap automatically. This would especially handy for components that have the Fill Container width applied to automatically cascade and fill the frame when scaling down.

I want to attach JSON lottiefiles of animated illustrations (made in another tool) to a certain page in my design file, so developers and other stakeholders can access and download the right (and most recent) assets. Would be even more great if you could link these files to specific frames in that file.

Hi, the recent changes to the toolbar mean I need to do an extra click to put in an arrow if I don’t want to use the auto arrow. And I need to now do an extra click for flow chart shapes as well. This isn’t great when you’re mapping on the fly and it makes you slower during collaboration sessions. This is SUPER ANNOYING. Am passionate about this because I love using Figma and it feels like you’ve put broccoli on my pizza. Please fix this so that things are immediately available with the least amount of clicks.

Often finding situations with multiplayer mode where we’d like to see the other person controlling a prototype or various interactions, but the preview window and present mode don’t seem to support it. The ability to view cursors in Figma layers/properties panels would be awesome as well!

Selecting color styles/variables, text styles, or anything else from one of these narrow and short popup windows in Figma is like trying to read a book through a keyhole - a major usability issue considering that selecting these things is one of the most common operations that a designer does. I have modified a few lines of CSS in Figma to demonstrate the glory of a wider and taller color styles window, where style names are not truncated so that I can actually read them, and my screen space is being used to its full potential.

In the community tab, the save button should be added to the main search results as many people like myself are working we like to saving files for later. Instead of opening every file and then keeping it from its detail page, it is annoying and time-consuming.

I would like to be able to set global variables in a component library (for example, for callouts), then use those components in other files and control variables used in those components from the Local Variables panel. For example, I could create a “callout” component in a library, add that component to multiple screens in a file, then use the component’s boolean global variable to turn all instances of that component on and off at once. I’d like to toggle this variable in design/dev mode, not in prototype mode.

It would be awesome if, when a Frame is selected, all of it’s child layers’ interactions could be listed in the right side panel as well. This would make it easier for us to track down where interactions are being set, especially when designs are shared between designers and it’s not immediately apparent which layer/element has the interaction.

While we set to expose nested instance’s property, we can easily adjust them in the property panel. As I try to get the exposed instance’s property through plugin api, my method is to get all exposed instances of one node, and read their componentProperties each. Now here’s the problem, I discover that every nested instance (no matter what parent they’re under) is in the top instance’s exposedInstance property. It’s kind of hard to sort them out to be of right nesting structure and in my case I need the right structure. So I think if we could get exposed instances’ property by their structure through api, while not breaking the property panel (cuz adjusting them all in the top level is easy), that’ll be more convenient.

This will save some tedious typing in some cases.

I like to design while only looking at the screen I’m designing, but Figma makes it hard to focus because there’s lots of element in the canvas. I’d love to be able to remove the tab bar at the top, the blue selection around layers, all the drag handles, the resize handles, the auto-layout borders, etc. Sketch makes it possible to have nothing else than your work on screen and that’s very comfortable to polish the details of a production, work on shadows, find the right alignment, etc.

Is it possible to update and export frames from multiple files without opening each file? I have a large set of detailed map graphics. Each map has it’s own dedicated .fig file that includes the frames appropriately set up for export. Each map is made of elements tied to shared color variables and components from a shared library. When I update then publish those variables or components naturally the frames in the working files update but only after I open the file > review updates > update changes > then export all the frames in the file. I’d need to do that for hundreds of files. I’d like to be able to somehow “batch update” then “batch export” these files. Perhaps a plugin? I understand this can be accomplished by having the entire library of maps in a single .fig file, then export all frames from there at once, but for various reasons I’d like to keep each map as it’s own separate file.

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