Share Your Feedback

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

错误：无法复制粘贴 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.

Hey There - your ‘squares’ in Figjam are not squares, but squares with rounded corners and not quite squirkles. For all of us who know what they’re doing, please provide full control over all objects so we can create in the way that is needed. Thanks

At the moment, as far as I’m aware, the only keyboard shortcut for switching between different UI modes in Figma Design is ⇧ + D. This toggles between Design and Dev Mode. Where it starts to feel odd is if you’re in Draw or Motion and hit ⇧ + D, it brings you to Dev Mode. If you hit it again, you’re now in Design mode with no keyboard shortcut to switch back to your previously active mode.However, you can switch to Draw via the actions menu, but there is no keyboard shortcut. There is no option to switch to Motion via the actions menu.I propose adding dedicated shortcuts for each mode. Possible shortcut options:Design: ⇧ + ⎋ Escape Draw: ⇧ + W Motion: ⇧ + J or ⇧ + O Dev Mode: ⇧ + D (keep existing shortcut) Cycle mode forward: ⇧ + ~ Cycle mode backward: ⇧ + ~I also think all of these should be added to the actions menu as well. Even better, customizable shortcuts for any actions menu command would be amazing.

Ew. No. 

In Figma Make when chatting to the AI and writing bullet points, I expect hitting Enter to create a new bullet point, but it sends my incomplete chat to the agent, wasting me time and credits.

I would love it if we had a way to export multiple PDF pages as an export option. Do we have that option here in Figma? If not, that would be awesome if we did!

Hi! I’ve been testing figma motion and I noticed the preview is always at 60fps or more, not really sure, but there is no way to change the preview to something else, I would need to be exporting the video at 30fps or 24fps everytime I want to check on animation  timing. Any way to change that or is it something for an upcoming update?

"Please add support for fully custom workspaces in Figma, similar to Adobe Illustrator or Photoshop. Users should be able to move, dock, and save custom panel layouts to fit their personal workflow and make designing easier."

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.

Je suis assez déçu de Figma ces dernières semaines/mois.Beaucoup de mises à jour qui changent la prise en main des habitudes. Pas grand chose mais chercher tous les 3 jours ce que l’on a l’habitude d’utiliser c’est exaspérant.Sans parler des regressions en chaine sur les slots, le comportement des autolayouts, les ratios qui recommencent à se comporter n’importe comment alors que c’était devenu un super outils.On sent bien que vous êtes en train débattre contre l’arrivée des iA mais s’il vous plait. Continuer de proposer un soft de qualité.

When working with variables it is really annoying that the Variables window closes on esc. I want to dismiss sample color or selecting another color from my styles as examples, but instead it closes the Variables window.

With the latest UI panels updates, I now lost the ability to directly select a HEX value straight from the Fill layer. A huge downgrade, now I need to open the color panel, switch from HSB (that I use frequently) to HEX, and copy from there. Please bring back direct input field in the Fill layers to have ability copy color value directly.