Suggest a Feature

I assume figma AI is only for paid plans especially because it is a costly thing to maintain and run, as it requires datacenters and a whole team behind itHowever some people have a PC that could run with no problem an AI model. Same for figma filesMaybe Figma should make available to it's users to run AI models locally and store files locallyThis would maybe help figma reduce costs tooIdk I may be wrong

I’m pretty sure I won’t be the only one… but I tend to open the same figma in different windows without noticing that I have 2 or 3 instances of the same file opened. I really liked how chrome solved it with the dropdown on the top right to navigate between recent and opened tabs. It would be very helpful.Thank you!

when i duplicate style in the style panel, it does not rename it automatically. It is a big issue as the user is unsure which one is the original and which one is the duplicate and then continues to update the the properties of the style he assumes is duplicate. Now he could be updating the original style which is applied to the designs and might mess up the design. There should be some way to differentiate the duplicated style immidiately when it is duplicated...i think it is the same with variables. 

As a user that uses Grid for designing tables (header, rows). I would like the option to add new rows or columns and change the order of the rows/columns. when adding a new column/row to an existing populated table does not mean I want the row/column to be at the end of the grid. The current design options (drag and drop) make it very hard and frustrating to introduce edits to existing populated table designs.Design idea: add drag icon to enable rows/column drag (change order) in addition to the number order of the rows/columns

I was wondering if you can set the horizontal or vertical wrapper in Auto Layout to inverse. I think that option should exist—it’d be genuinely useful in code.

Hey Figma Team,As a designer who relies heavily on Figma Make for my design-to-production process, I wanted to share some insights and suggestions that could really enhance the overall experience. Below are a few key pain points I’ve encountered, along with a suggestion that I believe would greatly streamline the workflow.1. Challenge: Large Frames Automatically Converting to ImagesWhen uploading larger frames from Figma into Figma Make, I’ve noticed that sometimes they automatically get converted to static images. This compromises the flexibility of working with vector-based designs and impacts the quality and adaptability of the final product. It would be fantastic if there were a way to either prevent this conversion or handle large frames more intelligently, allowing them to retain their original quality and interactivity.2. Challenge: Manual Batch Uploading for Multiple FramesCurrently, I’m limited to uploadin

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.

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.

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.

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.