Suggest a Feature

I have been designing for set-top boxes for several years now. And it is very convenient to do it through the transmission of the screen to the TV. But, there is no official support for Figma Mirror for TV sets. Many times I wrote to support and asked, but I always got the answer that there is no support. The most interesting thing is that Figma Mirror works perfectly on Nvidia Shield or Google Chrome (last generation) set-top boxes. You only need to put the app through aptoide. But with each time figma mirror refines the functionality for the phone, which severely degrades the functionality in TVs. For example, last year, after another update, the Remote Control for prototyping stopped working on the TV. It was very convenient to make a prototype, connect the buttons on the remote, and control the app. It felt like you were really using an out-of-the-box app. But it doesn’t work anymore. The second example happened with the last update. There was onboarding, which doesn’t allow you to

These are new and improved color formats that replace hex and rgb. They will soon become the standard in web browsers. They open up more colors than are currently possible. The Expanding Gamut of Color on the Web | CSS-Tricks - CSS-Tricks

Hi, I’m not sure if this is new since the May update, but I wonder why “empty” (all elements hidden) Auto Layout Frames keep the size of the last hidden child (and I do not mean last in the list, but the last element to have been toggled out of view by the user), making them not-0px high even with nothing in them. See here a file with a Frame with three hidden rectangle: the Frame keeps the size of the last child rectangle to have been hidden. When adding a 0-px Frame to the AL frame, and toggling this 0-px Frame off last, the container goes 0-px. In my opinion, empty AL Frames should have a height of 0. What do you think?

I’m sure this is a request that has come up many times before, but I’d really love to see the ability to configure haptic feedback in Figma.Many mobile interactions rely on haptic feedback, such as pull-to-refresh, confirming whether a gesture will trigger an event or not (like drag and drop), or providing tactile feedback when an interface changes state.For truly faithful prototyping, haptic feedback is something Figma is currently missing, and it makes it harder to accurately replicate the final user experience.That’s why I’d love to see haptic feedback integrated into Figma prototypes, with the ability to configure when and how it’s triggered.

One thing that’s become frustrating is that it’s no longer possible to collapse just the left panel while keeping the right panel visible.In UI2: Ctrl+Shift+\ only hid the left sidebar. The collapse arrow on the left also only hid the left sidebar. Now in UI3: Both Ctrl+\ and Ctrl+Shift+\ collapse both left and right panels. The collapse arrow also hides both panels together. This makes workflows harder for users who want to maximize canvas space but still have quick access to the Inspector or Design panel on the right.Request:✅ Please restore the ability to independently collapse the left and right panels — both via shortcut and via the left collapse arrow.✅ Even a setting in Preferences to toggle between “unified collapse” and “independent collapse” would be great.

Annotation mode is useful, but when you write a lot of specifications, it clutters the screen and makes it difficult to concentrate. I want it to be an experience where you can read each comment in turn, like comments. Ideally, it would have the same visibility as the comment panel.

Hi Figma community 👋Our team manages a shared design system that is actively evolving, and we frequently update components to improve usability and consistency.One challenge we often face is tracking component updates across project files. While Figma provides version history and “Compare with previous versions,” identifying changes requires opening each component individually. This becomes especially time-consuming when updates affect many components or multiple screens.It would be extremely helpful if Figma could provide better visibility into component changes, such as: Notifications when a referenced component has been updated Visual indicators showing which components have changed A clearer diff or change log for component updates This kind of functionality would greatly help designers, PMs, and developers understand whether updates require action on existing designs.Curious if other teams managing large design systems experience the same challenge? How are you currently hand

Hi Figma team,My team and I have been experimenting with slots recently. I'd like to propose a feature enhancement: when a component with properties is added via a slot, those properties should be accessible directly from the main component.Ideally, these nested properties would surface automatically, eliminating the need to click deep into the component hierarchy to make edits.

I never use the AI Agent. I have no desire to use the AI Agent. I resent Figma’s attempts to get me to use the AI Agent. Yet, when I create a new Design file, the AI Agent panel is open by default. Two questions:How do I select either “File” or “Assets” as the default pane that opens when I create a new Design? When will you release an update that allows me to remove the AI Agent button from my left nav bar?

Hello,some feedback from my side regarding Folders, I like the options of a nestable folder, but I find it hard to navigate to the files I’m looking for. The folders are named, but the file thumbnails that were visible with Projects were a huge readability feature that I’m really missing now.I was searching for it in settings, but couldn’t find a way to set it. I actually added a description to a folder, but did not actually see not one place that the description was shown? This part is especially confusing.If I could make an improvement suggestion to a current implementation it would be to have a setting to show or not to show some folder contents thumbnails, similar to the previous implementation.Fingers crossed this can be done!

