Share Your Feedback

I finally figured out (I think) where my prototyping pain is coming from. I think maybe most users would use navigate to in order to navigate between dashboard pages, but I am using change to w/i instances of a large complex component set … with variables. I think my approach is more dynamic, but of course takes up more memory. And, navigate to has some limitations in terms of carrying a prototype across files.  Can Figma consider making variables x prototyping x navigation more robust/dynamic while not destroying memory?

TL;DR: Could Figma please extend the hitbox for the expand/collapse layer button (the chevron to the left of layer name) to the left edge of the screen?Hi. The hitbox of the button used to expand/collapse a layer in the Layers panel does not extend to the left edge of the screen. The hitbox is overall very narrow - not even 16px wide?This increases the precision needed to press the button - and requires precision in a situation where just generally throwing the cursor in that direction, for it to automatically stop at the screen edge, would require so much less attention.I don’t see any good reason to not extend the hitbox to the edge, since it’s already a dead zone where there’s no interaction. 

Hello, I’d like to share some critical feedback on the new UI3 asset panel, as it has significantly disrupted my workflow and, I believe, undermines some of the core organisational benefits Figma has always offered. 1. Loss of nested sectionsIn UI2, the Assets panel allowed nested subsections based on 'Frames' within a page on the design system (e.g. “Inputs” → “Main Component” and “Component Blocks”), so you could keep building-block elements separate from your primary component.   UI3 now flattens everything into a single folder, regardless of how many 'Frames' containing sub-components you have. For files with dozens of related components, this makes it very difficult to locate the exact asset you need without constant searching. This old method used to allow me to organise my components in an easy way. Allowing me to just select my design system > Select Inputs > Select Main component. While now I have to select my design system > Select Inputs > Search and find my main

Enhancing Component Flexibility with Slots: A Real-World Scenario"We often find ourselves needing to edit content within a component instance without detaching it. While a 'change once, update everywhere' approach for simple variant states is great, we really need more flexibility within those instances."Understanding the Power of SlotsThe Slot feature introduces a powerful new component property acting as a designated placeholder within a master component. This allows components to achieve both rigorous standardization and dynamic flexibility. Designers can now freely swap, add, or remove content and structural elements inside a component instance, all without ever having to detach it.When combined with Auto Layout and other Component Properties, Slots make components significantly easier to manage and far cheaper to maintain. This approach is particularly effective for use cases involving diverse content, frequent content updates, and high reusability, like those found in enterprise

Is anyone else running into a lot of memory issues since upgrading to UI3?  Seems the memory management is worse than it used to be.Getting memory limit errors on files that seems much too small to justify them. Had an issue where I could not merge a branch back into main due to running out of memory.  Even running the operation on a PC with 96 GB of ram (yes, ninety six) did not fix the problem (what? HOW?!) I just tried to disconnect a bunch of frames from their component masters (with a lot of nesting) and the operation failed.  First it asked if I wanted to reopen in recovery mode.  Then the interface just went away and left me with a blank window.I use a lot of nesting to make my mocks responsive, and I build everything from components so I can use properties to configure each one how I need.  My approach has always been hard on Figma and performance regularly ground to a halt, but this behavior feels new.  Is anyone else dealing with new and more frequent memory issues lately?

A productive feedback software fosters productive feedback culture! What I experienced in your Forum / Issue Tracker:✅ The forum guidelines recommend “Search before you post”. ❌ But the search function is currently very mediocre!Please make sure that one can least…Decide in which fields search shall match: Title, Body, Fulltext. (e.g. Github in:title) Highlight where the query matched in your the search results . To quickly grasp relevance. Filter by issue status: Open, Closed. You have that data per issue, make use of it! Screenshots of the current experience: 

I don’t think this used to be a problem, but since the new update it’s now full of bugs and I really miss the old UI. The bottom menu is a waste of space, just put it back in the top and let us use the short cuts! I have a habit of creating components outside a frame and I noticed that recently, it’s super hard to select objects grouped by auto-layout! I’m forced to put the whole thing in a frame just to do this or it will drag out individual element eventhough they’re all inside an auto-layout! Another thing about ‘Shift + I” shortcut for inserting components is that it will always prioritize inserting inside an auto-layered object closest to my cursor rather than where my mouse key is pointing, EVERY SINGLE TIME.

Hi, I have been searching to disable the “Spell Check”. While the Online Guide explains it clearly where to find it, intuitively I wouldn’t expect it there.To me, Spell Checking is either a user-setting or a preference of the application, not specific to the document or whatever I’m currently editing. I would suggest either moving or adding the “spell check” to the user-settings dialogue or the application-preferences.Option AOption B Let me know what you think Regards Lukas

Every good forum usually has a “meta” category where to submit shortcomings/proposals on the forum software itself.Due to lack of this I will post my Meta suggestion into the closest available category, which is:  Share Your Thoughts → Share Your Feedback.But I recommend you to create such a category, which is a best practise.

When I select an element in a component or component set to add a boolean property, Figma displays a modal window showing the list of available properties. But boolean properties with long names are truncated without any option to disclose the full name.Please Figma should provide a resize capability or tooltip option for the modal to make it more accessible.  

