Share Your Feedback

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

really figma team? now i must click individually to toggle layer visibility. just yesterday i can hold mouse click to hide multiple, it was smooth before, 1 click hold - hide/show multiple.now is disaster, wasting time, bad ux. 

HiI have just used Figma motion for a quick animation and in general it works ok, but I have noticed a few things:Gif export is low quality even it’s set to High. Grey colours show pixelated. I tried to export it at 2x and resizing the file. It does help with image quality but it obviously increases the file size which is the reason for exporting as gif in the first place. Trying to scale or rotate a layer automatically creates a keyframe when I don’t want to, this doesn’t happen with position.  I can’t keyframe component properties, it would be really helpfulIn all, it’s a great addition to figma. However, I have experienced some glitches on the desktop app, I hope having all of this stuff added doesn’t affect overall performance. It seems to improve when I quit the app and restart again.  Thank you.

Hello! In regards to the slicing tool/functionality, I had some feedback that I’m hoping can be taken back to look at possible revision. Here are the thoughts I had: • When it comes to the actual slicing, while it can snap to shapes, it doesn't naturally snap to the edge of the frame to prevent it from going over. • For the exporting of slices, the file-size of the exports is much higher than the equivalent export from Photoshop. For example, if I were to slice an email for the purpose of handing off to the devs in both Figma and PS, the Figma exports are 2-3X the size of the PS exports. This is an issue for our devs as they require the total file-size of the slices combined for the asset to be 1MB or smaller.• In PS, we have the capability to change the quality of the exports by % vs predetermined presets (i.e. high, medium, low), which grants more flexibility in file-size. To be able to alter to that detail would be of benefit in Figma. Hopefully I’m making sense in the above feedbac

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

Nested properties do not show up when selecting multiple instances of components Example when selecting 1: Example when selecting multiple: My expectation would be to also be able to set up the decoration left icon when I'm selecting both layers. 

I am quite certain I am not a robot. However, when creating an account just now using a work-specific email so that I could accept an invite to a Figma team, registration was a very frustrating affair. The CAPTCHA was far too long (5 questions), the instructions were maddeningly vague, and I failed multiple times. Each failure meant having to do the entire 5 question CAPTCHA again from the beginning. I attempted to switch to the audio version, hoping that might be easier for me to understand, but I failed that too. As a result, registering a new account took at least 15 minutes, and had it not been necessary for a work assignment, I would have given up altogether.Please consider changing your CAPTCHA to something that can be more easily completed by humans. While I certainly understand the desire to avoid spam signups, other websites with similar challenges have found approaches that require a user to, at most, click a checkbox. Perhaps Figma could follow a similar model.

JSON Code not updating the durations after making adjustments to the timeline. I’ve tried to close it and reopen. I’ve republished the component. Not sure what else to do.

I noticed a usability issue with the Figma Agent placement. Since the Agent icon appears on the right side of every frame, it often overlaps the area where users expect to grab the resize handle. While resizing frames today, my cursor repeatedly landed on the Agent instead of the transform handle, which disrupted the interaction.Possible improvements:Move the Agent to a corner of the transform bounding box. Keep the current alignment but add more spacing between the frame edge and the Agent icon.

As seen by the video, if i enter text in your file search and then try to clear the field with the x, nothing happens. Assuming this is a bug?

Dear My Love.. Figma Team, I wanted to share some critical feedback regarding the recent UI update to the Local Variables panel, along with a highly requested feature suggestion. 🚨 [IMPORTANT] Feedback 1: Excessive Spacing Between VariablesSince the latest update, there is a massive, unnecessary vertical gap/spacing between each variable row in the table (as shown in my screenshot). The Issue: This drastically reduces information density. It looks less like clean UI and more like a bug.• The Impact: For large design systems with hundreds of primitive variables, this requires an exhausting amount of scrolling. It completely disrupts the workflow and makes the panel feel cluttered yet empty at the same time.• Request: Please restore the compact, dense layout or at least give us a "Compact View" toggle in the settings. 💡 [IMPORTANT] Feedback 2: Support for Relative Units (%, em, rem)While we are on the topic of variables, we desperately need support for relative units in number/dimensio

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!

Hi Figma team,I’m developing a plugin that exports Figma Motion animations to PAG, Tencent’s vector animation file format.While working on this exporter, I’ve encountered several gaps between Figma Motion’s canvas rendering and the animation data currently exposed through the Plugin API.The most important issue is the transform anchor or pivot point. I cannot find a reliable API for reading the actual anchor used by Motion. This becomes critical when a designer has manually adjusted the anchor point. Reconstructing it from the node bounds, relativeTransform, absoluteTransform, or the first animation frame is not always accurate, especially for rotated groups and nested nodes.I also could not find detailed documentation explaining how node.animations should be interpreted and reproduced outside Figma. Some areas that need clarification include:Whether Position values are absolute coordinates, parent-space values, or offsets from the static transform. How Position, Rotation, Scale, Width

