Share Your Feedback

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

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. 

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

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?

In dev mode please place the assets panel above the code.because the code takes a second to generate it makes it feel like the assets panel moves right before you click it

Hello! I am a community advocate for FOF, Sofia for Bulgaria and we experience difficulties when we want to use Bulgarian Cyrillic in several fonts with the “Stylistic sets” feature, but Bulgarian Cyrillic just doesn’t work. When I try the same in Adobe Illustrator for example - there are no problems. The only solution we’re able to find is to change the font’s core defaults to this type of Cyrillic, otherwise, it is impossible to use the stylistic set in Figma. Best Regards, Daniel Dungyov

Copy properties does not work as it did beforeBefore if i copied properties from one auto layout to another it copied everything, but if i paste properties onto a square or any other shape and then copied properties of that square - all info about the paddings would have been erased. It was easier this way to just copy the fill color, stroke and corner radius styles to a different looking auto layoutNow even if you copy properties from a shape it still keeps the paddings and gap size

When opening the Text styles panel, it should automatically scroll to the currently applied text style instead of starting at the top of the list. When you have a large list of styles it becomes really difficult to swap between different styles in the same category, such as switch between display styles or body styles 

While using Claude.ai with the Figma connector Claude told me it wasn't able to programmatically insert the contents into the slot inside a component “because Figma protects slot nodes from plugin writes”. If this limitation is intentional, why? It serious limits the usefulness of the connector. Please allow the connector to write to slot nodes.

Figma has been an essential tool for my daily work as a solo UI/UX designer. However, the recent bundling of AI Credits into the Professional plan has significantly increased the subscription cost, even for users who never use AI features.Previously, I was paying around USD 20/month for the Professional plan. After the Config 2026 changes, the cost increased to approximately USD 55/month because AI Credits are now included by default. There is currently no option to disable AI Credits or choose a lower-cost Professional plan without them.This creates a real problem for independent designers, freelancers, and small businesses. We subscribe to the Professional plan because we need features like:Unlimited design files Components and Libraries Variables Advanced prototyping Version history Team collaborationThese are the reasons we pay for Professional—not necessarily for AI.Forcing every Professional user to pay for AI, regardless of whether they use it, feels unfair. Many of us already r

Hello Figma Team,I've been a long time Figma user and have relied on it extensively for website design. Unfortunately, over the past year I've found the overall experience becoming increasingly frustrating. Many workflows that were once fast and intuitive now require significantly more effort, and it feels like the focus has shifted away from the needs of production designers.Some of the issues I've encountered include:Copying a layer from one frame to another no longer pastes it in the same relative position. This used to be a huge time saver when working across multiple artboards. Selecting layers has become much more difficult, especially within nested Auto Layouts. I often find myself drilling through multiple layers just to select the object I want. Auto Layout has become overly complex. Small changes frequently produce unexpected results, making simple edits unnecessarily time consuming. Changing layouts, such as moving from a four column grid to a three column grid, often stretc

I really appreciate how much Figma has invested in Dev Mode and AI features. With MCP support and AI-assisted workflows, Figma is becoming an essential tool not only for designers, but also for developers.However, I think there is a growing group of users that doesn't fit well into the current pricing model: solo developers and small teams without dedicated designers.I'm currently a paying Professional subscriber because it's the only plan that gives me access to the developer features I need. As a solo developer, however, I mainly use Figma for:MCP integration with AI coding assistants AI-generated UI designs Editing designs with prompts Inspecting layouts Generating code from designsI rarely use advanced collaboration features, team libraries, branching, or other designer-focused capabilities included in the Professional plan.I would love to see a new plan designed specifically for AI-first developers. It could be a lower-cost individual subscription that includes Dev Mode, MCP, AI d

Hi everyone,First off — Figma AI (Agent) has been an incredible addition to our workflow. Really impressed with how well it understands and interacts with design systems. Huge kudos to the team behind it!I've read through the article https://help.figma.com/hc/en-us/articles/38978644498199-AI-workflows-collection-Best-practices-to-help-Figma-AI-understand-your-design-system#h_01KKFV30GE7M7PH1YPBCNXG07W , and while it provides great foundational guidance, I'm finding it hard to translate those principles into a concrete restructuring plan for our own design system. The "what" is clear, but the "how it should actually look in practice" is still a bit ambiguous.We'd love to restructure our design system to fully align with Figma AI best practices, but we're missing a tangible reference to work from. So my question is twofold:Could Figma publish an official example design system file that demonstrates these best practices end-to-end? Something the community could open, inspect, and use as a