Suggest a Feature

It would be great to be able to store the files we share within one of our projects, without being the owner of the file. At the moment, if you don’t own the file, you can’t put it away…

I wish I could hold down something like control, option, command, and/or shift when dragging to KEEP the dragged layers position in the layer list. This would be a huge benefit!

Hello there 🖐️ Environment is important and the change taking place is irreversible. 💣 Every day we are destroying our place of life a little more, and the internet has a huge role in this change, our sector of activity has a role in this change. (small reminder: the internet emits more greenhouse gases than the air sector) 🔥 This is why Figma, our favorite tool, must make decisions in favor of the environment. Encourage us to be careful, optimize our images, keep files light, delete unnecessary files, etc. 🍃 The first step would be to know how big our working files are. It would be nice to add this information in Mo below the project name. 🔍 There is an exemple :

It would be great if Figma had a way to automate, curate, and provide data visualization to Figma library analytics each month without the need for API integration to pull to a website. It would be helpful to have comparison data from month to month as well as a tool that could create reporting for managers such as a PDF export. This could be a part of Figma in a viewable area where you have the opportunity to configure the libraries and properties you collect data on or a plugin that automates this process in a similar manner.

I have been trying to figure out how to do this but I don’t think its possible. How great would it be to be able to reference the colour style of a nested component and have that be applied across the new component. This would mean that you don’t need to design a huge amount of variants to just change the text colour. Rather you change the nested component (which already has a number of icon and colour changes) which has colour styles baked in, then the text layer references that colour style and updates automatically.

Pls incorporate an animated keystrokes feature during prototyping? It would be so nice to record videos or GIFs of simulated user input, especially given the growing prominence of AI chat design experiences.

Would love the ability to have a single page live within two files. Sometimes I have a page with items where they could potentially live in a few different files. Right now, I’m just using a widget to link to the other pages, but would love if a page could sync across multiple files. Kind of reminds me of how instead of folders in Gmail, you use tags, so you can tag a single email with multiple relevant tags. I want something like this for pages.

It would be very helpful to sort Figma files by File Owner or “My Files”.

The current layout for stroke per side is top/bottom/left/right, if you go into custom, it is left/top/bottom/right if going clockwise, then if you tab through it goes left/right/top/bottom. I think it would be more intuitive for designer and developer for these to be setup how it is with border radius. Going top/right/bottom/left, in a circle clockwise order.

while presenting my software design in Figma I was facing problems using my navigation prototype. and that was because of hover effect on Present page of Figma.

Showing the entire description in the tooltip when hovering over a component in the asset panel can create a large amount of text that is not necessary to understand the usage of the component or to choose a component. Keeping the description short will prevent adding more important information in dev mode or under the component description in the right panel (or in the new modal when it returns) My suggestion is to add another field (header, summary) above the description, that will be shown on the tooltip in the asset panel, where the full description will be shown in Dev mode and in the right panel. Alternatively, maybe it is enough to truncate the tooltip after a few lines of text, this way the author can decide what will be shown in the tooltip and what will only be visible in the description

Firstly, I’d like to express how impressed I am with Figma. It’s evident to see why it’s leading the way in UX design and collaboration. However, as a disabled visual designer, there are key features that, if addressed, would significantly enhance the usability of your platform for people like me. A few months ago, I communicated my challenges when I began using Figma. Having spent two decades in this industry, it’s concerning that this is the first design tool I’ve struggled with due to my disability. My fear is the potential risk of becoming irrelevant if I’m unable to efficiently use Figma, which is now a mandatory skill in most modern UX/design jobs. I recognize that many Figma users might not face these issues. However, I believe there’s immense value in enhancing its accessibility. Here are some features I believe would make a considerable difference: Extended Toolbar Options: Allow users to click for commands like grouping, ungroupi

On Layers panel, the divider between the top list (pages) and the bottom list (layers) is really not easy to see and therefore grab. Could we have a more comfortable one? Minimalism is cool but not when it goes against usability. Thanks!

Inspect tab is least effective to me with the way each section is put one after the other. There is not option to move the sections up & down or remove sections that I dont needed. When working in developer mode, layout & code sections are of top priority to me & they need to be shown at the top always so I can copy the code. Please provide option to perform above actions.

Currently Figma allow design system authors to have alternative titles of components using the component description. I’m suggesting adding a new field instead of having many different titles to the description field. My workflow include onboarding many new designers so preparing for their different “Naming” Backgrounds is beneficial without impacting the actual component description.

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

Been enjoying prototyping with variables and conditionals! What would have been 68 individual frames, I have a complex prototype using 3 components and 5 frames. Thank you Figma!! In the future, it would be great to have efficient ways to apply actions across multiple frames such as: Copy/paste actions Group multiple actions into a set of actions a user can copy and paste Select multiple frames and append new actions into each’s interaction set Variables with functions/series of interactions???

I searched but couldn’t find a request like this. Now that you can queue up a bunch of commands in a single interaction, it would be nice if you could inject a pause in between executions. Example: On click set variable showFrame to true Wait 300ms Set variable x to 5 Right now I’m achieving this through a hack. I have a “hotspot” component with two variants, and I do this: On click (of variant 1 of the two-variant hotspot) set variable showFrame to true Change to variant 2 dissolve 300ms Set variable x to 5 This works, but it would be cool if there were a more straightforward way. Note if you need more than one “wait” in an interaction using this hack, add more states to the hotspot, as for whatever reason, changing back to variant 1 doesn’t work.

When moving and adjusting large designs or flows, the comments remain where they originally were. I want them to come along for the ride and stay with the component or area on the Figma where they were originally placed. I don’t want to have to go and grab them to put them where they were. There was a suggestion made by a PO earlier and it’s not the same use case. I don’t need to move frames to other pages. This is more about work in progress on the same page.

When selecting a number variable, it would be helpful if the actual number value is shown next to the name. Color variables have the color swatch for easy recognition. Number variables could mimic Text styles, where the font size and line height are shown next to the name.

Please allow clicking a component to: change the variant of some other component show or hide an element

Design reviews, ideation sessions for fully remote teams. Right now we have to switch between the video calling app and Figma. It feels more natural to schedule a video call directly from Figma since we already have the real-time collaboration out of the box.

Please allow elements to be shared across variants. It’s very brittle to rely on names for connections between variants. It’s also very tedious to have to give everything a unique name.

Formatting like H1, bold, etc. currently aren’t reflected in the hover state of components in the Assets tab. The minimum solution to the problem would be at least not to ignore line breaks.

I would like to be able to bulk edit component descriptions. For example if the descriptions are structured with headlines that are consistent across all components, I’d like to be able to edit those shared text elements in bulk, instead of going through hundreds of components individually.