Suggest a Feature

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.

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\

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.

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?

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. 👍

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.

This isn’t necessarily a bug, but definitely unexpected behavior. So I have a simple button component, which changes to a hover state component while hovering - cool. Works perfectly. The problem arrises when I want to use that button in my prototypes. If I add an on-click interaction to navigate to a different frame, for example, the click interaction doesn’t work. As soon as my mouse hovers over the component, it technically changes to the hover state one, which doesn’t have the click component on it. The on-click interaction would need to be added to the hover state component, which I can’t do because that isn’t being used in the actual design (it’s only accessed via the change-to while-hovering interaction). Expected behavior: either (A) all interactions that I add to my component should remain, even after it “changes” to a different component, or (B) visually change a component to a different one, but don’t actually change it, so I can sti

I’m looking for a replacement for Fireworks/Photoshop. This is the decider. Thank you to anyone who can help me with this.

Hello Figma-TeamFirst of all, thank you for building String — it’s a great tool for managing design tokens and keeping typography consistent across projects.I’d like to share a feature request related to typography tokens, specifically font styles / weights.The problemWhen creating a font token in String, I can currently define the font family, but the font style (Regular, Bold, Italic, Light, etc.) needs to be handled separately in Figma.In some projects, we only use specific styles of a font — for example Italic only, or Bold only. Because of that, I’d love to define the font style directly within the same String token, instead of creating and maintaining separate tokens or manual overrides in Figma.Why this mattersThis becomes especially important when a font changes during a project.Example: Font A uses 

In Preferences there’s the option to turn off text suggestions, but that’s not it.“Your image looks a little blurry”, “Find more like this” — thanks for trying to be helpful, but it appears right on top of the toolbar and is highly distracting. Info pills there should appear to show results of my actions, otherwise it’s disruptive to the flow.Moreover, “your image looks a little blurry” isn’t even working correctly. I tried to understand the logic, but it seemingly appears randomly and not even once it appeared when I was actually working with an image layer.As for “Find more like this” — no idea what it does and why it appears when I’m pasting an image into another image layer to replace the fill.

I posted this wish in comments back in 2022 and 2023. Am I the only one that wants a nice elegant curved arrow option for the connectors? 🙂 It makes diagrams look so much friendlier and aesthetically pleasing, instead of orthogonal curves, straight lines or angled straight lines. Thanks all! Ben

Ai suggestions are turned off in the menubut I’m still getting this every time I copy and paste a text frame 

In Figma, I can create a color variable like Primary/500,but there's no way to create another variable that links to Primary/500 with just a different opacity (e.g., 50%).This becomes a problem when I change the base color — I have to manually update every opacity variation, which is time-consuming and breaks the idea of dynamic design systems.🔧 Feature Request:Allow opacity to be applied on top of existing variables when creating new ones.

Optimize existing functionality to allow direct conversion of existing components into Figma-compliant component-based design source files via screenshots. The current application implements basic functionality, but the output has two main problems: 1) the generated SVG format files do not retain component structure; 2) the official Figma API does not seem to support direct component creation. Please improve the solution to achieve true component-based output while maintaining the existing category layer functionality. 

 I need to do regular bookkeeping throughout the year. Yes, I am in the EU which cares about and requires reciepts for bookkeping.Modern bookeeping platforms in the EU needs reciepts as email attachments to be automatically filed in the customers bookkeeping.Stripe doesn’t seem to support that by default at least for various reasons. This is a struggle as a customer.But I know that the American company livekit.io is an example of SaaS that attaches the reciept as PDF on sendout. Could you at least have it as an opt-in option in the Billing settings please?Thank you,  

When publishing a library, I would like an option to shows all nested elements at the top level. OR even better, when in a Figma file when working in the ‘Assets’ tab, I’d like an option in the grid view (in addition to the grid / list) which allows all elements to be displayed on the top level and not display them as nested items.I realize when publishing I can put all elements on the same page in a file and then I will have no nested items for the users in authoring when trying to pull in components. However, this makes the page too massive to work with. I have to break up the pages but when published, this make nested items which I don’t want. I want everything displayed on the top level as its SO MUCH faster for designers to easily pull in components/elements when they don’t constantly have to go back and forth between levels to find the components they need.

Just discovered the “Templates and tools” tab and was excited to see if my team could migrate our design file templates to actual Templates. However to my disappointment, Figma seems to only offer this feature for Figjam and Figma Slides.My team uses design file templates to keep our work organized in a consistent way within each file. Right now our process requires having a “Template file” and manually duplicating it whenever we want to set up a new file for a new project. It would be nice if these could be built in Templates that we could access upon creating a new file instead of needing to navigate to the template file and duplicate it. 

Hi, How do we create a team via REST API?  Thanks! 

The plugin api provides the variables in any collection in the correct order, and this order is updated if user reordered variables. But for collections, the api doesn’t provide them in the correct order :→ if a user created Collection1 then created Collection2, then reordered them so that Collection2 is before Collection1, the plugin still gets them by creation order → Collection1 then Collection2. Can this bug be fixed quickly? It would be a great improvements of the api.    

Using string variables as a “CMS” across multiple teams is great to achieve consistency in ux writing/labels etc. If only it was possible to use markup within the variables. Because sometimes i run into a textbox where I want to format part of the string as bold, italic, underline … the usual suspects. With the way string variables are currently set up I can not cover this case with them. Hence, it wold be great if some kind of markup support was added. Marry Christmas ;]

Maybe on confused on how the feature works. If the team is using for ideation and keeping the master branch clean for devs and clients. When it comes time to push elements from a branch to the master file, currently it pushes the entire branch. This is pointless. We don’t want all the ideation, all the options, all the throw away work, just the version that we moved forward with. Currently we need to make a new branch we call “to be merged” and we need to copy just the artboards that are approved into the new branch then merge from there. This feels like to many steps and is complicated on a team of 4 designers. Shouldn’t there be an option to select just the artboards, components, styles, etc that we want to bring forward and leave all the other work in the archived branch incase we need to go back and grab something from it in the future? Pushing everything makes the feature feel useless because you’re either deleting all your ideation or creating “merge” branches to ma

If a layer has been locked in a Slides file - either by a user on a Full seat, or by the Collab user copying elements or frames across from a Design file, the user on the Collab seat will be unable to edit, unlock or remove the element.Suggest to either allow Collab seat users to also see the layer panel in a Slides file -- OR add an additional “Unlock all layers” when right-clicking a slide.

The Problem: Lost in the Canvas WildernessWhen working on large, sprawling Figma files (especially design systems, deep user flows, or complex prototypes) with hundreds of frames, the canvas becomes a massive workspace.We frequently need to pan or zoom away from our current focus—the frame we are actively designing—to: Reference a component in the design library on the far left. Check colors/styles on the style guide at the bottom. Look at a distant flow branch for context. The pain point: After checking that reference, returning to the active working frame requires slow, tedious, and imprecise manual scrolling/panning, which is a significant flow breaker. This effort grows exponentially with the size of the file.The Proposed Solution: "Go to Working Frame" ShortcutWe need a dedicated keyboard shortcut to instantly snap the viewport b