Suggest a Feature

When publishing a template in Figma Slides, I would like to see the animate/transition properties included. Currently, every slide defaults to no animation when starting from a template.

Please, bring your chrome extension to Firefox. Long story short: because Arc browser is sunsetting, I moved to Zen browser. And I thought it was a cross-browser extension, but to my surprise, it wasn't listed in the add-ons. I think many users would be happy to have it on Firefox

why can’t figma make make components that we can import back into figma. It would be useful to us make to generate a design system, using prompting and be able to import thes eback into figma as components.

The problem When I click or paste a Figma link in my browser, it opens the file in the Figma desktop app, which is what I want. But the browser tab stays open showing only "Opened the URL in Figma app." I open dozens of Figma links a day from Teams, email, ADO and docs, so I end up with a pile of empty tabs. I have to close each one by hand, and it makes it harder to find the tabs I actually need.What I'd expect After the hand-off to the desktop app works, the leftover tab should go away on its own.Possible solutionsClose the tab automatically. The page could call window.close() after the app opens. This works when the link opened a new tab. If the tab can't be closed (for example, the link was pasted into an existing tab), go back to the previous page instead of leaving an empty one. Add a setting under Preferences → "Open links in desktop app," such as "Close browser tab after opening in app," for people who want the tab gone right away. Keep a fallback. If the desktop app doesn't re

It has come to my attention that people in this community have been asking for long over SIX years, yet no response despite Figma having new features rolling out ever so often. This particular feature has been brought up over the years and there is still no improvement, update, or even a response from the team. It has been long enough. Please consider adding this feature. It will really help thousands of designers out there who use this service. It has been very tough to work around this flaw, where the guides keep moving despite my cursor clearly hovering over my work. It’s a hassle. I hope one of the developers see this and decide to actually make the change and help us designers. Thank you.  I beg you listen to the users. There have been numerous feedback from the users all over the world asking for this specific feature yet no answer. 

I’ve already started using the new slots and I find them amazing, but I think it’s very limiting to prevent the use of grid layout. 

An option to change the “Move” cursor to a red laser pointer, that leaves a trace behind, would be great when explaining things in Figma. One could also use this in present mode. What do you think? 

I would like to apply a mode on designs across all variable collections. I separated colors, radius and spacings in different collections when creating the design library. Now I can only apply a mode for colors OR radius OR spacings – but not all together.One alternative option would be to move variables between collections, while keeping the linking to components and designs. So I could merge colors, spacings and radius to one collection. A consistent structure for collections was already requested 3 years ago: 

When adding components to a Slot and attempting to surface nested properties I see a message that nested properties can not be surfaced with Slots. This severly limits their usefulness to us since we are creating multiple composable components using sub components with properties and having to drill in to each instance in a multi-item Slot is very time-consuming.

I noticed an unnecessary empty space in the top navigation bar of Figma's home screen, as highlighted in the attached screenshot.The navigation items (Design, FigJam, Slides, Make, Spec, and More) appear too spread out, leaving a large unused gap in the navigation area.My Suggestion:Figma should optimize the spacing between navigation items and align them more closely to create a cleaner, more compact, and visually balanced navigation bar.Reducing this unnecessary whitespace would improve the overall layout, make navigation feel more organized, and provide a better user experience, especially on desktop screens.It's a small UI improvement, but it could make the interface feel much more polished.

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. 

This is a feature in dire need of attention. Figma needs to fix it’s bullet implementation. A user should be able to customize bullets per level. This very board does it better than a professional design tool that should be able to handle lists! Not every site is cute. Not every site is fun. Regulations means tiered bullet lists and I’m tired of hacks to make it work. This is what a tiered bullet list should look like:Level one Level two Level three Level four A user should be able to set the character for each bullet on any and all bullet levels. I love that I can paste code and tell an agent to do stuff for me. What I’m not stoked about is that I’m writing this almost a dozen years after launch.

This makes it easier to use components in designs for different screen sizes. And then you don’t have to calculate every time what 40% or 60% of the width is. This also makes it easier to design scalable applications that grow with the width of the screen.

I’ve created a Figma plugin to get the state of local variables then trigger external API’s based on that state change. I’m trying to have a prototype instance of the file communicate with the Figma Plugin I created so when I click a UI element in the prototype, a variable changes which triggers an external API. Right now, there’s no way I can find to ‘listen’ for the variable state change in a prototype because it does not ‘write’ to the original variable value.

I have searched and can’t find an answer. I am a bit surprised this isn’t already a feature. I would like to hide the selected object’s BLUE OUTLINE with a key command or in the View menu. Please and thank you.

