Suggest a Feature

At the moment, I can only apply a boolean property for show/hide to specific layers of a component. Why can’t we have the ability to apply a boolean property to an entire component? For what I’m building, I need the ability to show & hide entire components. Right now, the only way to do this is to restructure my components so I can add the boolean property to each layer. This is really tedious. It takes extra time, adds churn, and adds more boolean toggles to the panel than should be necessary. Please consider adding this into the next release.

I am using Figma from almost 2 years. It’s a great tool. Previously I was using Windows 10 yet recently switched to Linux(Ubuntu). Figma doesn’t have any official release for Linux. There are some Unofficial desktop versions but they are “BUGGY”. I request you guys to release an official Figma desktop app for Linux.

People have been complaining about this for years. I have to add ® and ™ to strings of text in my artboards. The superscript version of the character must be the same size as the rest of the text string, or it will not be vertically aligned properly with the rest of the text. The ®™ symbols are much too large, especially in headlines, but if you reduce the font size of that character, it drops down too low and is no longer in the superscript position. In Sketch or any other proper app, you can adjust the baseline of the specific character (baseline shift) so that you can re-align it properly. You can EASILY accomplish this in CSS and create specific styling for the “sup” tag which handles this in code. Why is it nearly impossible to replicate what is easy in any other app in Figma? I’ve seen people complaining about this since 2018, so I take that as an assumption that Figma will never fix this issue? The only way to get a properly aligned and size

Using overlays greatly reduced the amount of duplications in my frames, still there are flows when I start with an overlay in a given position and would like for it to be swapped with a differently positioned overlay. Currently I do that by targeting a new frame and using a timed overlay opening from that. Looks fine in the prototype, but adds few extra steps/duplications that I’d happily do without.

Hey Figma Community, I’m excited to kick off a discussion on a feature proposal that I believe will significantly enhance our workflow: an easy way to remove missing libraries and immediately conceal the styles copied from other libraries to be applied as core visual styles within the new library. The Problem As we continuously evolve our design projects, we often encounter situations where styles and components from old libraries are no longer relevant or used. However, these linked styles still persist, creating unnecessary strain and clutter within our current design files. It can be quite frustrating to see missing library notifications, giving the false impression that essential design elements are missing when, in reality, they are not even utilized in the new library. The Proposal Introducing a Complete Detachment Button for missing libraries, which will: • Remove Missing Libr

When user does something in the plugin UI and then wants to undo it, it breaks the flow when Cmd/Ctrl + Z doesn’t work. Even I sometimes try to press it and nothing is happening, this makes me frustrated as a pro plugin and Figma user. Currently you can implement undo manually by detecting the shortcut and communicating the undo action to the plugin backend — that’s not too hard. But things quickly become complicated if you want Redo to also function (since it’s not available in the API, you’ll have to build your own undo/redo queue). And then other shortcuts can be used by users in different contexts too. It would create a good user experience if you can trigger shortcuts in Figma, either by passing them from the user action event somehow or by simply manually triggering them (the latter would also open up a lot of other possibilities). In a similar way, it would be great if a plugin can get shortcuts when the plugin window is not in focus. This would create a

I don’t use Figma all the time, I don’t want it to run anything on startup. It’s frustrating to manually remove Figma from Login Items, since it automatically adds itself there again. It would be nice to have at least an option to disable it in settings, or even better - remove that functionality at all, since it’s not user friendly. I want control over what and when the apps do at my workstation. P.S. If it’s needed for updates check - I’m more than okay to update on app start

Figma needs an autolayout option for tables, or grids. None of the extensions or apps work well. Designers like me need to make grids all the time. Right now, I make autolayout rows, but they invariably need to be synced with the column header, which I do manually by editing fixed width.  Please add an autolayout for grid that would allow items to be in both a column and a row. 

In order to get a more accurate, real-world idea of our design system’s usage, we need an option/filter to exclude certain teams from the analytics data. Specifically… us: the design system team.Our own experimentation, maintenance, etc. is bloating and cluttering our library analytics, so we would like to be able to exclude ourselves, as well as any other teams we deem necessary (ex: we will sometimes create temporary teams for testing and experiments).

As a design systems manager, I would like to be able to exclude branches while reviewing library analytics for component, style, and variable usage so that I can find and update the main files that are dependent on my design system.Use case: I am currently trying to deprecate an older version of a library using Library Swap. The easiest way for me to do this is to use Library Analytics to find all files on my team that use the library’s components or styles. However, branches also show in this list, and I can’t see that the file is a branch or what file it is branched off. I would like to be able to filter branches out, since they will get the update from the main file anyway, without having to click in and open each file to find out it is a branch.

