Suggest a Feature

Is it possible the prompt result from figma make design wise to be copied in the main design file i’m not seeing any button that allows me to do that 

When a Figma branch is updated from main, components modified on the branch can be replaced wholesale, even when the branch changes are additive or limited to layers or properties that do not overlap with changes from main. In a recent library-maintenance session using Claude and Figma skills, this caused branch-specific edits to be lost multiple times and required rerunning rebuild scripts after each update from main.Request: allow incoming updates from main to be reviewed and applied at a finer granularity than the entire component. Ideally, non-conflicting changes could be preserved automatically, while actual conflicts are surfaced at the property or layer level with a choice to keep the main version or branch version. Even a simpler option to preserve branch changes where they do not conflict would be a meaningful improvement.Use case: I maintain a Figma library that mirrors a shipped React design system. My branch often contains targeted changes, such as rebinding a token, renami

The Plugin API currently cannot enumerate styles or variables available from libraries linked to the current file. Methods like getLocalTextStylesAsync() and the variable equivalents only return local items, so using linked-library assets requires the plugin to already know the asset keys in advance.This creates a discovery gap for plugins that work with library content dynamically, especially AI-driven workflows that maintain design systems from code. A linked library may already be available in the file, but the plugin cannot inspect its contents unless the keys were prepared ahead of time or the assets are already applied somewhere in the document.Request: add async Plugin API methods to enumerate styles and variables reachable from libraries linked to the current file, without requiring pre-known keys.Use case: I maintain a Figma library that mirrors a shipped React design system and use AI-agent scripts to apply updates as code components change. With linked-library enumeration, t

I’ve been using Buzz to create full page templates, which has great potential. However, in the Edit Content panel, all editable fields for the entire page are displayed at once, which makes it difficult to navigate and manage.My suggestion is to improve this panel by making it context-aware. For example, when a specific section or component is selected on the page, the panel could display only the fields related to that element. This would make editing full pages much easier and more efficient.To give some context, in one of my projects, Buzz shows around 160 text fields along with dozens of media items. That’s a lot of information to manage in a single panel. A filtering mechanism based on the selected element would significantly improve usability.

Please make it possible to control which properties of nested components (atoms) can be used in higher components (molecules). What if I use same nested component in different objects and I don’t need some properties in both of them? What if I don’t need some booleans which is part of variants of that atom in molecule? Please fix it, thank you.

I would love if Figma integrated a smarter paragraph composer for Thai. Currently, our linguists have to manually update line breaks for Thai during QA, but I feel that most of this could be avoided if there was a dictionary-based approach to when lines break in Thai. I’m aware that non-breaking spaces could be used by the Thai linguist, but I’d love if this was more automated.

On this page https://www.figma.com/community/education, I would like to have a search bar below the description for Education or on the same level as filters. There is a search bar in the top right corner of this page, but it doesn’t filter the content on my current page. Education filter search bar ideas 

Hey hey! Sometimes me and my team works on branches. This is fine if you know where you are looking in specific team / project however that’s not the case when searching. The file “card” doesn’t show if the file has branches in the search results. I guess my ask would be to add same interface I can see within a project when I hover over a file to search results file as well. Many love! <3

Middle-clicking a file in the file list should open it in a new tab. This is expected browser behavior on Linux (edit: also on Mac).Current Figma implementation is blocking it.

I'm really enjoying the Actions menu! It would be awesome to have the option to access the Assets tab directly as well, just like we can currently access the Assets left panel with a keyboard shortcut. This way, we could set a custom shortcut to open the Assets tab directly from the Actions floating menu.  ​@Figma_Desktop🙏

I prefer to use Figma when the left panel is hidden. When I have to search for components, I either need to reveal the left panel or use the actions panel, which doesn’t allow me to quickly search components, as I have to use both the mouse and keyboard for every single component. Please allow using tab in the command menu.  

I absolutely love Figma Slides!! It’s so cool that slides automatically get grouped into bundles. However, I feel like if there was a way to label these groups, I can organize my rather large (100+ slides) presentation better. Thanks a lot for the amazing work, team! <3

Hi,“Hide prompts when sharing a Make prototype” seems extremely straightforward, but is not yet possible, thus this feature request.I love working with Figma Make and want to integrate it into the prototyping workflow. Unfortunately, sharing Make prototypes turned out to be a real headache. But without being able to share a prototype externally (and temporarily), the whole Make prototyping workflow doesn’t make sense, since copying the prototype pages into design doesn’t copy any interactions or animations. The goal: Share the Make full-screen preview with external viewers, without showing the AI chat history # Problem 1: Prototype viewable for logged-in users onlySharing did not work for not logged-in users, for whatever reason. Figma support couldn’t help either, thus it might be a bug.Workaround: Create a free account for the viewer, then share the full-screen previewTo shorten and speed up the whole thing, I decided to create an account for my client, and then share the preview wit