It really annoys me that Figma automatically creates subfolders when you export an element that’s inside a component and has a ‘/’ naming convention. I always have to go back into the folder and delete the folders or rename everything. It would be great to have a simple checkbox toggle in the exports panel to enable/disable creating subfolders, similar to Illustrator.

I usually share my Figma file with developers so we can work on the same file at the same time. This is very useful because developers can inspect the designs and start working on them directly.However, I sometimes need to make changes or try different solutions before the design is actually ready for development.The problem is that developers can see these changes immediately while I am still working on them. This can be confusing, especially when I am still experimenting, changing layouts, or making updates that are not final yet.What I would like to have is a simple Draft / Publish option.When I start making changes, they would stay in a Draft version that only I can see. Developers would continue seeing the latest published version.Once I finish my work, I could click “Publish Updates”. At that point, the changes would become visible to developers, and they would receive a notification that there are new updates.It would be even more useful if Figma could highlight the updated scre

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.

In Finland, we have to attach the invoices to all card payments for bookkeeping. Now I need to every month to go to Favro and manually download the invoice. Please add a feature where I can define an email address for the invoice emails and automatically send new invoices in an email with the PDF invoices attached so that we can automate the download and processing of the invoices. The subject of the email should have the same structure each month ("You Figma invoice YYYY-MM-DD) and the PDF invoice name should be unique and contain the date of the invoice, for example, Figma incoice YYYY-MM-DD

It would be very convenient to be able to create folders for saved plugins and sort them yourself, which would make it easier to find the plugin you need when you don’t remember its name while working in Figma. For example, you could create a group for plugins called “Palette,” which would contain only plugins related to choosing a color palette. This would greatly simplify finding the right plugin for your work, since you’d know which plugin you need and in which folder you can find it — without having to know the plugin’s name and search through the list of all plugins, especially if you haven’t used it in a long time.

I just want to adjust the page settings for each page “frame” so to speak so I can make it wider. It’s not clear that this is possible.

Whenever I’m creating a component with variants, when it hit the plus button, it puts a copy down and to the right. hit it a couple more times and they just keep going right.My first click after hitting the plus is to turn on autolayout for the component. Feels like this should happen by default. This view can’t be useful for anyone.  

Hello, It would be more than interesting to be able to create variable at a component scope. And of course instance to inherit those variables. Why ? it would be a good way to organize variables. One file can have a lot of different components and subcomponents = a lot of variables. it would give us the possibility to ease prototype creation by preparing upfront variables in components library. it is a good way to get rid of variants. I mean variants are nice but variables are far better :). it would give the possibility to create different set of variables corresponding to different state of the components faster.

I’m developing an icon set, and attempting to export a set of uniformly sized SVG assets. Each icon has a 20 x 20 frame, with the vector graphics nested inside. In some cases, the graphics have strokes that exceed the edges of the frame, even though the vector paths themselves are inside the frame. In those cases, when exporting to SVG, the viewbox is greater than 20 x 20. How can I restrict the viewbox to a very specific size? Seems like this post is related, but I’m having a hard time understanding the guidance: SVG exports at a different size to W & H values in editor - #3 by Corin Thanks!

Every time I exit Figma and come back, the previously selected sort order is lost, and it defaults to "Last modified" – "Newest first". Previously, the selected sorting option was always preserved.

With the new update, we have a great new feature, but unfortunately, it’s not usable with our component structure. Exposing all props of a nested instance also exposes props that we don’t want in the context of the consuming component. What if we could also select which properties to expose? This would lead to a cleaner sidebar with only valid props.

In Figma prototypes, elements set to Fixed are automatically rendered above scrolling content. This makes sense for common UI elements such as fixed headers, navigation bars, or floating buttons — but it prevents other very common web design patterns.For example, a background element may need to remain fixed while the page content scrolls above it. Currently, this requires workarounds with nested viewport and scroll frames.I suggest separating scrolling/positioning behaviour from layer order, similar to how this works on the web with CSS position and z-index.A simple option for Fixed and Sticky elements could be:Always on top – current behaviour Respect layer order – the element remains fixed/sticky but retains its position in the layer stackThis would make it possible to prototype fixed backgrounds, overlapping sections, layered sticky elements and other common web interactions much more naturally, without restructuring the entire prototype.In CSS, position: fixed or position: sticky 

A great feature to have is text styles not breaking when a designer is using Cmd + B to bold a word or phrase. Currently it unlinks the text style and applies the bold to the underlying font. It would be great if there was a feature where when I use Cmd + B, it swaps to that text style in the library (where the style already exists) and updates in the property panel as well.

I want to present a full page prototype in Figma Design where most interactions are built in Design, but more advanced sections are built in Figma Make. Today, a Make embed can be shown on the canvas, but not as part of the actual Present/prototype mode flow. I would like Make content to render as an embedded block inside a scrolling Design prototype, so advanced interactions can be presented in context together with the rest of the page.