Suggest a Feature

When using the People / Billing groups overview, I want to be able to filter out so that I only see users with paid licenses. Either by combining “seat type:Full + Dev + Collab” or to be able to set “seat type:not-Viewer”. We have a lot of users with all kind of licenses and a lot of viewer only licenses. When reviewing the users I have to switch between viewing Full / Dev / Collab and I’d like to be able to see all of those paid licenses together without general viewers and not have to switch between them. 

Currently, I have to manually scroll through the Recent tools list every time to find a tool I use frequently. This becomes time-consuming and inefficient. 

Clicking between two pages is inconvenient – there should be a hotkey for that. Context — I have components in Page A and need to see the changes I make on Page B. I make lots and lots of small iterations to my design and want to swap between Page A and B quickly to see results. Solution — A back and forward button (or hotkey) that let’s you jump between pages you’ve last visited and forward again.

It seems to me that the idea of a view only mode should also include the ability to swop between themes. I have 5 themes for my files and in order for the clients to see them I have to put 5 screens on the page and change theme manually before they go and view. Is there a reason why Figma doesn’t allow the users in this view only mode access to just swop between them?  

Hey Figma.I am having difficulty using Figma due to a few usability issues.First, hiding the layer panel should only hide the layers themselves, not the entire left navigation bar. That way, I can still access features like variables and agents without expanding the layers panel. The 'Minimize UI' button could also be placed on the left navigation bar. Alternatively, the navigation bar buttons could act as toggles to show or hide their respective panels—for example, clicking the 'Files' button would show or hide the layers panel. This feels much more intuitive. Additionally, switching from a fixed component view to a floating component view feels quite jarring.Second, when the layers panel is minimized, zooming in on a selected object doesn't bring its full dimensions into view because parts of it get obscured by the properties panel. I'm not sure if this is a bug, a limitation of 13-inch displays, or just standard behavior, but it's an unexpected and incredibly frustrating experience

It’s great that Slots are here and getting better. We’ve noticed that sometimes, Slot warnings can be easy to miss when our designers start to ‘tighten up’ designs for review or delivery. It would be great is the Check Designs feature could also check for Slot warnings when limits are bypassed.

{Commenting as Guests} Clients wanting to give access to prototypes to temporary teams without the need to create accounts as guests only, allowing comments and feedback within Figma prototypes. Possibly allowing these users to make comments on prototypes as Guests with temporary names.

Hello everyone ! 👋I’m surprised that no one has shared any frustration about the tiny click + drag zone for font size adjustments yet.Currently, you have to hover the very small left edge of the font size input field to trigger the click + drag behavior. The issue is that this border is extremely thin—much thinner than other properties. For example, other input fields include an icon to make the click + drag action more intuitive, but the font size input lacks one.A simple fix would be to add an icon (like in other properties) to the input field. Alternatively, if you prefer not to use an icon, adding some left padding to the input would also solve the problem.Personally, it's not a day-to-day issue for me — it happens mostly during specific tasks, like logo ideation where there's a lot of text sizing work involved. Maybe that's why no one complains about it.  

The descriptions written in variables should be shown when selecting/picking them in respective pickers - maybe as tooltip? Otherwise I don’t see, how this could be accessed/taken into account by the users of our library.The grid view of the color picker shows the actual name as tooltip for example. This could also be used to actually show the description. 

This has been mentioned here: Hide layer using variables - #5 by Andreas_Braendhaugen1 Invert boolean variable for layer display - #14 by Desislava_Slavkova Inverted Boolean Property - #2 by drewcovi_usb but those topics are all closed. I am looking for the availability to HIDE a layer when a Boolean variable is TRUE and SHOW it when it is FALSE. So, the inverse of the default/current behavior. I want to do this without using components. Use case: When a variable is true, show one frame. When that same variable is false, show a different frame. I can get basically this by using two different variables: but it would be more convenient to be able to do it with just one. Just give me a Boolean toggle when the variable is used to say if the variable should be inverted or not.

Is there any plan to be able to create the gradient itself as a variable? For example, if I wanted some themes to have a solid background variable but others to have a gradient?