Dear Figma team,Please consider adding support for pixelated, stepped, or chamfered corner styles for Auto Layout objects.If native support is not currently possible, it would be very helpful to expose additional corner geometry controls for FrameNode in the Plugin API so the community can build custom solutions.This would significantly expand layout styling possibilities while preserving the flexibility of Auto Layout.Thank you! 🖖🏻

It would be useful to be able to add a trigger to a frame that once it ‘loads’ some kind of interaction would kick-off. This would mean that not every prototyped action needs to be on click or on some clear action on the user’s part and would also allow for variables to be used to check what states components should be in so that we can have conditional logic per page.

When publishing resources (Figma Slides templaces or custom plugins and widgets) you can´t publish for a Workspace only. You can publish to entire organization or current team only.

Enough time has passedI think that Figma should Implement Latex support (Math Equation) natively instead of doing it by plugin which makes the equations in to vector format and its very hard to use with text whenever we use it with text and all…. Its also a suggestion to add at-least a font which support Latex if the above request is hard to implement.

Hi again Figma Team! So Would like us to have the option to assign different colors for each Mode without the need to create a Variable. In code we can assign different colors for items based on the Mode without defining it in our CSS sheet. example we would write this inline CSS as "background-color: light-dark(#ffffff, #000000);”I did a quick mockup of how this would look like but appearance doesn’t matter as long as we have the option to do this. It would reduce a lot of clutter when creating tokens and would give us a good  flexibility to color stuff that are a 1 timer case  

Hey Figma Team! I would like us to adopt the option of having Opacity Properties panel for colors. We can do this in code so I don’t see a reason that our design tool can’t do this simple thing. In CSS we can do “var(--foreground), transparent 50%)” and same thing in Tailwind which is much simpler “fill-foreground/50”. We can also achieve this in Mobile too with different scripts. Right now my work around for this is that I need to create a new Variable for this specific opacity and it creates too many unnecessary tokens that we can avoid.   

Like the title says. It would be awesome if you could just use a picture you took from a sketch or a whiteboard of a diagram, and FigJam could convert it to a digital diagram.

Hi, as I’m always on the lookout to work more efficiently, I’ve been surfing the web looking for a specific answer to my question which I haven’t found so I’m guessing I already know the answer, but here goes. I need to make an editable form in PDF which my client can open and fill in, in PDF. I can make up the form in PDF, either from scratch or from an existing PDF (exported from Figma), but the latter doesn’t work because even if I add form fields to my Figma file, Acrobat doesn’t recognize them. I found a plugin called Pitchdeck Presentation Studio which is great but it doesn’t say anything about fillable forms. I’ve tried the plugin CopyDoc Textkit which is also amazing but nothing on fillable forms. The only option I see now is to make the file in Figma without formfields, export it to PDF and add the formfields in Acrobat afterwards. Does anyone know a more effective workaround? Thx

Hi Figma Team,While working on my project, I noticed that when a file uses components from an external library, Figma mentions “Some components from this library are used in this file” under the Manage Libraries panel.However, there’s currently no way to easily see which specific components from that library are being used or where they are located in the file.It would be extremely helpful if Figma provided a way to track or highlight the components used from each library, for example through a “Locate components” button. This would make it much easier to manage dependencies, replace assets, or clean up unused libraries.Could you please let me know if there’s currently any way to check this, or if it’s planned for future updates?Thank you!

The presentation mode is set so that moving the mouse pointer to the top edge of the screen triggers the display of the figma-options. This is extremely disruptive especially when you want to present the menu of your own prototype which usually is on the very top of the homepage. Is there any way to change this function?

hey, sometimes i just want to check how people with a viewer role would see the file and dont want to bother logging in with a “viewer” account. then it would be just nice to be able to switch the UI to what they would see. e.g. sometimes i wonder what they can and cant copy or what they see in the side panel AND NO i dont want to go to the Figma documentation and look for that screenshot 😃 just let me switch view > check > done > happy 😃

Variants have become one of the most important features I use within Figma. They are incredibly powerful! As they are so useful, I find myself looking for the ability to have properties show ONLY when another property is a certain value. A quick example of what I mean is like this: Let’s assume you have a button, and the top level of the properties are set up to be Primary and Secondary: Let’s now assume I have an icon added to my buttons, but they are ONLY available to my Secondary button: It would be so helpful here if this was possible: Select “Secondary” as my Property on the button variant. When “Secondary” is the active Property, I can then see ANOTHER Property where I can choose the icon for this example. That icon Property is only visible because I have said that it belongs to the “Secondary” Property. Apologies if I have not explained this very well, but I think this could really be helpful when working with Variants.