I was genuinely excited about this new feature, not just because it helps reduce the double dipping on seat pricing, but because it seemed like a much simpler way to collaborate with external teams and clients who have their own Figma accounts.Unfortunately, the current limitations around the very minimal number of connections make it feel fairly useless, especially for a small agency like ours that work with multiple different teams every day. I had hoped this would be similar to Slack’s connection feature.More importantly, the feature still feels underdeveloped. Our team typically sets up two folders per client: 1 internal for exploration and iteration, and 1 external for sharing polished work. We were hoping the connected projects feature could replace our external folder and streamline collaboration. But when we tested it by adding a completed website and design system to a connected project for the client’s team to use, we quickly ran into an issue. Our team couldn’t access the de

The changes made to the transparency in the seat approval settings are very welcome.Without the 'Manual approve seat if available' and 'What is included' options, I paid for unintended seats several times in the past. This makes controlling costs much easier. Thank you for listening to the feedback.  

Usability problem. Could we get rid of the 'Show more properties' button and show properties always open, please? It's very annoying to have to click it open every time. Or provide user preferences. 

Usability problem. Could the 'State' section be set to be open by default, please? It's vey annoying to have to click it open every time. Or provide user preferences.  

Our design system in Figma often involves iterative refinement, leading to the identification of redundant variables (colors, etc.). These unnecessary variables are often duplicates of existing ones, linked to the same foundational variable library. To improve the organization and maintainability of our design system, we require a more efficient way to remove these redundant variables.Currently, deleting a variable that is in use by multiple objects and elements within our designs is a cumbersome and potentially error-prone process. We propose a new feature: when a user attempts to delete a variable, Figma should present a prompt asking which existing variable they would like to substitute for the one being deleted.This functionality would allow designers to seamlessly replace the usage of the obsolete variable with a chosen, equivalent variable across all instances where it is currently applied. This would significantly streamline the process of cleaning up our variable library, ensur

The new auto layout design seems unintuitive now that gap and alignment placement has been switched (alignment left, gap right). We would be far more likely to ‘set and forget’ the alignment, but often do tinker with spacing and gaps in auto layout. Every time I intuitively reach to edit gap in auto layout, I have to scan and mouse over alignment, something that just doesn't need to be in the way. Gap and alignment should be swapped back to what it was (alignment right, gap left). Anyone else experiencing this friction?Otherwise, this auto layout update is a wonderful and welcome change!  

Colour panels for fill and stroke- I frequently change opacity and colour by hex codeMaking this one additional click is frustrating   

I’m not using it at all but it distracts and takes a lot of working space. Is is completely unnecessary placed there. Make it customiseable and optional

Hi,I am trying to use the new function “GRID” into AutoLayout setting.AS you can see from my image, the component “SIMBOLO” is made by 9 circles, I can easily set the padding between them, and it’s ok. But WHY does the height not fit to the contents?I cannot set HUG contents both. on Height nor Width.This cause a problem in using the istance for misalignment in over-nesting autolayout, as an example. Thank you for the attentionHave a good weekend!

rename optionthat is how your rename ai option still, one year later works… a completely pointless thing that needs to be constantly edited manually

See above screenshot . OLD  UI vs NEW UI3Now the component icon is almost invisible on left sidebar. And it has different icon from actual component, which is confusing

Figma started out as a tool primarily focused on prototyping, with a focus on accessibility and collaboration. Limiting the sharing of prototype links on the sStarter platform goes against this spirit.This alienates non-users from the platform, creating unnecessary barriers and, apparently, only with the aim of monetizing more.I think the company should maintain the possibility of sharing prototypes separately — even if it were limited to one at a time — so that designers and teams can continue to show their work to clients, stakeholders or colleagues without requiring everyone to have an account.Continuing with this limitation could end up shooting themselves in the foot. Many users should start considering more open alternatives, which could be detrimental to the image and growth of the platform in the future.What is your opinion on this?

It takes a long time for styles from a design system to update when used, literally around 5mins before the changes is reflected, for better content if I’m using a current text style and I change to a different text style, it takes close to 5mins before it is eventually changed.

Image parameter adjustmentI can't see the exact parameters that I'm using to increase the exposure or saturation of my images, and if I want to get the exact same exposure increase for another of my images, it's difficult. This makes consistency in long term design pose a difficulty.New UIChanging button icons or changing the position of buttons without improving the experience or adding functionality is not friendly to long-term users. PrototypesI have seen to your growth, and I have seen your efforts, and your intentions. But the limitations of prototype still persist, such as the complaints about all the “on scroll” interacts, also including the inability to trigger a change when the global value changes.

Let's address the elephant in the digital room: Figma's compulsive need to force-feed updates to its users like some overzealous IT administrator. This isn't software evolution - it's digital waterboarding. The complete disregard for user autonomy in their update policy would make even Windows Update blush.Without warning or consent, we're suddenly greeted with relocated features playing hide-and-seek, shortcut keys that now trigger random functions like digital slot machines, and UI elements rearranged with the logic of a toddler playing Tetris. That carefully cultivated muscle memory? Gone. That optimized workflow? Obliterated. All sacrificed at the altar of "progress" that feels suspiciously like change for change's sake.The most infuriating part? The complete lack of new bottom bar. While we're scrambling to meet deadlines, Figma smugly insists we pause our actual work to play archaeological dig through their new interface. Their update notes read like fortune cookie wisdom - "Impr