So many times I may detach a component or copy and paste a frame and have to go one by one deleting each annotation that carried over. Would be great if I can just select the frame and have some sort of shortcut to delete all annotations. Would save me a lot of time, I do this at least a few times a day and some of my frames have over 20 annotations. (working product designer) 

Please add independent loop controls for animated component instances in Figma Motion, so an instance placed inside a parent frame can repeat on its own timeline without forcing the main component duration to match the full frame durationExample: a 2-second animated component placed in a 10-second frame should be able to loop continuously for the full 10 seconds while the parent frame animation continues separately.

I would like to make lines of text that, when hovered, display actions in an action bar. However, when I move the mouse over the action bar, I leave my frame, since the action bar is in absolute position. We’d need an option to make absolute elements hoverable and clickable even if they are outside the main frame.

Simple but yet powerful addition would be support of the categories for Figma CMS content. Along with different type of filed you can add “Tags”, and allow users to create them when they add new content items.On the front side, simple filter components with showing “All” as selected by default tag and list of tags after. Together with my proposed pagination idea Figma Sites would be able to support much bigger pool of builders and designers.

I think it would be great to see keyboard shortcuts for the ‘Auto height, Auto Width’ text box sizing features. I use these all the time and it would be really beneficial to have a quicker way to change these 🙏

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!

Although I find the new autolayout UI extremely convoluted and overdesigned, the ‘hug/fill parent’ feature is great. However, It would be immensely helpful to have more control over how the elements fill the parent. Currently, the only option is for the elements to fill the remaining space, but oftentimes, I need certain elements to take up a certain proportion. Example: I need element-1 to take up 2fr (~66%) and the rest to take up 1fr (~33%). It would be a game-changer if we could use ‘fr’ units. Framer does this beautifully and it’s vital for efficient, adaptive layout workflows:

Add native two-way sync between Figma variables and a design tokens file so changes made in Figma or in code stay aligned automatically. Figma already supports variables through the REST API and Plugin API, which teams use today for custom sync workflows, so built-in syncing would reduce manual reconciliation and plugin dependence.

Hey Figma So I have been building our component library and stumbled through this issue where I built parts of the component that are not needed to be published because they are only make sense to use them inside the main component. So having these nested components being published make it confusing and clutters the library. Can we please allow Instance swap property and Slots to have these components show up I literally picked them as Preferred component but they won’t show up since they are marked as Hidden.  

I have a single page site that has a nav bar that scrolls to different sections on that page. I want to add sub pages for some of the content on that page, and I’m trying to add the same nav bar and anchor a nav menu item to a section on the main page but it doesn’t seem like its possible unless its on the same page. 

I'd like to suggest adding additional readiness statuses beyond "Ready for Dev". For example:Animation Ready UI/UX Ready Legal ReadyThis would allow teams and agents to understand which aspects of a design are complete and which still require attention, rather than relying on a single development readiness indicator.

Add native JSON / Lottie format export support for Figma animations and prototype interactions directly from the Export panel.Why is this needed?Currently, to export UI animations or micro-interactions as light-weight .json (Lottie) files for web and mobile apps, designers have to rely entirely on third-party plugins (like LottieFiles or Aninix).

Add a unified, searchable variables table directly in Dev Mode so developers can review all variables, modes, and collections in one place instead of only seeing variables tied to the selected layer. Dev Mode already supports variable details, suggested variables, and access to local variable collections, so expanding this into a full-file view would make multi-theme and multi-brand systems much easier to inspect.

I'm building a blog with Figma Sites CMS, and articles vary a lot in how many images they use, some have 1, others 5+, in different arrangements. Right now a CMS Page is one shared template for the whole collection, so every article renders with the same fixed layout. If an Image field is left empty, it just becomes a transparent fill, the layout doesn't collapse, so I end up with blank gaps instead of a clean design.Figma Sites already ships a big library of pre-built blocks with different image/text combinations (Insert > Blocks), which is exactly what a blog like mine needs. There's just no way for the CMS to pick a different block per item based on how much content that item actually has.Two things that would fix this for my use case:1. Conditional visibility tied to whether a CMS field is empty, so an unused image slot collapses cleanly instead of leaving dead space (similar to "Is Set" / "Is Not Set" conditions in Webflow or Framer).2. The ability to swap which component/block