Share Your Feedback

I think It’d be much better if Figma to stop treating its products (FigJam, Slides, Buzz, Site, Make) as separate file types and start treating them as page types within a single file.Every time Figma releases a new tool, it forces us into another siloed file type. If I’m working on a product feature, I shouldn't need one file for research and flows (FigJam), one for Exploration (Design), one for presenting to stakeholders (Slides), and another for campaign assets (Buzz).It breaks context and creates insane file sprawl for what is ultimately a single project.If these were all just specialized page types inside a single master file, everything would live under one roof: Page 1 (FigJam): Research & User Flows Page 2 (Design): High-Fi Mockups & UI Systems Page 3 (Slides): Stakeholder Deck Page 4 (Site / Buzz): Landing Pages & Marketing I know this clashes directly with Figma's tier/seat pricing model for different products, but purely from a UX and workflow perspective,

Hi Figma team,When creating Text Styles, Figma currently captures properties like font weight, size, line height, and letter spacing, which is great. However, color is not included as part of the Text Style definition.This means that even when a Text Style is applied consistently across a design, the color still needs to be set manually every single time. For teams working with a strict brand identity, where specific text colors are tied to specific text roles, this creates unnecessary extra steps and increases the risk of inconsistencies.It would be really valuable to have the option to include color as part of a Text Style, so that a heading style, for example, always carries its correct brand color by default.If there's already a workaround for this that I'm not aware of, I'd love to hear about it.Thanks for considering this.Justin Eleveld

seems like a simple thing but yet it cant find them

Hi, I think my request is obvious and I bet all pro tier users agree. We really need this. Thanks

My name is Gleb. I'm a producer at a regional TV channel in Bashkortostan, Russia, and this is my Figma love story. I found Figma in 2022. Before that I had tried several times to learn Photoshop and the tools around it, and failed every single time  I just bounced off them. Then, after everything that happened in 2022, I realised I had to level up my skills if I wanted to earn more and provide for my family. A post about Figma showed up in my feed, I decided to give it a try, and it was love at first sight. The interface was so clear that I only opened a tutorial when I was truly stuck. I remember barely leaving my desk for a week, digging through the software and enjoying every minute of it. Figma replaced everything for me — Photoshop, PowerPoint, Miro, all of it. And a special thank-you for Community. That is where I go for inspiration, where I train my eye and learn from people far better than me. Now, how Figma changed my life. 2025 was financially hard. My wife was pregnant, we

The features added to Figma in the past few years (FigJam, AI, Motion) is creating lag and additional complexity for a tool that was historically lightweight, collaborative, and easy to build UI for developers. While I love the innovation, I wish I could turn off all these features so they don’t create unnecessary cognitive load while I’m working. Thank you for your understanding.

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. 

안녕하세요피그마 환불 요청 드립니다참고이미지 넣어드립니다 

Since changing the animation duration for a single destination updates all selected interactions simultaneously, the duration input should be directly accessible under the 'Mixed' state. Forcing designers to temporarily select a specific frame just to reveal the millisecond field creates an unnecessary friction in the workflow. Please consider keeping the animation settings visible even when destinations are mixed. 

Hi everyone! Last year we acquired Weavy (now Figma Weave), to power the next generation of AI-native creation at Figma. Figma Weave is a creative workflow canvas where you can build, edit, and direct how visuals come to life.As we explore how to bring Figma Design and Weave together, we’d love to hear from Figma users like you:👉 How has your experience been getting started with Figma Weave?
👉 How does it fit into your design process today?🔍 Get startedHere are some resources to explore:Read about how we built five simple workflows to create multiple variations of brand assets on our blog. Browse 20+ new creative workflows from Figma Weave on the Figma Community. Check out FAQs on our Help Center.We’d love to hear your thoughts! Feel free to reply in this thread and share your experience.

Please provide an option to remove this "grid" in autolayout; it's become impossible to work with. I didn't write this before because I thought I'd get used to it, but NO, it's terribly unnecessary and completely inconvenient. Please provide an option to remove autolayout by default. This feature is only for some kind of perverts. Whoever suggested it obviously has never used their own program. Thanks for your attention.

 i can do this all day。。。。。。。。。。。

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

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

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.