Suggest a Feature

Is there a way to see more details when getting updates when there are changes? having only a preview and/or comparison does not help at all. It would be cool to see what exactly (style, element etc.) has been changed.

Figjamのカラーはかわいすぎるので、私のビジネスには向いていないです。いつもひとつひとつ手作業で変更したり、Figmaにコピーして変更していますがとても煩雑です。 proプランでもカラーの設定を任意に変えられるようお願いしたいです。

Seems when there is a lot of content, the left nav of endless scrolling of slides and sections is extremely difficult to navigate. I regularly notice designers would use Figma to organize slides (before Figma offered “slides” functionality) in a grid, with section slides to the left. This makes it extremely easy to jump around to sections of content in slide decks. Seems like being able to flip to this sort of “overview” view would be extremely beneficial in the Figma slides editor.

I just had to search the longest time for the boolean property. I actually ended up switching back to the old UI to create the property and upon more research and talking to team members, I found where the boolean properties are hidden. First, there is no tool tip when hovering over the highlighted item, so no explanation on what this button does, even though every other item in the appearance section has a tool tip. Upon pressing the unlabeled button, I get a list of variables. The + in this view, I would assume creates a new variable, since I am in a variable window. Finally, I found that clicking that + button actually creates a boolean property?? I have no idea why this is paired with creating a variable. Why is the boolean property not clearly surfaces like variants, text, or instance properties are? I suggest surfacing this property, like it originally did on the old UI to create a faster and more intuitive work flow.

i allready see aout 2 flaws in this system, the first one is that it is not designed for that purpose, the second one that it needs a file format. (please excuse the bad gramar and sentence building aswell as the typos my hands are cold and i am tired sorry) now i need this version because i am not able to afford a plan for private reasons, that is out of discussion. and what i want to do with it is screw around with it when i am bored and sometimes actually design stuff with it and for both purposes it is a great tool. i just found out about this flow thing system because i tried to ignore the prototype button because i was sure it was some text coding tool. turns out it wasnt. i found out about it (this is important) about splines states and stuff, but it is an 3d tool and a school compunter reduces itself to atoms trying to run one. so what it thought is maybee Figma got some addon or something with that i could make animations or even better entire apps. and then i found out i coul

To make it easier to use the text case feature, it is recommended to add this feature(which is available in the text menu) to the right-click menu of text

I’m using this function hundreds times a day, and need it. Why not?

Scenario: I normally keep all my components on a separate page and I like to NOT organize them into frames but use a plugin to group and sort them by name. Problem: However, when designing for a dark UI it’s very frustrating to use the assets panel as most components are close to invisible. Often a component itself has no background color so the bright foreground elements are displayed on a light grey rectalngle in the assets panel. Solution: Instead of this light grey background, the assets panel should use the background color of the page a master component is located. When designing for a dark UI it’s not uncommon to also set the background color to a darker grey to make it easier on the eye. So this solution would also work if you do not keep your components in one single page but across the entire document. And if one likes to organize them in frames, then the frame’s color could still kick in.

Hi Figma team, I’d like to request a feature that allows us to reorder properties in components. Currently, properties such as Boolean, Variant, and Text are displayed in the order they are created, and there is no way to rearrange them. This can make managing complex components with multiple properties difficult, especially when new properties need to be added later on. Here’s why I think this feature would be helpful: Improved Organization: Allowing reordering would help designers group related properties together, making components easier to understand and use. Flexibility: When designs evolve, we often need to introduce new properties. The ability to reorder them would let us keep our components tidy without deleting and recreating existing properties. Efficiency: It saves time by reducing the need for workarounds, such as renaming properties or re-creating them in the desired order. I believe this feature would benefit many designers working on scalable design systems. Thank you

Make comments window resizable same as layers panel

I do appreciate the new features like variables and conditionals and they help a lot in building prototypes. But there are some improvements that are needed to make this product truly great: When I am editing the interactions, the panel is super small and cannot be resized. I have variables in groups, so I can usually only read the group name and not the variable name. This means I have to open every single interaction to understand what it does. It would also be great to not only see the variables but already the interaction. The panel (popup) needs to be resizable. The search and select in this panel is also not ideal. I need to make sure that the element the interaction is on is at the very top of the screen. Otherwise the select disappears from my screen, I cannot read anything and I have to close it, move the canvas and start over. When I set a variable and type in “true” and then hit enter, I expect that this interaction is saved and the select dropdown disappears. Instead an “=

Hi There, As Figma is the all in one tool for our daily jobs, I was thinking that if we could directly add notion tasks through our feedback addition on Figma, would be great. Imagine having a feedback session with you team and you come up with some changes or ideas that needed to be implemented in Figma, if we could somehow bind this commenting of Figma to notion boards, could make our lives way more Figmaish!

