Share Your Feedback

There are a lot of great adjustments and logical changes within UI3, however one of the main reasons I’ve still been using UI2 is the floating action bar.Can we get an option to dock this to the top of the screen or put it elsewhere? I use hotkeys for all of these actions and it’s kind of distracting in the center bottom of my screen with a dark background that keeps drawing my ADHD brain to focus on it when it’s not important to actually building designs.

I saw the update, “We updated the file browser to create a more consistent and seamless experience as you use Figma products.”I have too many files in projects -- I need the List View to skim them fast. This change does not make a more consistent and seamless experience, it’s slowing me down and making it much harder to find the files I need. Please bring this back, this is impeding my ability to find things.Is there a plugin I can use to get my list view back?

I just noticed something while transitioning from UI 2 to UI 3, and I’m wondering if others feel the same.Earlier, when using the K (Scale) shortcut, the focus was set in a way that pressing Tab would quickly take you to the width adjustment field. This made it really efficient to scale objects while maintaining precise dimensions.Now in UI 3, pressing Tab inside the scaling option focuses on anchor points first and seems to stay within that section instead of quickly moving to width or height. This small change makes scaling a bit less efficient for me since I now need extra keystrokes to get to the fields I use most.Does anyone else find this workflow slower? Or am I missing something? Would love to hear thoughts from the community!(Figma team, if you're reading this, it would be great if we could have the previous tab focus behavior back!) [Attaching screenshots for reference] 

As in the title. Either I will stay longer at work to do my job or I’ll change to HTML/CSS completely. Want to help? IMPLEMENT TABLES/GRIDS, NOT CRAPPY UI.

Some floating window panels in Figma are too small. For example, the color panel. I've created some color variables, but every time I want to select a color, I have to use the scroll bar to find a specific one. It's really exhausting because selecting colors is a frequently performed operation. Why can't we increase the height of these floating windows?

When I serach for a file on the home page, this research among the entire files contents (which is good). But this search algorithm do not prioritize file name it self. For example, if I have a clear match with the file name (meaning search = “ABCD”, filename = “ABCD - Project name”), this should be displayed at the top.

DOnt know why figma must hide propeties and the most of time user have to expand it to continue. Bad ux and create many annoying 

Hey, just wanted to bump this thread, as it’s been 2+ years and this issue still persists. It’s annoyin as hell and requires to create unnecessary wrappers just to eliminate this problem.Solution: I’d expect the swap component property to only affect the component itself, not the particular variant of it. Therefore I could set multiple Slots to be of a single component type (eg Button), then fine-tune their appearances slightly via that component variants (eg Button: Primary | Secondary | Tertiary etc.).

Please tell me if I'm just too used to something else, but this doesn't feel intuitive. It doesn't look like a button, let alone something clickable. I spent days trying to figure out how to bring the properties of a base component into the parent component.Additionally, I have to hover over it to even realize that applying the variable is possible—there's no visual indication of it. You need to hover to discover it.  

"Regarding the page names on the left side of Figma, when we are building a component library, each component may have updates. We hope that there can be a tag next to the page name to indicate the 'updated' status. Is it possible for Figma to implement this in the future?"

I want to slice the layers within a frame, but the 'Snap to Pixel Grid' feature is not activated, which makes the slicing process very inconvenient. I would like to know the reason why this feature is no longer available. Please bring back this functionality, as its absence is causing disruptions in my work. When working with Auto Layout and framing the entire page for slicing, I hope the 'Snap to Pixel Grid' feature will be activated. Figma, please take quick action.

The “Start editing” alert dialog seems like a dark pattern. People could accidentally upgrade their seat without realizing it. This wasn’t a necessary addition. Was someone confused about how to upgrade their seats, because if not, this comes across very shady.  

I’m trying to take the certification course ($97) and I got stuck because the menu in the video is different than the menu in the app. See attachment. Of course there isn’t a phone number to call about this. Outside of demanding a refund, I thought I’d try asking here. The Back to Files option at the top of the menu doesn’t exist in my copy. I have the latest version installed. A pet peeve about doing these online courses is there isn’t a a human to contact, and the AI chat bot is an idiot. 

It’s been extremely helpful for devs to be able to add their own annotations during handover. Using comments will only add extra clutter to people’s inboxes with unnecessary notifications

Hello!I would love to get support about moving files from an expired account to a new account.I have been using my school account for the edu plan and got a notification it is expired. I still need to use the materials in the previous account, Is there any way I can access and edit the files in the previous account?

Hi,I’m digging the Figma app - it is helpful. I’m used to having the blending options show right under “Appearance” but now, I’m seeing that I have to select the color hex button to access blending options like “Overlay” or “Multiply”. Can we get this back to the way it was? I’m not sure if I’m missing anything on my end but if this is the latest release, it is a cumbersome experience for me to have an additional click just to access the blending tool. Furthermore, how would I even know which layers have blending associated with them? As of now, I’m forced to click that layer, then the color palette, and then be able to see the drop icon to see if it indeed has blending on it. The 1st 3 screenshots are the current experience I’m seeing. The latter 2 are the previous version - which I think it a whole lot better and saves a lot of time. Thank you.

The Figma boards I work with (on Mac) are very wide and tall. The slider navigation is just too hard to grab on the bottom of the screen when there are other menus popped over, and it disappears into the board and into the images, perhaps there could be a setting allowing the user to change the color to meet their current visibility needs. It would also be nice if the right and left menus could be easier to fully minimize out of the way (without using the permanent setting to remove them from my view). I am not always working on an external monitor and on the 14” screen these take up almost 4” of the design window.

Coloring strokeHi guys,I have an idea that can we have all stroke property below for each generated color?For example, I want right stroke to be blue, and down stroke to be black, how can I do that? 

trying out the figma ai “make image” thing.. clients can spot the ai images, and they dont like them. They’re really small in resolution too. 👎

There is little that Slides offers me which I can’t do in Figma already - except add presenter notes. Why not just enable the ability to add presenter notes to Frames?The fact that I can’t prototype within Slides really kills the usefulness of this feature. Second, having to import all the content I’ve already created in Figma into a Slides file is a pain which could be avoided with presenter notes on Frames. 

when we publish library when there is no change to publish then Publish button sould be disalbled not active. 

The new aspect ratio lock is good so far, I have no problems with it, but I think we can make it great.I was just using the feature for locking the aspect ratios of images and using auto-layout and fill width to grow/shrink the images to fill the frame. That works well, but I noticed two things:Order of operations: I have to set a fixed height and width first with the aspect ratio I want (400px X 300px for example for a 4:3 ratio), then I can lock the aspect ratio, then I can set the width or height to fill. Not the end of the world, but it takes a couple of steps. What if we could specify the ratio we want at any time? For example, place an image, set it to fill the frame, then specify the ratio. Maybe it’s a dropdown select of common aspect ratios or maybe it’s a manual input. Usefulness for developers: When inspecting the image in Dev Mode, the aspect ratio really isn’t helpful. For example, on one of my images with a 3:2 ratio, the CSS style for the image says “aspect-ratio: 332.0

I request the removal of the “Help” question button in the inspector panel. It is intrusive, persistent, and annoying, similar to a pinned chat agent that obscures relevant information. It is also redundant since help is available in the toolbar menu. Please remove that button; it’s driving me crazy!

Our design system devs asked us designers for a better way to compare changes within our component specs between updates.  We stage our components as instances in a separate spec file from the library file the components are published from.  Each component and variant is contained within an individual section acting as a wrapper.  The wrapper is where we enable a “ready for dev” tag to capture a version history.  Using this method we’ve run into a few obstacles: Sections don’t capture granular changes, we’ve had to switch from wrapping our component instances in sections to frames for a version history to be recorded within the compare/diff window. Ready for dev version history can only be viewed by first entering dev mode, then entering focus view on the versioned frame (it doesn’t show if you enter focus view from design mode). `Compare changes` within the standard dev mode view does not show this information and instead compares against the original component or shows version histor

Dear Figma Team,I would like to provide feedback regarding the behavior of stroke and padding when exporting designs for CSS implementation. While Figma offers excellent design tools and helpful CSS hints, there is a notable inconsistency between how strokes are visually represented in Figma and how they translate into CSS code. This discrepancy can lead to confusion and extra work during the development process.Issue DescriptionWhen designing input fields in Figma, strokes (borders) are measured separately from padding, and padding is displayed as starting from the outer edge of the element's frame. However, when exporting to CSS or implementing designs manually, borders are treated differently due to the CSS box model: In CSS, padding is measured from the inner edge of the border (stroke). Figma suggests using box-sizing: border-box for correct border inclusion in dimensions, but it does not account for the fact that stroke thickness affects the visual padding. Example ScenarioIn m