The library we are using in our company can be modified by several people in the team. When I want to publish changes to the library, sometimes I would see changes I didn’t make. Or sometimes it was a change I actually made that had an impact on another component, but it’s difficult to understand right away given that you can’t have a close look at what has changed exactly (the preview is so tiny!) It would be great to have some kind of before/after preview each time I hover one of the components in the “changes” list. It would reduce the risk of publishing wrong components that are not well built. Because right now I always have to ask my team if they have touched anything in the library which is getting tiresome to be honest. Thanks ✨

Hello, I would like to know if it’s possible to select several words in a text layer, for example to put them all in bold or a different color from the rest, but all at once. Like in Word or Google Doc, I believe the shortcut is ctrl + select the desired words or part of words. It would be useful if it also worked across multiple text layers. I tried all the shortcuts I could think of but nothing seems to work… Selecting words one by one and apply the wanted properties every time feels soooo tedious. Maybe its not a popular request but that would be so useful. Thanks !

While working to build out our design system with variables, it seems like there isn’t an easy way for developers to view a full list of all variables built into the design system without having edit access to the design system or without the variables being put into a different reference system like a notion page as the master file and have Figma reference those values.

It would be great for the Windows desktop app to support snap layouts in Windows 11. Snap layouts allow a user to hover over the maximise or restore button and quickly snap that window into a layout.It seems that another user has requested this in a roundabout way (below), however this feature can actually be enabled for apps with custom title bars. Microsoft documentation: https://learn.microsoft.com/en-us/windows/apps/desktop/modernize/ui/apply-snap-layout-menu\

Dear Figma Support Team, I am writing to inquire about the current support for color fonts in Figma. As a designer, I greatly appreciate the versatility and creative possibilities that color fonts bring to my work. I have recently been experimenting with various color font formats, such as OpenType-SVG and COLR/CPAL, which allow for intricate multi-colored typography. However, I have encountered some challenges when attempting to utilize these fonts within Figma’s design environment. It appears that Figma currently lacks full support for color fonts, as I have experienced difficulties with the proper rendering and editing of these fonts within the platform. It would be immensely beneficial if Figma could extend its capabilities to fully embrace color fonts, enabling designers like myself to fully explore the potential they offer. Color fonts have become increasingly popular, allowing for more expressive and engaging desig

I’m building a stable prototype with Figma Make, and the credit model is a practical blocker. I’m already at ~500 prompts/executions on this project. Figma’s own positioning puts 3,000 credits/month at ~50–70 Make prompts (~43–60 credits per prompt on average). If my workflow needs ~500 prompts, that’s ~21,500–30,000 credits, or ~7–10 months of the included allowance. I’ve also seen 4,250 credits disappear without reaching a usable prototype outcome. The main problem is that because Make is agentic, the cost isn't fixed per prompt and you can't accurately predict it before running. What the agent chooses to do (actions, files, iterations, model) determines billing. Because you can't confidently plan or iterate, it's a budget black box.Make only seems feasible for small demos at the moment, or if you manage to iterate with almost no reruns. Sometimes it is not enough even for a small prototyp

We’re working on a larger Component library that includes non-published components (components with the prefix _ or .) as base components in order to simplify large, complex components. We intended – in some specific cases – to offer regular components as templates, that a designer would then have to detach and work with a bunch of base components to build the desired design. What we have come to realize with this approach, however, is that these non-published components don’t receive updates from the library when they are updated in the main library. Is this intended behaviour? We basically have the option to simply publish these base components as regular components, but that of course would mean cluttering up the assets overview with a bunch of modular components.

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

I create a concept in Figma Make and want to test it with the team and potentially with customers, but they can see my underbelly chat. Is there a way to hide the chat?

Organization would be immensely helpful if we could create folders for our drafts. I want to be able to organize my drafts into different categories (such as UI kits, Ideas, Wireframe kits, iOS, Android, etc…) so I can find files easily. Right now, the drafts page is a huge jumbled mess and I can’t create Team pages for everything. Maybe something as simple as being able to add ‘tags’ to each file, similar to Zeplin.

Why this matters:  Protects sensitive client data Prevents accidental access by team members Adds an extra security layer beyond sharing permissions Critical for agencies, enterprise teams, and regulated industries  This would be a huge step toward making Figma more enterprise- and agency-ready when handling confidential work. Hope the team considers this. 👍

When marking a comment as resolved, we are now automatically moved to the next one. I’m wondering if or how we can disable this behaviour?My work flow being to go from screen to screen of user flows, and not comments to comments, this is very disrupting as it can bring me anywhere in the file, and I need to find and navigate back to where I was. I understand this might be useful for reviewers that only goes through questions left by other people, but this probably not most users, so it would be useful to have the ability to disable this feature.

As the title suggests, it would be amazing to have a collection list of links and then use that list as URL Links for components.

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.