Would it be possible to create a collection of modes with groups and sub-groups or create linked collections feature? In my case, there could be a light and dark mode using accessibility mode and the company’s branding could be distinguished from the client’s branding variables using sub-collections.Collection├── Company│   ├── Accessible mode│   │   ├── Light│   │   └── Dark│   └── Standard│       ├── Light│       └── Dark└── Client    ├── Accessible mode    │   ├── Light    │   └── Dark    └── Standard        ├── Light        └── Dark

Request: Through the Figma MCP, access contents of comments made in Figma Design file.Reason: Can provide context for designs, review bugs, etc.Current response from OpenAI Codex with direct link to comment:No, not the comment itself.What I can see from that link is the node it points to:file: XXXXXXnode: XXXXXXscreen: /sign-up-2 (iOS)That screen contains:nav title Sign UpEmail and Password inputsSign Up primary CTAContinue with AppleContinue with Googledivider OrAlready have an account? Sign inbottom legal linksBut I still cannot read the actual Figma comment thread or the #XXXXXX anchor content from this session.If you want, paste the comment text here and I can map it to this exact screen and tell you what change it implies. 

Layer names can get really messy when layer renaming is enabled, and the number never seems to be very useful for me. (ex I don’t remember what “Frame 324” is, I usually just reference a named parent/child for context). To me, it’s just additional noise in my layer list. Thankfully, Figma offers an option to disable this, “Rename Duplicate Layers”. This solves my issue when duplicating, so I don’t end up with “List Cell 2, List Cell 3, etc”. But… New frames & groups still get a number added by default. This can sometimes result in seemly very random numbers appended to a new group or frame, depending on how it’s added, or what already exists in a Project. For example, drawing multiple Frames will cause them to increment, but if you group an item and apply auto-layout, it starts again at 1. See this example. The behaviour I’d rather have Don’t append any number to layers when this option is disabled (New frames would simply be “Frame”, and you could create multiple elemen

Hey! Add more metrics to the Figma community / individual contributions - Its currently hard to track the AARRR funnel. Thanks in advance!

There are so many figma users in China, but there is still no Chinese support in 2025, while Korea and Japan nearby have it.

In tomorrow’s world: Privacy 📈; Subscriptions 📉; Trust in the persistence of the ‘new-analog’ even as companies crumble 📈; Optional version/yearly upgrades 👍🏾; Optional subscriptions for connected/online features 👍🏾; Locally hosted, LAN features 👍🏾 I personally miss software as a destination; not software as an automation. I can sit in Figma and think, not sit and be hounded for the next prompt. I would like to own that and save that feeling.

BackgroundPeople have been begging for local component instance-scoped variables since variables were introduced in 2023. This comes from variables as they are today existing exclusively at the document level, making advanced behavior possible to do once with the global state, but you painfully discover its impossible to package and re-use anything you make that relies on it. All instances have to share the single global state, which directly shatters the fundamental idea that Figma is about making re-usable components that speed up your workflow and maintain SSOT.Requests differ in their implementation, but the common request is to somehow allow components to define values with at least the same power as the existing variables, only local to each instance of the component. People want to be able to make the same advanced behaviors we already can with global variables, just packaged into a component you can actually instantiate multiple times without side effects.I’m writing this featu

SummaryAdd support for "global" or "parent" mode dimensions that apply across multiple variable collections. This would allow a theme like light/dark to act as a global setting that affects all other collections (like Surface, Density, or Brand) without needing to manually create every combination. The ProblemCurrently, Figma treats each collection's modes as independent and flat. When building a design system that needs both a theme (light/dark) and a surface context (default/prominent/muted), there's no way to express that light/dark should be a global setting that applies across all surface contexts. Current WorkaroundWe're forced to combine both dimensions into a single collection with combined mode names:Collection: SurfaceModes: - default/light - default/dark - prominent/light - prominent/dark - muted/light - muted/darkThis leads to:Combinatorial explosion: Adding one surface means adding two modes. Adding one theme means duplicating all surfaces. Maintenance burden: A syst

Krea 3 Edit on fal supports regional editing (a regions list of labelled bounding boxes, plus regional_edit to keep pixels outside them unchanged), but Weave doesn’t expose either, on the built-in Krea 3 node or on an imported krea/v3/edit.The parameters work through Weave’s run pipeline when they’re included, so it looks like a UI gap rather than a backend one. It would be great to have a box editor on the Krea 3 node, and more generally for imported models to show array and object parameters, or offer a raw JSON field, so we get every control the model has.We use Weave on a team plan for architectural visualisation, and this would make precise local edits to renders much more practical.