Share Your Thoughts

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

Figma's left sidebar currently gives most of its vertical space to the Pages section, leaving very little room for Layers.Since designers interact with Layers much more frequently, this makes the default layout inconvenient. Users have to manually drag the divider upwards every time they open Figma. 

I’m having trouble finding Figma design files in new version. Some files are in my drafts rather than in the plan or team workspace, and I can’t find the updated versions now.Would it be possible to go back to the previous version, or do you have any suggestions? Alternatively, should we allow files to be used only within the plan/team workspace?

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

This update is genuinely one of the most frustrating UX changes I’ve experienced in a professional design tool 😡 😡 😡The new left-hand navigation panel permanently steals ~60px of horizontal space on small screens, which is completely unacceptable. That space is my primary working area — the canvas. I am literally losing room to do my job so a panel can sit there doing nothing most of the time.Yes, Variables, Files, Assets, Find, and Library are important.No — they are NOT minute-to-minute actions.They do not deserve permanent, always-visible real estate. This panel is idle 90% of the time, yet it constantly punishes my workflow.On smaller displays, this feels especially hostile. Instead of prioritising the canvas (the entire reason Figma exists), the UI forces a bulky navigation column that adds zero value moment-to-moment and actively makes precision design harder.This change feels like it was designed for: Large monitors only Product demos Feature discoverability …not for actu

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.

So…. working today w/ the agent and now that button is gone.  it is in the other boards but not in one of my librarys.  i have shut down i have reinstalled, i have done the thigns…. but it still is missing = what is going on? 

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 🤞

For reference, I’m an experienced user of video editing softwares such as Adobe Premiere Pro and Davinci Resolve, and also a beginner user of motion graphics editing software such as Adobe After Effects.Some of these suggestions are from my first impression of trying to use the mode a while back:The timeline zoom is currently too vague. It was difficult for me to find, as it was located in the bottom right, and it has a limited capability of zoom (fixed). A good suggestion is the Davinci Resolve Version where you can adjust the zoom of the timeline. In this case you can choose to oversee the whole timeline or zoom in on specific places. Another use case is that currently the Figma zoom out maxes out at the whole timeline. This would mean the timeline would be very stretched just to fit for 5 seconds. It would nice if we can zoom out larger than just the duration of the animation (again, to goal is to oversee the whole timeline). Davinci Resolve’s zoom slider  The add animation is too

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.

To my mind, a design should be checked before it is tagged as ready for dev.If I mark a design as ready, then check the design and find out something needs to change, I’d need to re-mark it as ready for dev. This flow feels redundant as it sends unnecessary pings out and / or creates duplicate work for the devs and designer.I suggest removing this popup entirely as it is redundant at this point in the flow.Why now? 

 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?

I'm paying for a Professional seat, and somehow I burn through my monthly AI credits after generating just a few screens.For roughly the same price, I can get way more done with Codex. Figma really needs to rethink these limits.

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