Hi there! I’ve been messing around with figma motion for the past day or so, and am loving it. This is going to speed up my workflow so much as a motion designer at a company who was previously primarily using After Effects. There are a few core features that are missing that would really take this to the next level:ParentingProbably the biggest thing missing for me. Right now there is no way to link a layer to another layer, seemingly. An example of when this would be useful:I’m animating a logo, and I want the word to appear from behind the glyph. The glyph is moving left, and the type is moving right I have a mask for my text that needs to move left with the glyph, while the type animates right (opposite the mask) There is currently no way to link the movement of the mask to the movement of the glyph to reveal my text, if I want the text to move independently of the glyph (because the mask is linked to the text, separating it and putting it in the glyph’s movement group means it is

Hi Figma Team,First of all, thank you for continuously improving Variables—they've become an essential part of our design systems and interactive prototypes.I'd like to request a feature that would greatly improve the experience for designers building financial, banking, investment, insurance, analytics, and data-driven products.ProblemCurrently, Number Variables only display raw numeric values without any formatting options.1000100001000001000000123456789However, in real applications these values are displayed according to the user's locale.For Indian users:1,00010,0001,00,00010,00,00012,34,56,789For US/International users:1,00010,000100,0001,000,000123,456,789Because this formatting is not available, designers have to use string variables, manually type formatted values, or create unnecessary workarounds, which defeats many of the benefits of Number Variables. Proposed SolutionIntroduce a Formatting section when editing a Number Variable.Example: Edit Variable────────────────────────

플러그인 구독을 취소하지 못했습니다.결제된지 하루도 지나지 않았고, 사용하지 않았습니다. 환불 부탁드립니다.[attachments redacted by moderator to remove personal information]

Loving motion so far, but sometimes I need to drop 2 keyframes directly next to each other. At the current max zoom, the keyframes still basically overlap. Can you please increase the max zoom so I can really get in there and see my milliseconds? 🫪🔎

While I’m very happy to finally have a timeline, I’m struggling to get it to work for prototyping. With a traditional timeline I can have things appear in/out as needed when users move forward and backward or open/close UI elements. However, Figma Motion doesn’t seem to work that way. When I have a sheet appear up with an animation inside, I want a close icon to allow the sheet to drop back down without playing the animation inside in reverse. This doesn’t seem to work in Figma Motion. I found a check box that suggests it can do this if I select “Smart animation”, but it doesn’t work. It seems bugged. Cool feature but having it focused on prototyping would make it the most useful.Lastly, please make it so that we can have an animation loop when it’s running in a prototype. Currently, they only play once. It would be great to use it for something like spinners or flowing animations on a screen a user is looking at.

This update is genuinely one of the most frustrating UX changes I’ve experienced in a professional design tool 😡 😡 😡The new left-hand navigation panel permanently steals ~60px of horizontal space on small screens, which is completely unacceptable. That space is my primary working area — the canvas. I am literally losing room to do my job so a panel can sit there doing nothing most of the time.Yes, Variables, Files, Assets, Find, and Library are important.No — they are NOT minute-to-minute actions.They do not deserve permanent, always-visible real estate. This panel is idle 90% of the time, yet it constantly punishes my workflow.On smaller displays, this feels especially hostile. Instead of prioritising the canvas (the entire reason Figma exists), the UI forces a bulky navigation column that adds zero value moment-to-moment and actively makes precision design harder.This change feels like it was designed for: Large monitors only Product demos Feature discoverability …not for actu

I want to share feedback on the Figma Make credit system, because in its current form it is not workable for real projects.Yesterday I spent one working day building a page in Make (Full seat, 3,000 credits/month). By the end of the day I had consumed almost the entire monthly allocation — without reaching the intended result. The core problem: the agent frequently makes mistakes, ignores constraints, and breaks previously working parts of the build. Each mistake requires another prompt to fix, and each fix consumes more credits. The more rework the agent causes, the faster credits drain. Effectively, users pay for the model's errors.Suggestions:1. Improve agent reliability, or stop charging full credits for correction cycles caused by the agent's own errors.2. Add cost estimates before execution, usage alerts, and spending caps.3. Reconsider whether 3,000 credits is a realistic monthly limit for professional iterative work — right now it can disappear in a day.I like the product conce

Currently, Figma provides version history for files, but there's no way to know when a specific element was added to a file — for example: when was this card added? When was this component placed here? When was this interaction or behavior introduced? Version history helps you compare states of a file, but it requires manually scrubbing through versions to find when something appeared. It would be very useful to have a per-element timestamp or "date added" metadata, similar to how some tools show creation dates on objects. This would help teams with:- Auditing design decisions- Onboarding new designers to existing files- Understanding the evolution of a design without digging through history Is there any existing workaround, or is this something on the roadmap?

I found an issue with Figma Motion. After exporting to SVG, the animation direction changes from what I originally created in Figma Motion. (Video attached)In Figma Motion: The line heights scale up from left to right.The line heights scale down from left to rightIn the exported SVG: The line heights still scale up from left to right. But the line heights scale down from right to leftI checked other export formats, and they work correctly. However, SVG is required for my project.Could you please help me resolve this issue?

Previously, when export the frames, the pdf pages were combined into one pdf file. Now, it suddenly changed with separated pdf files per each pages. So I have to merge the pdf files. I do not understand why it changed to this burden way. Please restore the pdf export function. Any other thoughts?