Suggest a Feature

When working with a library that uses a large number of components and states, I think that like how we have a “direct select” tool for colours, we should also have a “direct select” button for component items.In my image, I have a component that has some booleans set up along with how I imagine the button would look and function. It would greatly help to have the same functionality we have to select any items using a specific colour with the “target” button beside it. This reduces time direct selecting items especially if there are items above the layer you intend to select. It also allows users to stay in the right panel for changes and adjustments if they can direct select the component element.  

Hi Figma team,I wanted to share a small pain point I keep running into — and maybe a solution.As a UI/UX designer working on complex SaaS and mobile projects, I often end up with Figma files that have dozens of frames across multiple flows. Despite careful naming, it's easy to lose track of what’s ready for dev, what needs review, or which version belongs to which client.Lately, I’ve found myself wishing I could just tag frames — like #ready, #needs-feedback, or #v1.2 — directly on the canvas or in the left sidebar.Something lightweight, like sticky labels or even a built-in tagging system, would make navigating and collaborating inside Figma so much smoother.Right now, I rely on naming hacks or color-coded backgrounds, but it gets messy — especially when the file grows.I imagine a world where I could quickly filter or search for #mobile or #dashboard and instantly jump to relevant designs.Thank you for building such a powerful tool already. I just thought this small improvement could

You know how sometimes you feel like having a copy of a screen in another file (or page), and would like to have it be updated automatically, but it feels overkill to create a main component out of that screen? If you just copy and paste it (for example for creating a prototype in a separate Page without messing your original screens), it’s pretty much instantly out of date. You also know how you can embed Figma files, frames or prototypes in any website, even integrating in other services like Jira and Dropbox with the Live Embed Kit. It works AMAZING, it shows even up-to-date designs, and you’re simply copy-pasting a link, without the overengineering of extra components. What if this would work within Figma itself?? Check this out: Would this be useful for anyone else? We for example would like to have an example of “usage” of each component in the Components Library, which is usually a screen taken from a variety of other files. But they invariably get out of date super soo