Set one variable mode for an entire file to reduce the friction of updating the variable mode on each page for a large file.

I, like many designers, have my own workflow and work style. This includes the way I tag up my designs with annotations, make notes about design decisions, and prep screens for use in other formats (like presentations). I would love to have my own personal library of “things”, including my own annotation styles, type, colours, components etc. that is only “published” for me - so that I don’t have to make and publish a library that will be available to my entire team. The reason I want some sort of “publishing” ability is so that I don’t have to go and get the things I want to use, or recreated things every time I work on a new project in a new file. And so that I can push my own updates that only affect my stuff. Our team has a File Management library with a bunch of stuff for everyone, but like I mentioned above, there are things specific to my workflow and style of presenting work that I’d like all-over-access to (and wouldn’t fit in the team File management library). Would I be abl

Currently working on some column components for our design system but they have the option to start with no rows which leaves just the header cell. This cell is the same for some of the different types of columns making them appear the same in the component library even though the content is different once more cells are added. It would be nice to customize the thumbnail shown to designers in the component library to give a better preview of the component when the default is not helpful.

Currently, the first component within a variant is displayed as the thumbnail for the variant in the asset tab. Here is an example; (Image shows “primary button” as a thumbnail for the variant) This can be problematic when the first of its kind is not visible ex. invisible divider, or small button… I want the ability to assign the variation to be the thumbnail displayed for the variant in the asset tab.

In the case of multi-designers, multi-projects and multi-documents, it is really tiring to manage and classify files. I hope to have file management with tree structure like confluence!!! 🥶

Hello, Is it just me or is it challenging to prototype w/ Variable Modes vs. Variables? I kind of think of it like managing states in Canvas vs. Prototyping. In canvas, toggling modes is great, but with prototypes, mode toggles become almost useless unless you’re doing a broade based switch. Then ultimately what’s happening for me right now is that I’m creating both mode differences and single variables so I can prototype with precision but also handle manual changes in Canvas. One example would be setting up a profile card that is disabled, but based on another component selection becomes active. In canvas, you manually make adjustments and point arrows for what happens conditionally. But if you try to move that logic into an active clickable prototype you either lose precision or break your project entirely. Right now the only solution is to create individual variables and maybe multiple collections… But of course this creates confusion all around. There’s a gap in the logic b/w pro

Any way to restrict fonts shown to users by default? Would like to see only assets we’ve allowed to simplify choices for designers. Additionally, fonts (like Noto Sans) are brutal to work with. Only want to support variants that are used within the design system.

All files open in dev mode = not a fan. How can I turn this off? It isn’t a great user experience to have to do this manually every day for every file. Can the regular, non-dev mode, be the initial load standard? When you have 20 files you’re in daily this just isn’t the best.

An annoyance I deal with on a daily basis is having to change what feels like nearly every single prototype interaction, because Figma has chosen something else for me. In practically every interaction, I use the Spring - Slow timing, but unless I’ve just literally just created an interaction and made a second one, Figma chooses ‘Ease out’'. Also, when I do switch it from easing to spring, Figma always changes my duration to 600ms. This is incredibly frustrating, as I’ve already set the duration I want, but Figma messed up the easing, so now I have to also revert its duration decision. I’d love to get a statistic on how many extra clicks this has cost me over my years of using this software. Figma should use the most recent duration and timing functions chosen, and not change the duration when changing easing modes.

Currently, when video files are imported into Figma, we lose access to their original metadata, making it difficult to locate the file on the hard drive. Could we enable the option to view the link and metadata of imported videos to streamline the process of finding them later? For example, if I import an image and later delete it, I can export it back from Figma and retrieve the original file. However, this is not possible with videos.

I have a problem with a shadow that faces the Android engineer when applying the shadow styling “the shadow modifier is not compatible with this design in Figma” and the outcome shadow is not the same as the design Is there any solution or plugin to fix that?

Proposal: Locking Page Names to Prevent Accidental Changes Accidentally deleting or renaming a page is a common issue, especially in collaborative environments where multiple designers work on the same file. This becomes even more critical when dealing with essential files like a design system, where unintentional changes can cause confusion and disrupt workflows. I suggest introducing an option to lock a page name, preventing accidental edits. When locked, renaming would require an intentional action to unlock, similar to how locking layers works in Figma’s layer panel. Key benefits: Prevents errors by reducing accidental renaming or deletion of critical pages. Ensures consistency across the team by preventing accidental changes, allowing team members to reliably find and reference the correct pages without disruptions or confusion. Protects key files like design systems from unintended changes. This simple feature could save time, reduce frustration, and enhance collaborative effic

Please increase text contrast and add padding for the component description container. Even better remove the rounded container completely, as it reduces the width of the description text. → Especially for larger amounts of complex documentation, this currently really is quite bad readability.