Share Your Feedback

📣 Don’t make the same mistake we did in attempting to clean up some projects by taking advantage of nesting folders 🚨If you move a top-level folder from your “All folders” section into another folder, then realize you actually want it back at the top level (perhaps due to the inherited permissions not being suitable, or just because you re-thought your organization strategy) there is apparently no way to reverse this change.You would think you could drag the folder back onto the “All folders” option in the sidebar: Nope! Or perhaps up to the team name that shows at the top of the page… Nuh Uh! Maybe right-click > “Move…” on the folder will offer the “All folders” option, maybe even under the “All” tab Negative! We looked through all the documentation and best practices guides we could find and this appears to be a fully-unmentioned gotcha 😖The AI support agent “helpfully” suggested manually re-creating such folders back at the top level, reapplying permissions as desired, and fin

It seems a little weird that you can’t copy a link to a layer within a component instance. I understand why this might be technically difficult, but it has been a real pain point for our engineers recently who would like to be able to point their AI coding tools to layers or frames inside components and who aren’t attuned enough to what’s going on inside the layer hierarchy to know why they can copy links to some things but not others.

Figma, Auto jump to next comments when previous comment is resolved is frustrating to use. Most of the times when we resolve a comments we tend to look and ponder on screen if we want to add any new comments. When it auto-jumps we need to search for the section again which is really bad experience. Please look into this. 

I was very excited to hear that grids were coming to Figma. CSS Grid was introduced years ago and brought with it many things that flexbox was incapable of doing, so I was hoping for a similar level of new capabilities here, and I genuinely cannot believe that this feature is being shipped in its current state (even as a ‘beta’). This is a very long post, but I feel like this feature has been implemented so poorly that it legitimately sows doubt in Figma’s capabilities to deliver features in the future.Inability to ‘hug’ contents Both rows and grids themselves are unable to resize themselves to match their contents (‘Hug”). Row heights must be either “Auto” (1fr) or a fixed height, meaning that if you want your rows to be sized per their elements, you’ve now manually defined each row height in px (not even a variable value), and instead of getting a clean CSS output, now you have however many rows defined in exact values, destroying any chance of scalability. This alone makes this fe

I don’t know why did figma launched sites if they wanted to bury it somewhere in the corner and not look at it as a product. I have gone through multiple reviews of people from Reddit to Youtube and everyone is saying that the product is super immature right now from SEO to CMS to animations. So the question is when is the team going to improve it to a point that people that work on Figma can stay on Figma for other work as well?

根据用户习惯默认锁定缩放比例 

The shortcuts Alt+B and Alt+N are prone to accidental triggers. Since the two keys are adjacent, mis‑hits are fairly common in real‑world operations.The core issue lies with Alt+N, which triggers "New File", and the high recovery cost after an accidental trigger: when you accidentally create a new file and close the window immediately, the blank sketch remains. Users have to navigate to the file directory and delete it manually via the right‑click menu.In my view, the root problem is not the accidental triggering itself, but the severe consequences and high recovery overhead it brings. It generates unwanted files that require extra cleanup steps, which easily interrupts the ongoing design workflow.Here are several proposed solutions:Reassign either Alt+B or Alt+N to reduce the risk of mis‑hits between adjacent keys. For blank documents with zero edits, do not save or generate files by default upon window closure. Enable custom shortcut configuration, allowing users to avoid key conflic

使用Agent频繁遇到无法访问PingFangSC字体的限制，希望可以解决 

I’ve noticed a usability issue in Figma around discovering updates/published files . Currently it’s difficult to tell whether anything has been updated or need to be published. There’s no immediate visual indication in the left panel, and users must actively open the Assets panel to check if updates are available.This makes updates easy to miss and adds unnecessary friction.Suggested improvement:Introduce a small notification indicator (e.g. a dot or badge) on the relevant menu item. This would give users an at-a-glance signal that something has changed and needs attention, without requiring extra clicks or manual checking. Thank you!

