Share Your Feedback

1. Visual Clarity of Selection StateSelected state issue with suggested change. Issue: The current selected state for measurement annotations is barely visible (appearing as a faint, sub-pixel outline). Suggested Fix: Change the selection outline to blue when an annotation is selected, matching the existing visual behaviour of the ruler selection state.  2. Selection Persistence & Unintended ModificationsGIF showing selection issues.​​​​​ Issue: Clicking a new measurement annotation currently retains previous selections. This causes off-screen items to remain active, leading to accidental moves or deletions. Expected Behaviour: Single-clicking any measurement annotation should clear all previous selections by default. Multi-selection should only occur intentionally when holding Shift or Cmd / Ctrl while clicking. Similar thread found here (Closed):  

This thread is here for you to share your thoughts and suggestions about the Figma Forum.We’re proud of the work we’ve done so far, but we know there’s always room to make things even better.
Here’s some prompts that you can use:What are your thoughts on the forum makeover of January 2025? What do you like the most? What have you struggled with so far? / What are the top three areas that need improvement? What would you like to see us implement next?If you spot a bug or have any feedback, drop a reply here — we’ll do our best to respond and improve!

This is so annoying! Each month I need to search for the invoice in your unfriendly interface. Seriously now! Better unsubscribe the service than getting such frustration.

FIXABLE OR NOT?I find that I now cannot use mose wheel to scroll when dragging a layer in the Layers panel.The only way to do so is to drag the layer to the top/bottom of the list like when using a touchpad.I HATE IT!It takes concentration to control how fast the scrolling is (how close i bring the layer to the edge of the list) and it doesn’t feel precise enough. Especially if the layers panel is made smaller/shorter.Scrolling with a mouse wheel is consistent and I am used to it enough for doing without much looking at the panel.Please tell me that it is some setting that I have accidentaly checked and that I can return my mouse wheel scroll.layers panel 

Not just for those who are studying or have a solo design system, figma pricing is aredy to high to not have features to another planos 

Fix it Figma team 

I realise some people will laugh at me for this post, that’s ok, I still love you and hope you have a great day :) Hi Figma team, I make a habit of thanking my AI for doing a good job as I’m sure many people do. It’s a natural and good part of being human to express gratitude. It’s also increasingly important that we continue to say thank you as more of our interactions with actual humans are by text and chat only. The way we treat AI can impact the way we treat people.I was wondering if you could please set something up with the AI in Figma so that we aren’t penalised for saying thank you. For example, Agent just did a good job for me, I said “Great job, thank you”, and it cost me 6 credits. We all know Figma credits are expensive and several thank you’s a day add up.How about a rule that detects if the message is under say 50 characters and it includes - thank you, thankyou, thanks, good job, great job, appreciate (etc) - it gets a free pass? It’s flagged as a thank you message and n

I’m working with a team on a large project, and we have a complex file structure. Removing the file previews has made it much harder to navigate our file system. Each group of files has its own color; previously, you could just glance at the main screen and understand where to go or see the file name in the preview. With only the folder icon and name, it’s much harder to remember where something is located. Please give us the option to revert to the previous interface with clear file previews.  

If I> select a few frames> create a new export> then deselect the frames> then reselect the frames> the export build is wiped out and I need to start over:Please restore previous behavior that remembers export build

It’s incredibly annoying to make this disappear. Just let me hit ESC. Please. It slows me down so much. 

We just wrapped the big announcements at Config, and we know there’s a lot to take in.This thread is your space to share reactions, ask questions, and let us know what you're excited about (or still curious about) with regard to Figma Buzz. Our team will be actively reading and sharing relevant takeaways with the product team.  What we’d love to hear from you:What aspects are you most excited about — and why? Where do you still have questions or want more clarity? Anything that didn’t quite land for you yet?  A few quick reminders:If you need help with a specific account or file issue, please get in touch with a specialist on the Support Team. A note on Community Guidelines: Posts that veer off-topic or become unproductive may be moderated to keep the focus on the product at hand. Keep feedback focused on Figma Buzz — this helps everyone follow along.

I lost a key edit to a file, undo wouldn’t recover it. I found it in the version history.Hard to find Couldn’t restore the edit. I found it, but I couldn’t copy and paste it. I hit recover, but it would glitch up and go back to the other edit when I closed it.End result, I had to finish a rush item by cropping a screenshot, not by restoring it in Figma, even though I could see the edit I wanted to restore and tried for 15 minutes.Serious concerns about stability of product after seeing this.

Whose idea was it to put the little icon for the new AI agent so close to the upper right corner of an object? I can’t tell you how many times I’ve gone to adjust the size of an object and accidentally opened the agent. Each instance doesn’t take that much time, but when you do it countless times a day, it makes work that normally feels fluid feel disjointed. If I want to open the agent, the option in the left nav panel is super easy to access. I don’t need the agent connected to every object I touch. I’d like to see the user research (or lack thereof) that made team Figma think this was a good idea. You’re assuming the agent is so helpful and so needed that people need it right there. That’s confirmation bias at it’s finest. Please take this away or at least move it!  

Hi Figma team,I'd love to see sorting preferences persist across sessions in the Projects view. Currently, every time I navigate into a project and return to the home screen, the sort order resets to default.Our team numbers all projects (01, 02, 03…) to maintain a clear workflow overview. Having to manually re-apply alphabetical sorting every single time is a small but repetitive friction point that interrupts the flow.It would be great if Figma could remember the last used sort order, ideally per user or workspace. This seems like a relatively simple improvement that would benefit many teams who rely on consistent project naming conventions.If this is already possible and I'm missing it, I'd love to know how.Thanks for considering this.Best,Justin Eleveld

