Share Your Feedback

Example:I have a bunch of elements that intentionally have a fixed height and width applied to them.I want to put them in a grid.When I do so - their width and height changes to fill. This is an unwanted destructive change and should be fixed or at least have a way to override.Is this how flex works in css? I don’t think it is - using display: flex - children keep their intrinsic size unless you explicitly opt into growing.

We need an option to retain our sort preferences. I notice that this change was made on purpose for people who thought they were missing their projects - but I think there should be a way in each person’s individual preferences if they would like to retain their sort preference every time or not. This is one of my most frustrating experiences when using Figma daily, and I think others agree. Lots of great updates have been made! This one missed the mark.

First of all, thank you for bringing motion design into Figma. I've been trying Figma Motion, and I'm really excited about its potential.Here are some thoughts I had while using it—features and improvements that I think could make the experience even better.1. Copy & Paste AnimationIt would be extremely helpful to have the ability to copy animation properties from one layer and paste them onto another layer.For example: Copy all keyframes from one object to another. Copy only specific animated properties (Position, Scale, Rotation, Opacity, etc.). Similar to "Copy/Paste Effects" or "Paste Animation" in other motion design tools. This would significantly speed up repetitive animation workflows.2. Better Text Animation WorkflowAnimating text is currently quite tedious because many animations need to be created manually.It would be great to have: Built-in text animation presets (Fade Up, Slide, Pop, Typewriter, Blur In, etc.). Character, word, and line-based animation. Stagger

Unsure if this would be considered a bug or feedback but it’s impossible to write words including the letter “n” within the text properties of components in Figma Buzz’s design mode tab in Asset view. The moment I type “n,” it immediately moves to the next frame instead of updating the text property or allowing me to continue typing. Editing the text directly in the canvas does not cause this issue, but it is frustrating to work around and troubleshoot for non-designer collaborators who are more comfortable using the properties panel instead of directly editing the text object.

I've been experimenting with multiple video fills in a fairly longer than average Figma Motion composition (2-3min). Thanks to the workaround from another thread, I've managed to get videos playing in the final export by adding two rotation keyframes.However, video synchronization still seems to be an issue. For example, I have a 141s video that's supposed to start at 0:00 when its layer appears at 32.14s in the composition. Instead, Figma starts playing the footage roughly 32 seconds into the original video, as though it's following the overall composition timeline rather than the individual layer's timing. It also unexpectedly loops later on randomly somewhere you don’t wanted.I've tried adjusting layer duration, opacity (0% → 100% with Hold easing), and Position/Rotation keyframes without success.Of course, Motion is still in Beta, but having independent playback controls for video fills (at least a start time, offset, trimming, or looping) would be incredibly helpful for more compl

When using the new text, Several functions in design are not available😅

The announcement of Figma Motion had me excited, but right now it feels like a more advanced prototyping mode. I understand that it’s still in Beta mode and I hope in the future it will actually be usable for integrating motion in a design system.Animation between statesIf I take a button from our brands design system, it would be very helpful to be able to keyframe states and variants. Maybe take a page from Rive’s book and add something like a State Machine.Text animationText animation is non-existent at the moment. If we want to create an animation of text being typed I’m not sure how we achieve this.TokenizationWhen exporting JSON, there are no tokens visible in the JSON file, it’s just raw values.Preset AnimationsThe preset animations are nice and all, but it would help immensely to be able to make a library of our own animations, so we can quickly build out motion components.Styles/ChoreographiesSimilar to how you can add multiple values to a typography and apply it as a style (c

I’d like a way to add a fill to a main component that is visible only while editing the component. It should not appear on instances used in other files through a library.Current behaviorIn a library file, I add a fill to a layer in a component, such as a background or guide color. I turn Show in exports off for that fill. This works, and the fill stays out of exports. I publish the library and use the component in another file. The instance still shows the fill on the canvas. These are client-facing end screens, so the fill shouldn’t be visible there.What I needWhen a fill is set to not show in exports, I want a way to have it also hidden on instances in consuming files. This could be a separate option, for example “Hide on instances,” or the same setting applied to instances.Design systems often need fills that help while building a component but shouldn’t appear in the final screens. The current workarounds are to hide the fill by hand on every instance, or to build a separate varia

I discovered by accident the new ⌥+TAB keyboard shortcut to quick toggle between modes (not sure what that’s officially called?). This seems super useful, except for whatever reason the order the modes are displayed in the quick toggle UI, is completely different from the order they’re displayed in the keyboard. In the toolbar they are ordered: Draw, Design, Motion, Dev Mode. Motion is relatively new, but I’d assume this is the order nearly everybody is used to.After hitting ⌥+TAB the quick toggle UI appears and the modes this time are ordered: Design, Draw, Dev Mode, Motion.This feels unnecessarily confusing to me. I rely heavily on the spatial positions of the active mode icon in the toolbar to see which mode I’m in. The icons themselves are relatively small and visually similar, so I feel like their position is a much stronger visual cue than the icon itself. So when the spatial consistency is suddenly broken, I have to stop and consciously read the labels and think about it for a m

Currently, when multiple objects are grouped, moving an individual object within that group causes it to be removed from the group. This makes working with groups unnecessarily difficult, as even minor adjustments require users to manually ungroup and regroup the remaining objects afterward.Instead, users should be able to reposition objects within a group while preserving the group relationship, allowing for quicker iteration and reducing unnecessary rework. This would make groups behave more predictably and better support common editing workflows.

Please enable Figma motion to work for “Change To” interaction in components. I use it in specific sections that change on click / mouse enter interactions but can’t use it because of this obstacle.Example: 1st, 2nd, and 3rd variant has animations. When I proto click → change to variant 2, the animation does not load. However if I have it looped, it starts after the full loop time length finishes for some reason.It works when using “Navigate To”, so for now I have to fake it by creating multiple frames of the full page instead of it simply working within the specific section.

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 

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.