Been testing out the Figma Agent using component library and have found it struggles to use nested component properties. While guidance for agents talks about buildng reusable blocks, it seems like this doesn’t work well with page-level compositions we use. There are page pattern components the agent fails to use nest components within. Here’s how it explains its failures - These are 2 of 3 patterns of failures agent was having building pages trying to use a page component and other compositional components. Pattern 2 — Complex nested prop objects on layout components (7 "Required dependency not found" failures)Higher-order layout components like Layout/Record page, Page header, and Tabs expanded failed with "Required dependency not found." These components have deeply nested prop structures:Page header: 8 props including boolean toggles (has Avatar, has Detail, has Actions), variant selectors (Breakpoint, layout), and nested sub-instances (Avatar, Labels, Header actions, Page header d

You just added 1 to 2 clicks to a feature that worked perfectly fine and only required one click.As a power user that needs to quickly select a hex value or change it you just added the equivalent of hundreds more clicks a day to my work load. I know I probably sound pathetic but I’m having a hard time justifying the changes to what I thought was a functionality that was as simple as efficient. Why add complexity to simplicity??Am I the only one complaining about this? 

Used Figma Motion Beta. The key frame doesn’t work for gradients (The position and opacity og gradient points).

We're on a Figma Organization plan, on an annual contract. Recently our team started getting logged out, and now only two people can be logged in at the same time. This didn't happen before, and we haven't changed anything on our end.We asked our Account Manager what happened, and they told us: "we haven't historically enforced the Acceptable Use Policy with the same rigor we're applying now." In other words, the rules didn't change - Figma just decided to start enforcing them harder, partway through our contract, without telling us in advance.This is concerning. We allocated budget for this agreement based on the assumption that the terms and level of service would stay stable for the length of the contract. If Figma can quietly tighten enforcement whenever it wants, with no notice, then the terms we agreed to don't really mean much - Figma can change how the contract works in practice without ever changing the contract itself. That's a real imbalance of power between Figma and its cu

Been testing out the Figma Agent using component library and have found it sometimes uses slots ok and often times bombs. I asked it what the problem was and got this response to pass along...it’s one of 3 patterns of problems the agent encountered. Pattern 1 — Slot-based composition not supported as JSX children (20 of 33 failures)This is the biggest issue. The design agent tried to nest child components inside container components via JSX children:jsx code<ComponentBox2 hasHeader={true} boxHeader={{heading:"Staff Info"}}>  <ComponentDescriptionList3 mode="vertical" numOfPairs="4" .../>  ← REJECTED</ComponentBox2>But Library's Box uses a SLOT property (Content#20610:16) for its content area — the guidelines say "Append children directly to the SLOT node." The JSX renderer doesn't support passing components as children into slot-based containers. This affects every Box (6 failures) and every Tile (9 failures in v1). The preferred slot values are correctly defined (Des

While applying for the Figma Education plan, I noticed the mandatory Terms of Service agreement is presented as a Yes/No radio-button choice.Because the user must agree in order to proceed, selecting “No” doesn't provide an alternative path. However, presenting “No, I do not agree” as an equal radio option can create an expectation that disagreeing may still allow the user to continue.A single “I agree” checkbox might communicate the interaction more clearly: unchecked = agreement hasn't been provided; checked = the prerequisite has been fulfilled.I understand the current design may intentionally make the consequence of declining explicit, but I wonder whether the radio pattern introduces a false affordance by presenting a choice that isn't actually actionable.  

The Publish Library action feels really hidden, and its location doesn't make much sense in a design system file.Why not make it a global action, similar to the Share button? When you're working on the design system figma file, publishing the library is one of the primary actions.Right now the flow is:Assets → Library icon → Publish → Wait...It feels unnecessarily buried. Let's make our lives easier.

The captcha puzzles to verify your login might be the most ridiculous thing I’ve seen in my entire life. I’m supposed to match a pattern to an image with an astronaut standing on top of said pattern so I can’t even see it. And the image is AI generated so the pattern isn’t even an exact match anyways. And I also have to do 3-5 of these just to login. Captcha has always been an AI training tool but at least it used to not be so blatant.

would it be possible to add a moveable anchor point that can be switched on and off.so that when ever i pause the motion design the time line cursor (time indicating cursor ) starts at the anchor point it is a pain to fine tune animations when i have to drag the time line cursor to where i want or wait for the loop to finish to start at my spacific point this feature would be very use full for fine tuneing specifice areas in the motion design that require precisionthis feature could be upgraded to have multiple anchor point each toggleable with shortcuts say like the number keys (1,2,3,4,5)

Hello Figma Support TeamI’m here for an update to reduce my seats  which i have accidentally enabled by creating a design file, thank you. I am unable to prevent this from happening at certain times, 1 click on Continue , just immediately converts my present plan into the full seat, Won’t happen again, I’ve raised a request for this immediately after the disaster, I’m seeking support here for the visibility,(help.figma.com/hc/requests/2049844)Best,Vasanth

I’d like to share feedback regarding the implementation of AI credit limits in Figmake. As a designer managing multiple complex projects, I believe credit restrictions would greatly undermine Figmake’s usefulness in real-world design and prototyping workflows.  1. Most AI usage is for fixing bad or incomplete output, not luxury use.  In practice, a large percentage of AI prompts in Figmake are iterative—used to correct layout issues, rebuild misinterpreted elements, or align behaviors with visual intent. Each refinement quickly consumes credits even though the output quality depends on that iteration. Penalizing iteration limits the model’s ability to produce accurate prototypes, especially when the AI output is imperfect through no fault of the user, making credit usage really unfair and frustrating.2. Predictability becomes impossible, discouraging adoption.  With a credit cap that no one knows how to predict and calculate ahead of time, I can’t plan how far my Figmake usage will tak

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.

错误：无法复制粘贴 Figma 环境中的交互：Windows，Figma 桌面应用 + Chrome 网页版 问题开始日期：2026 年 7 月中旬 重现步骤：1. 选择具有交互的图层 2.在原型面板内选择交互条目，或点击紫色面条连接器3。按Ctrl+C 4。选择目标图层，按Ctrl+V，结果：交互无法粘贴。它总是粘贴旧的剪贴板内容。预期：复制交互规则并粘贴到目标图层。我尝试过的排查方法包括：• 清除Figma桌面缓存 • 完全退出并重启桌面应用 • 硬刷新浏览器，无痕模式 • 验证浏览器剪贴板权限 • 在全新空白的Figma文件中测试 • 尝试分别选择noodle和原型面板交互行，所有尝试均失败。重要提示：这个bug存在于桌面应用和网页浏览器中，而不仅仅是网页版。

Like many design systems, our current library uses placeholders + instance swap and we would love to switch to slots.The issue: While it’s possible to wrap placeholders in a slot to preserve content in existing instances, that content is no longer preserved when the instance swap property is removed from the original component. As soon as we remove the instance swap property from the parent component, all instances lose their swapped content.This means we have two options:Remove the property anyway and cause major breaking changes to hundreds of projects Accept redundant properties in the already crowded property panel for any component we switch from instance swap to slotsI’d be very happy if we could remove the property, or rather reassign its function to the new slot. 

https://app.weavy.aithe only way i could be 

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.