We need a side-by-side visibility!The switch from a floating/movable Variables modal to a full-screen tab has hurt my workflow.I need to see the canvas and variables side by side — to check a token change against the design, compare values across modes, catch mismatches before they ship.Switching back and forth constantly is tedious! This isn't just slower — it's causing errors. Editing without seeing the canvas means working from memory instead of visual confirmation, which leads to picking the wrong step in a scale or missing something like a contrast issue.Please! make it float again. 

Changing the Variables panel to be a tab along the side that takes over the view instead of a panel I can move around has impacted by design flow. I would often have the variables panel open side-by-side to my designs so I can view/add/update variables and build design simultaneously. Now I have to flip back and forth causing frustration and slower process.

The recent figma autolayout update has brought up conflicting emotions. From one point it’s great that the autolayout would work closer to code, but on the other hand for teams that do more complex projects than Web UI, this creates a loooot of issues. 3 things in particular, that I know for sure, will break what we've been using in case of complex layouts:"Padding now always gets the room it needs" - Often when necessary, I relied on the fact that you can set auto-layout frame size to 0 and add paddings inside to allow precise position of elements without affecting the size and position parent and sibling frames. Now that won't be possible. ⁠"Inside strokes counting in autolayout" - again pretty sure this will break layouts where inside stroke was used. ⁠"Stacks with gap set to auto no longer overlap" - A lot of cases it's better to have parent in the desired size than have the parent rely on the children. Then we will get uneven distances and paddings in some cases. All of this would

I’ve been thinking about how much difference good file organization can make when working on a design project.For example, how do you usually organize your Figma files and pages? Do you have a specific naming system for layers, components, and sections, or do you keep things more flexible?I’d be interested to hear what organization habits other designers have found useful, especially when multiple people need to work on the same file.

Hello! I noticed that in the Figma article What is Human Computer Interaction?, the author writes:Dialogue. Use clear and concise language to communicate task completion, like  “Purchase Confirmed” pop-ups after completing an online order. On Shneiderman’s website, he writes: Design dialogs to yield closure.Sequences of actions should be organized into groups with a beginning, middle, and end. Informative feedback at the completion of a group of actions gives users the satisfaction of accomplishment, a sense of relief, a signal to drop contingency plans from their minds, and an indicator to prepare for the next group of actions. For example, e-commerce websites move users from selecting products to the checkout, ending with a clear confirmation page that completes the transaction. I understand that they are variations of the same word but I would argue that in this context, it is important to use dialog because Schneiderman is referring to the importance of the graphical interface  (li

Looking to better understand gradient behavior in Figma.The example below shows a setup for a Skeleton loading layout/animation. The gradient sits above a background layer with a light grey color.skeleton reference I want the gradient to provide a small white highlight wave, animated across the background layer. It has stops of 0%, 24%, 48%, and 100%. Three of the stops are fully transparent (to match the CSS). Even when set to fully transparent (#00000000), a fill color is present in the transitional areas. This should transition from white to transparent.Currently, Figma requires setting the transparent color to match intended visual styling, here requiring setting the transparency to match the background layer. This feels like an unexpected setup step, and clunky.Is this intended? How does this align to CSS?  

On the vertical bar on the left (as per screenshot) how can I swap the 'Agent' button to the 'Assets' one so it's under 'File' instead?    

Hi, and apologies for posting a new question – it may well have been asked before. To be honest, I can’t be bothered to look it up. Besides, the more questions on a single topic, the better the chances of success.I’m not really sure how or what to write here, so I’ll just set out my ideas and suggestions – things I keep coming back to whilst working in Figma.Feature request: Responsive Component Swap Based on Container WidthIt would be extremely useful to have a way to automatically switch a component variant or nested component based on the width of its parent frame or container.When designing responsive interfaces, components often need to change significantly between desktop, tablet, and mobile layouts. Auto Layout handles resizing well, but sometimes resizing is not enough — the component itself needs to change.For example: Width > 1200px → Desktop Navigation Width 768–1200px → Tablet Navigation Width < 768px → Mobile Navigation Ideally, we could define breakpoint rules d

A bit meta, but found a bug in the Forum here 😅The emoji picker gets overlapped with the reply input:...also, it would be a nice-to-have feature to have a search in the picker.

Sometimes when I am working on a specific frame I accidentally click the Figma make sparkle icon and it brings up the chat as a popup and there is no way to click out of this unless you click out of the frame (it is extremely difficult because I use sections to group my frames)

 I ran into a font issue while working with MCP use_figma and wanted to share it here. I have a font installed on my system (Pretendard) that works perfectly fine in the Figma UI — it shows up as "Installed by you" in the font picker. However, it's completely invisible to the Plugin API when running through MCP use_figma. listAvailableFontsAsync() returns around 7,600 fonts, but none of them are locally installed ones. It seems to only return Google Fonts.loadFontAsync() also fails, and trying to appendChild a component instance that contains text using the font throws a font load error — even into a non-auto-layout frame. Steps to Reproduce 1. Install a local font on your system (I tried both ~/Library/Fonts/ and /Library/Fonts/ on macOS) 2. Confirm the font shows up normally in the Figma UI 3. Run the following via MCP use_figma: const fonts = await figma.listAvailableFontsAsync(); const result = fonts.filter(f => f.fontName.family === "Pretendard"); return result.length; // 0 awa