Suggest a Feature

I should be able to see what new changes have been made in the file and who made those updates.

Found that the new UI is not highligting an error if an incorrect font weight is selected. Which then might not allow you to apply such text styles to text layers and not understand what causing it.

Problem Statement: Currently, when designing floating chat components or similar UI elements in Figma, setting a sticky position to keep components visible while scrolling is limited to static top-of-page behavior. The lack of bottom-right or bottom-left sticky positioning complicates the responsive design process, requiring manual adjustments for different screen sizes. Proposed Solution: Introduce an Advanced Sticky Positioning feature in Figma’s Scroll Behavior settings. This feature would allow designers to specify sticky positioning for elements in relation to top, bottom, left, right, and their combinations. This functionality would enhance responsiveness and reduce manual effort. Key Features Sticky Position Options: Top (existing behavior) Bottom Left Right Corners (e.g., bottom-right, bottom-left, top-right, top-left). Responsive Adjustments: Allow sticky position settings to dynamically adapt based on frame constraints and screen sizes, making designs more fluid across d

mindmapで一つが長いと同じ階層にいる他の位置も長くなってしまうのを直してほしい

It would be nice if we can toggle a boolean variable easily instead of having to use conditional. Example solutions: Set variable [variable_name] to [!variable_name] Set variable [boolean_variable] to [true, false, toggle]

Background: A useful control feature in Figma Enterprise is the ability to restrict access to plugins with Admin approval. Setting up Admin approval allows organizations to vet plugins for security compliance, and also to manage costs for plug-ins that are paid, not free. A typical arrangement is that an enterprise will require Admin approval for plugins, and allow users to request approval with a justification. Users who try to activate a new plug-in will then see this popup. Once the request is filled out, it goes to Admins’ plugin approval queue in Figma. However, most large organizations use other tools outside of Figma to manage these types of software access requests (in a tool like SharePoint or ServiceNow), as there may be multiple departments involved in vetting and approving a plugin. This causes double work for Figma admins, because they have to email back the requester telling them to also place a request and justification in the corporate approval tool. Possible solution

Since the release of the new Figma and the “removal” of the property tab its really difficult to find where you set each property, it took me 20 minof a lot of googling and tutorial watching to find the new placement. What makes it even more difficult is that the property button for e.g. a text input is an invisible button that only shows when you are hovering. Is it possible to always show that button, so that the enduser doesn’t have to remember where on the screen each hidden button is? Today it functions like this: Couldn’t the standard state show the button?