Hello,My developer pointed out to me that when they view the Figma files in Dev mode, the font information only shows this: color: var(--rgb-353132, #231F20);font-family: "New Science";font-size: 24px;font-style: normal;font-weight: 700;line-height: 30px; /* 125% */ Are you able to have dev mode show that information within the css styling?

Auto-Layout has padding (inner spacing), but no margins (outer spacing). Currently the only 2 ways to add spacing is to: Create a spacer element or Wrap the items in another frame and apply gap spacing This creates a lot of unnecessary frames, and sometimes creates nesting so deep it goes outside the layers panel. Not sure if a technical limitation left this out of consideration in the first few versions of Auto Layout, but it would be much appreciated if it were included in a future version as it comes up as a significant limitation many times a day.

It would be beneficial if Figma included the option to enlarge the interactions panel. Reading all the conditional and variable interactions within the small preset frame size can be challenging. Enabling users to expand the panel size, similar to the way the variables frame can be expanded, would make it easier for users to review the interactions they have set. Being able to copy interaction would be extremely helpful and reduce redundant work

Is there a way where i can bind the border with a bolean variable in which i can show it on or off.

Something that would really help me to present my design once it is finished would be to have the ability to copy and paste sections of the completed design to another page and be able to change the prototyping behavior on those sections independent from the main design. The purpose of this would be for example, if I am showcasing a particular mobile screen and it’s capabilities I want the viewer or user to only be able to go so far in the prototype and have to move on to a different Flow in order to be able to see the next interaction or sequence of interactions as I see fit. This would help greatly in being able to use Slides effectively in terms of controlling the narrative of a project. The other obvious benefit is that up to date some interactions only work as designed when the viewer starts that interaction from a certain place in Prototype chain. This ability to separate out sections of the design as I have described would enable me eliminate people viewing interactions in any o

With regular horizontal or vertical auto layouts, we can shuffle/move child items of the auto layout using the arrow keys.Why has this not been implemented in grid auto layout?  Users should be able to use the arrow keys to move grid child items up/down rows or left/right columns.In general, I have been finding grid very hard to work with.  It’s very unintuitive to populate a grid with items—you try to drag and drop items into specific spots and the items never land in the spot you tried to drag them to, and then it always ends up adding extra rows or columns.  And then once a grid is populated with items, it is extremely difficult to move the items around in it, because it requires that you basically either remove the items from the grid or drag and drop them over one another, and this presents all the problems described above.  A user should just be able to move grid child items around with the arrow keys just like any other auto layout,

Hi! First, thanks to the Figma team for all the hard work. Now, let’s talk about Figma Slides Templates. To edit the template styles, I have to select a slide first — which feels a bit unintuitive. In Figma, when you click on the canvas without selecting anything, you can access the file’s styles. Can we bring that same concept into Slides?When I open the template selector, I can edit the styles there through a dropdown. Is that really the best or only way to manage styles in Figma Slides? I don’t think so.Colors & Text Styles: I can delete them, but only through a pretty complex interaction — right-click?Layout Grid: How can I set a default grid? Right now, I have to manually add my custom grid to every new slide I create. If we can't set a default, the feature kind of loses its purpose. :(  

I’d like to suggest an improvement that would streamline the design process—especially when working with components.Currently, when resizing or aligning elements, I need to press the ALT key to view spacing measurements (such as padding, margin, and distance between elements). This adds unnecessary friction, especially during frequent adjustments.My suggestion is to add a toggle in the settings that allows users to always show spacing measurements by default. This way, whenever an element is selected, its padding, margin, and size can be instantly visible—without needing to hold down a key or guess the values.This feature could be customizable. For example: Always show padding/margin/size values when selecting an element. Let users choose which measurements they want to see by default (padding, margin, width, height, etc.). This wouldn't overcomplicate the UI but would significantly increase efficiency, especially for developers, UI/UX designers, and those working with design systems

Hey there! It would be helpful to allow additional metadata to be stored on pages, which could then be queried via the search function.In daily use, this could include alternative titles (especially useful when using a page for one software feature), specific variants or identifiers that refer to third-party software (JIRA numbers), or version numbers. Adding a date field would also be beneficial, especially when working with large files, to better track updates and content relevance.

In the properties panel to the right of the name of whatever you have selected some options pop up such as multi edit, select matching layers, use a mask and/or 3 dots for more options. What is odd is that when I select a variant for example from one component those options can be either wildly or subtly different than if I select a variant from another basically identical component. It almost seems random to me though I’m sure it is not. Is there a resource that could illuminate not so much what is showing when a selection is made but why that particular pop up icon is visible so as to get a better understanding of what inconsistencies might be happening on my end? Always curious. 

During design system development, we often encounter components that could be simplified as templated versions of existing ones.Examples: A datepicker is essentially a pre-configured text input. It could be created simply by setting specific properties on a standard text input component.  A menu component could serve as a generic list for dropdowns, but we could offer templates like "Countries", "Categories", or "Currencies". Adding these templates to the design system would help designers avoid "reinventing the wheel" by creating slightly different versions of the same pattern.Proposed UX for Template Instances in Figma: Create a generic component. Create an instance of that component. Customize its properties as needed. Click "Save instance as preset" or "Save instance as new component". Give the template a name. The template appears as a selectable option (e.g., in a dropdown) when creating new instances.  

I think it would be interesting if plugins inside Figma could be organized by categories, similar to how it's done in the Community. You can see in your menu that your installed plugins are already arranged in a way that helps you better understand how each one works.

In one of my projects I was wanting to capitalize a single word, but realized I didn’t have the ability to do so without it being manual. I feel a shortcut, even if its just in the drop-down sub menu, would be useful for multiple selections that need to be capitalized especially when it’s not the whole sentence/paragraph. 

Add the ability to save local copy per page 

We do many presentations in multiple languages and the process is extremely cumbersome as each time we make a design change in one presentation, we have to duplicate it in all different languages. What would be a killer is the introduction of a Text Layer in Figma Slides. You would select one text layer across the deck and build the whole presentation in a given language. You could add another text layer that would replace the first one with another language etc. Hence, before presenting, you would select one particular language and here we go. If some design changes in the presentation have to occur, you make them in the “core presentation” and it would apply automatically to all layers. Think of the number of presentations that have to be duplicated to be translated in multiple languages today. It would definitely be a game changer and a reason for many companies to immediately switch to Figma (including ours).

Branching is a great feature that helps align the work of designers and developers by providing a shared “main” branch and clear organization. However, the lack of a search input to quickly find a branch becomes frustrating, especially when working on large projects with many branches. Adding a search bar would significantly improve usability and speed.That would be a simple and efficient quickwin. 

If you could set the animation type to a varriable, this would be helpful for creating settings that reduce motion.

 I need to be able to write more functions and specifications on Figma Design, because in this way, the project can view pages and specifications at the same time, and does not need to switch to other files (Word, ppt) to view FRD or PRD. The designer does not need to switch to the platform to write files, and can collect the above text AI into an asset of internal business logic.Or you can import these specification text into Confidence / Jira /Word. I often have to copy it to all other collaboration tools after writing it in Figma. It's really tiring.Why is Annotation not enough? Because the text cannot disappear when the case is finalized, and it must be output on the pageAt the same time, it can switch to display and hide everything, and provide it to different users to view. The function can be attached to Instance without having to pull a lot of lines to the Note next to it, which is really time-consuming. Finally, it is recommended that these texts can be copied once by Figma Ma

Hi Figma Team Legends,How do I reorder the Figma Prototype Flows?  Can you please add a drag and drop feature to reorder them.  I would like to group related views/screens side by side.  Currently they are spread higgled and pickled. This makes it difficult and frustrating to view and check if I have all designs linked.  :-( Once the drag and drop feature is implemented.  A reorder lock toggle switch, should be added to the top ‘Flows’ bar which auto locks the added ‘Flows’ from being accidently moved around when exiting. Your consideration on implementing this feature, would be greatly appreciated.  :-)P.S. Bring the honky and keep the fire burning!

Hi Figma Team Thx for your great work. I have a request that would make my work easier. Could you make it possible to pin plugins in the tool-bar of UI3. Thx

Can't currently apply variable to font in Figma Sites.