Share Your Thoughts

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

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.

Its beyond frustrating that to view annotations you have to have a Figma license. People like BA’s and PO’s just need to see annotations but do not need to edit or review the files merely look at the designs and see the annotations to get an idea of the functionality. Our organisation has many licenses as we have a large team of designers and developers all who have licenses. The annotations feature should be made viewable to people you share a file with without having to purchase a license. To get around this we have created an annotations component but the built in one is so much easier to use. Figma please make the new annotations feature viewable to all. I understand the licensing aspect for editing etc but to view an annotation makes no sense that you would need to purchase another license so someone can view a note.  

hi, im encountering condition where my file in figma make get warning of high memory usage, and it seems not because the amount of code that generated, i think it’s the cause is the chat is to heavy. any idea why this is happening?if the chat is the cause, i think add a chat deletion feature will be helpful, 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.

Hello, good day.I’m experiencing serious issues with the new Figma UI update. Many essential tools — such as padding controls — are missing or hidden.Please do not enforce this new version. The previous UI was much better, clearer, and far more efficient for designers.This new version has no advantages, feels confusing, and makes our workflow significantly harder.

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

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.

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.

This is a regression in Crop behavior.Previously, it was possible to adapt a 16:9 image to a fixed 1:1 (768×768) exportby symmetrically pulling the left and right crop edges toward the center.The content itself was not edited, only the visible area was adjusted.This workflow exported a correct 768×768 image without empty paddingand without cutting important text.Currently, Crop enforces strict aspect ratio behavior.When adapting 16:9 → 1:1:– using Fill crops important content– using Fit / Scale results in empty bands (letterboxing)This removes a previously available and widely used workflowfor preparing fixed-size marketing assets where content cannot be modified.This is not a design request but a regression.There is currently no way to reproduce the previous behaviorusing Crop, Mask, Frame + Clip content, or Image Fill.Please consider restoring the previous Crop behavioror providing

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 

Feature Request: Native Lottie (.json) File Support in Figma PrototypesSummary:Please consider adding native support for Lottie .json files within Figma prototypes, allowing designers to preview and interact with lightweight animations directly in the canvas and prototype mode.Why This Matters:Lottie animations are widely used across mobile and web platforms due to their small file size and rich visual capabilities. Currently, Figma only allows Lottie integration via plugins like LottieFiles, which limits functionality to static previews (GIF/SVG) or external exports. This creates friction in the design-to-development workflow and reduces fidelity in prototype presentations.Benefits of Native Support:Real-time playback of .json animations in prototypes. Improved design accuracy and stakeholder communication. Seamless handoff t

When aliasing a color variable to another (img 1), or using it directly on an element (img 2), we should be able to override the opacity without the need to create a variable for each transparency variation: Cant override opacity in the alias: Example 2 Cant override the fill opacity:

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