Hi Figma Team, I’ve been having trouble since the height and width (including Fix, Hug, Fill) parameters were moved to the bottom of the component section. Before, I could easily move in and out of nested components and quickly access the height & width parameters because they were always in the same place. This allowed me to adjust all nested component measurements quickly. However, with the new arrangement, I can’t quickly access these parameters without the component section pushing them out of sight, which means I have to scroll to find them every time I move in and out of nested components. Maybe we could make the height & width parameters stay at the top for consistent accessibility. Thanks and keep up the good work! (:

When adding a new row or column to a table, it doesn’t keep the formatting of the rest of the table (text style, border color etc…). It’s tedious having to set it every time you add a row or column.

Hi, I have an idea to share as I like working on Figma by hiding the UI controls, But it becomes problem when I have to press command + . to show the UI controls. Now the idea is what if I take my cursor on left/right corner edge of the window and hold to make the UI controls automatically. that should ease the usability and reduce the stress of entering the shortcut. Thoughts? Thanks, Varun Sahdev

I think it shouldn’t be case sensitive when we want to set our grid layout count to “auto”. I need to type “Auto”, instead of “auto, AUTO, aUTO”.

Please let users merge similar components into one

The delete key should absolutely not default to deleting the whole slide, it’s incredibly easy to accidentally delete the slide with no confirmtion.

Hello. Old UX shortcuts are broken and no longer available in UI3. For instance, clicking on the text “Export” no longer adds a new export to the list - which is a bit strange because it means that I have to click this stupidly small button now to do one of the main purposes of even using Figma in the first place for many kinds of design. Please–reconsider adding more convenient hitboxes for common actions.

Please add more simple transitions for the “Navigate to” interaction, for example zoom in / zoom out, and let us specify the zoom amount.

Be able to temporarily hide some slides in the left panel and don’t show them in the presentation mode. Add an eye icon per every slide.

I’ve been using the Component Finder feature in Figma, and while it’s undoubtedly a fantastic tool, I’ve found a potential area for improvement that could make it even more invaluable to all of us. Currently, the Component Finder is a powerful tool that aids in quickly locating components within our projects. However, one challenge I’ve encountered is when I type too quickly and make typos. This can sometimes lead to the component I’m looking for not being retrieved in the search results. I believe that enhancing the Component Finder to support typo-tolerant searches could be a significant leap forward in usability. Enhanced User Experience: We all know that mistakes happen, especially when typing in a hurry. By enabling the Component Finder to recognize and adapt to these minor typos, we’d experience a smoother and more accurate search process. Increased Efficiency: The primary purpose of the Component Finder is to help us work more efficiently. By addressing the typo issue, we’d fu

The layer hierarchy has disappeared in the Figma slides. There used to be a collapse/expand icon on the left of the layers, but at some point, it disappeared. (This seems to be a bug due to an update.) Even when opening a blank Figma slide, a default library (such as Light slides) is automatically created. It would be great if there is an option to not use the default library and instead use my own custom library. (Currently, when adding a library, the new library gets created under the default library, causing scrolling issues.) It would be helpful to have an option to add page numbers.

I hope we can have an option to reorder the sections in the Properties Panel. I barely use the Position tab (I only use the “Ignore auto layout” button), and it always takes up space in the panel

I currently use Figma mostly for UI’s. However I have to switch to illustrator to make icons, icons that could have simply been made in Figma. This doesn’t only affect the pen, but also simply things such as the lines. All blue lines in images are the pen tool, all white lines are just normal lines. Here are my QOL suggestions: Add length to straight pen lines. It’s a very simple feature to add, but makes it drastically easier to use the pen tool. Add angle to straight pen lines. Unlike normal lines, pen lines don’t show up in the sidebar. So you can’t see it’s angle. It would be very helpful if that was shown in some way. A way to modify the angle would also be great, but that’s a lot more work to implement. Option to Show & Snap the distance between points in the editor. They currently have a very simple implementation of this already. However, its very lacking. If you look at this example: You will see that the lines snap together. However it doesn’t snap horizontally b

When defining tokens with primitives, currently you have to just remember your primitive definitions. It would be nice if we had a subtle little preview while hovering.

The FigJam toolbox to add stickers could be improved imo (e.g. bring back dock & resize ;-)). For custom FigJam sticker libraries, it would be nice to also have a keyword search bar at the top inside the library. To only search within a specific library. We have a library with stickers for low fidelity mockups for example, I would like to search only in that when creating a mockup. It would also be handy to select and drop a bunch of stickers on the board at once. If you could search and filter, then drag to select multiple, this would be very helpful. Or even just a way to select multiple items by clicking and then dropping them.

Not sure if this would be better under Product Feedback, but are there any plans to add branch names either to the File search index or as a separate search category? We’re looking adopting branching and would use Jira ticket numbers probably in the branch names, and being able to search and find the file containing the matching branch would be a huge time saver.

Would be nice to show which color I’m editing inside the library color selection panel. This is shown in the “selection colors” section when I click on an element, but when I click into this color and another panel appears for me to change that color, I would like to see what color is being selected in that panel simply because visual indicator and name of color aren’t enough. I still have to squint or read.

I’m not sure if there’s a way to implement this today. I understand that properties are a shared language between design and dev. However, I can see how design teams may benefit from having additional props that would help with design productivity if we can use additional properties or variants that only we can see and use in designs. Example below of boolean props to show/hide additional tabs. Devs don’t need to see these props, but it helps designers quickly show/hide more as needed for their own projects. Does it even make sense to use props this way? Either way, I’d love to hear everyone’s thoughts on it. Thanks!