Suggest a Feature

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

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.

Hi, I’m not sure if this is new since the May update, but I wonder why “empty” (all elements hidden) Auto Layout Frames keep the size of the last hidden child (and I do not mean last in the list, but the last element to have been toggled out of view by the user), making them not-0px high even with nothing in them. See here a file with a Frame with three hidden rectangle: the Frame keeps the size of the last child rectangle to have been hidden. When adding a 0-px Frame to the AL frame, and toggling this 0-px Frame off last, the container goes 0-px. In my opinion, empty AL Frames should have a height of 0. What do you think?

I’m building a figma plugin where I’m giving the user a button to record their audio. I’m using the Web Audio API with the following code snippet: **var** audioContext = **new** **AudioContext**(); navigator.mediaDevices.**getUserMedia**({ audio: true }) .**then**(**function**(stream) { **var** source = audioContext.**createMediaStreamSource**(stream); }) .**catch**(**function**(err) { console.**log**('Error: ' + err); }); ’m able to console.log(navigator), but there’s no mediaDevices field showing up. I think the issue is that the plugin window is an iframe and in order to get mic access from an iframe, I have to add an attribute to the iframe tag (javascript - Cam access for embedded iframe - Stack Overflow 1). However, I don’t see how I can get access to the tag. Would anyone be able to answer this? Thanks!

Its hard for me to remember names or plugins sometimes. I have a local plugin that i built which has the plugin links to my favorite plugins(Since Figma doesnt give an option to see the favorite plugins on Canvas). Its like a plugins shelf.I want to be able to open my favorite plugins from within this plugin. I dont mind if my local plugin closes and opens the plugin I want. Currently Figma doesnt allow to call for other plugins from within a plugin and also two plugins can’t be open at a time. I hope this changes soon 🤞

I have a suggestion that I think could be really useful: allowing country flag icons to be added to Figma page names.Sometimes, designs vary by country, so we may need separate pages for each market, while in other cases a single page may cover multiple countries. Having country flags available as page icons would make it much easier to identify and organize these variations at a glance.For example, this is currently the best workaround I’ve found to represent the US and Canada.  It would be great if you could consider adding this option in the future. I believe it would be especially useful for teams working across multiple markets.Thanks a lot for the attention.

Everything is in the title, it would be amazing so when only one screens is ten foot long, your section can be small for all other screens.

 I like outline view because it gives a really good overview of the structure and is helpful when debugging alignment issues. Where there’s raw (editable) text it becomes very busy – I don’t think this text needs to be outlined, I can’t edit the paths and it creates a lot of visual noise. Totally makes sense to have the paths visible if text has been converted to paths however.

We work in a large company with over 100k employees and have very strict rules on how to share content with clients. What we are missing are advanced sharing options for “only-view”. Sometimes, we want to share content as a ‘view-only link’ with the client to receive comments and feedback directly on the artboards. Other times, we want to share as a ‘view-only link’ but without the possibility for viewers to leave comments. This crucial option is currently unavailable for us, and it would be great if this feature could be added to the sharing options. Thanks! 👍

Hi, I came across a similar idea - Search results are not precise - we get 'similar words' instead of exact match but unfortunately in Figma still missing. I think the exact search by name is a “must have”. Furthermore, it would be very useful if it were possible to find instances of a specific component, according to the specified properties. I think both functions are quite essential for keeping documents in order. Do you plan to add them please?

Please add auto nested code block indentation to Specs in Figma, please, instead of having to indent manually. Manual indent for new lines for nested CSS/code blocks 

Been playing around with the “expose nested properties” feature currently in beta. One of the great uses of variant properties is the ability to batch edit property values on multiple selected components. That use doesn’t carry over to exposed nested properties (yet I hope). Demo file to help When selecting one component instance exposing nested properties, said properties display fine. Add another instance of the same component to your selection (using Shift+Click), and the nested properties outright disappear from the right panel. I haven’t seen this issue raised elsewhere! Do you experience it too?

Today I tried to search a file in Figma and discovered that the search-by-team filter has been removed. We are part of a large organization and do all our work within one team folder; without the ability to narrow down my search to our specific team, we’ve essentially lost search. If there’s no room in the universal-search filters anymore, maybe offer a separate search function at the team level? Please bring our search back! I don’t want to have to go back to scanning files manually within folders for 2+ years worth of work.

I find the new Grid feature in Auto Layout really convenient for building tables. It’s easier and more flexible than it used to be, when you had to set up separate Auto Layouts for rows or columns, making it much more cumbersome to change the content later on.However, it seems that this approach makes it impossible to implement a hover effect across an entire row.The old approach is still an option, of course, but I design applications with many different types of tables, and I’d love to implement this behaviour system-wide, without having to create new components for every table.I realise this behaviour wouldn’t make sense for every type of Grid, but it could be an optional setting for each individual Grid, such as “Extend hover to entire  [ rows / columns ]”.I think this would require naming conventions for component variants, since there’s no way to know what the cells contain.What do you think?Thanks,g

Has anyone found a way to have a color variable for bulk create in Figma Buzz? For example, I have an ad. I want to make 5 variations with different background images. I also want each ad to have a different font and button color. Do we think there will be an update down the road to make these edits in the google sheet for bulk create or will it need to be done manually after creation? Am I missing something? Thanks!

This has been mentioned here: Hide layer using variables - #5 by Andreas_Braendhaugen1 Invert boolean variable for layer display - #14 by Desislava_Slavkova Inverted Boolean Property - #2 by drewcovi_usb but those topics are all closed. I am looking for the availability to HIDE a layer when a Boolean variable is TRUE and SHOW it when it is FALSE. So, the inverse of the default/current behavior. I want to do this without using components. Use case: When a variable is true, show one frame. When that same variable is false, show a different frame. I can get basically this by using two different variables: but it would be more convenient to be able to do it with just one. Just give me a Boolean toggle when the variable is used to say if the variable should be inverted or not.

Figma motion does not currently have the ability to play and export video fills, so video objects are treated as static images. The ability to incorporate video objects into the timeline would be extremely helpful. Exposing the current frame of a video as a keyframeable property be a great solve.