Share Your Feedback

Please check the video.https://share.cleanshot.com/F4WbvN1jEvery time I use “rewrite” I have to press “open actions” shortcut 3 times to make it actually open again. Looks like a bug in UX but probably just the code.On a broader term, why push ai features and make them this interruptive?

Is there a way to export some frames as one pdf? When I click export > PDF, it exports all frames as individual PDFs which is not what I want.  I have lots of frames in this file. Say 1000s. I need to export 17 as a PDF. 

The function GRID doesn’t work as function WRAP.It is absurd that if do I delete an element into the autolayout, in grid it remains a empty space.In Wrap Mode it didn’t happen, elements naturally stacked due to the rules of padding set in autolayout.With GRID mode there is NO CONSISTENCY in padding. NOW, the GRID rules. So if do I set a vertical padding 10px, BUT the grid does not “afford” that padding, IT’S THE GRID THAT WIN, padding change, but I don’t have any information about this changement (just zooming in and checking manually).Moreover, with Wrap Mode, if did I resize the frame of the autolayout - with all the elements inside in Fill container - especially after the introduction of the precious Ratio function) - the elements would had resized. Now, not!Elements go off the grid.Changing a grid already existing is IMPOSSIBLE through the new GUI.It is impossible to ALIGN things in the grid.Joseph Muller Brockmann would be very unhappy :(  Everything doesn’t work.This new tool has

新版UI界面功能太难用了，能不能弄回旧版本，网格布局那些全部没了，用起来好别扭

It would be more convenient if objects resized with a fixed aspect ratio automatically rounded their dimensions to the nearest whole pixel. At the moment, one of the dimensions—either width or height—often ends up with fractional values like 40.63px, which can cause visual inconsistencies and alignment issues. Ensuring both dimensions snap to whole pixels would enhance precision and improve the overall editing experience.

The recent Aspect Ratio update has brought with it a frustrating change to the way objects snap to the pixel grid.Previously, when changing the size/position of an object by dragging, it would snap to the nearest pixel. If you needed to get more specific - and have an object at 1.5px width for example - you could change this via the properties panel without having that object snap to the nearest pixel in terms of positioning/size.This felt like a really nice balance between snapping to the nearest pixel with the cursor, whilst retaining control over incremental choices via the properties panel.Now, after the most recent update, we no longer have this control - when you change the size of an object in the properties panel it snaps to the nearest pixel.For example, if I have a rectangle which is 6.5px wide and 1.5px tall, and I use the properties panel to change it's height to 2.5px, it'll automatically change the width to 6px. The same goes for positioning.Of course I can go into the pr

Hey guys, I was playing with Buzz and after pasting one of my assets, the auto-layout property is gone! It seems auto-layout is not supported on the parent frame, or is this a bug? If it’s not a bug, there’s no use for us. We create hundreds of Newsletters and ads with auto layouts which flow automatically depending on the content.Also will the collaborators be able to swap instances of a symbol on a design and hide items? Thanks!

The Figma Sites Webpages Canvas, Has a max height, I can’t continue modifiying the work.  

Previously I was able to manually change the spacing between equally distributed frames or objects  even though the items were not in an auto layout. Now that functionality is gone and I can only edit the spacing manually or by using the pink interface between items - which makes it harder to get specific numbers.

The most recent update changed a few things in Figjam. First, they added a lot of new “shapes” (which is just a rectangle with an icon inside), and added a couple of new default colors. HOWEVER, they also changed the base colors for stickies!They are now way paler, with washed out, low contrast colors. I’m sure it was supposed to make them look both like real sticky notes and to increase the contrast between the background colors and the text for accessibility reasons, but I feel the colors don’t contrast enough at all between one another.I use colors a lot to help with identifying specific sections or types of notes, I often use every color of stickies available to distinguish between specific uses of each (like taking notes during user tests, each color representing a scenario).Unless custom colors are finally made available for stickies in Figjam, I think they are going to be way more annoying to use for me from now on.  

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