Report a Problem

 I can not see a <Annotate for agent> button on any new created Figma make.

Was the copy link to selection action removed?

The description of changes that is added in the library when publishing is no longer showing in the design files when reviewing updates. The post here mentions the function 🔗.I’m using the desktop app on Mac. Enterprise plan. I followed all steps from the Quick fixes on troubleshooting checklist.I’m not sure if the feature changed or it’s a bug since the new UI, because I noticed that the help article doesn’t mention the description. 

Just got the UI update for Figma’s Desktop client, and Assets tab is now in a completely seperate tab from File. I used to be able to tell at a glance whether there’re updates pending. Now I need to manually click on the Assets tab every. single. time. just to look out for that blue dot.It’s important for me to work with updated components. Lots of projects, lots of libraries.Feels liek a backward change. Like XD.How can I see the blue dot the moment I open a design file?  Or, how can I roll back to the previous UI? 

Apparently, I’m running an online contest and I relied on Figma Motion as the on-screen graphic. Now the way the animation works is that I tend to use preset animations (e.g. opacity, position). For example, a simple text would have an entrance and an exit animation, consist of Opacity + Position > wait > Opacity + Position. There are two Opacity to allow smooth entrance and exit. Now everything works fine, until one day when Figma Motion started to break down. Figma Motion only accept one opacity per element, according to my testing, and only if the animation start at 0s then it will work fine. Delaying the animation will result to the element being exposed before its initial animation. I will also attach a “before everything crashes” video and a “testing crashed” video. I appreciate your attention, and to hope this issue will be fixed asap.

I seem to be getting a weird behaviour when prototyping with components. Noodling a component sometimes refuses to connect up unless using the interactions side menu . Any ideas on what might be causing this?

I think there may be a bug with the horizontal constraints.When I apply the Top and Left constraints, the vertical constraints work as expected. However, the horizontal constraints do not.More specifically, it seems that the Left and Right constraints are reversed: When I select the Right constraint, the element actually behaves as if the Left constraint were applied. The left edge remains fixed, while the right edge moves. Conversely, when I select the Left constraint, it behaves as if the Right constraint were applied. In other words, the horizontal constraint behavior appears to be inverted.Could you please verify whether this is a known issue or a bug in the software?

I reported this issue over a week ago and just received a request for a screen recording.The Bug: The Figma prototype's floating navigation obscures almost 100px of our design, completely hiding our main navigation.The Constraints: Company security policy strictly forbids sharing internal artifacts, screenshots, or screen recordings externally. I cannot provide them.The Impact: I am getting direct complaints from my Product Managers and business stakeholders. We cannot keep using painful workarounds to hide your UI.Please let me know how can I escalate this.

Hi everyone,I’m facing a frustrating issue: multiple Shift-related shortcuts have stopped working in Figma on my desktop.Here are the specific shortcuts that are broken for me: Shift + left click (not working) Ctrl + Shift + R (now is selecting the text like was ENTER before) Shift + Enter (now is renaming the layer for some reason) Ctrl + Shift + < (not working) For context: I have already tried clearing the Figma desktop app cache. The shortcuts are failing across multiple keyboards. I also tried using it on the browser, but I encountered the same issue. I am looking for a working solution or workaround since this severely impacts my workflow. If anyone has experienced this or knows a fix, please let me know. Thanks in advance for the help!

Reporting a false-positive domain block. Signups and logins with @zamana.com are rejected with 'Signups from this email domain are forbidden,' including via Google sign-in. zamana.com is the legitimate corporate domain of Zamana Inc - Google Workspace, valid MX/SPF/DMARC, no disposable/temporary email service.The domain (registered since 2004) was acquired by the company in October 2025; any disposable-email activity predates our ownership. It was first flagged around 2019, years before the company existed.It was on some disposable blocklists under prior ownership but has since been removed from all major ones (IPQualityScore, mailchecker, wesbos, UserCheck, and others). Figma appears to be reading a stale list. Could a Figmate open a ticket to whitelist zamana.com? Happy to provide verification privately.

Hi everyone,I’m trying to determine whether this is a bug, an account-specific issue, or an intentional product change.For the past 1–2 months, my Figma files no longer display the collaborator/viewer indicator in the Share dialog.Previously, when I clicked Share, I could:See how many people were currently viewing the file. See the users who had view access to the file (including non-team members if they had access). Remove people who no longer needed access.Now, the Share dialog only shows entries such as:Anyone → Can view OwnerThe list of users with access and the viewer indicator are no longer visible.I’ve confirmed that:The issue occurs in both the Figma desktop app (macOS) and the browser (Safari). It affects multiple files, not just one. It started approximately 1–2 months ago. Restarting the app, using a different browser, and signing in again did not change the behaviour.I also found another Reddit post from a user describing what appears to be the same issue, where a Figma tea

Opened downgrade + cancel auto-renew ticket #2030321 on 23 July. Got auto-reply. No human contact for 6 days. Charged €3,120 today (invoice 90OZSSU5-0006). Two more tickets today - same auto-reply only. Three open tickets, zero humans. Long-time Org customer. Need billing escalation on #2030321 today. Who can help?

The measurements are not duplicated along with the contents.When elements placed inside a Slot container are measured using Figma’s Measure Tool, duplicating the Slot with all its content or parent frame/component containing the Slot results in the duplicated object losing all measurements. Steps to ReproduceCreate a Component containing a Slot. Place an element inside the Slot. Use Figma's Measure Tool to add measurements directly to the element/frame inside the Slot (Shift+M). Duplicate the parent Frame, Component Instance, or the Slot itself (via Cmd/Ctrl + D or Alt + Drag). Check the duplicated Frame or Slot.Expected BehaviorThe measurements attached to the objects inside the slot should be duplicated along with the slot/frame contents and remain visible on the duplicate.Actual BehaviorThe objects inside the slot are duplicated, but all attached measurements vanish / are not duplicated. The duplicated frame or slot appears without any measurement annotations.Works only in Frames or

 Why getting this error as Figma MCP says for get_screenshot read only access is needed.Figma [get_screenshot]OUTLooks like you don't have edit access to this file. The file owner can share it with you and make you an editor.[Resource link: rate-limits-access.md] file://figma/docs/rate-limits-access.mdFigma Debug UUID: 0256d728-3a1d-4b09-922c-3bbc9a6633f5  

HiI'm trying to publish an update to my plugin "Rennu" (by Yan Bogdanov), and I'm blocked at the final publish step with this message:"We detected a change to your account details. Please contact support@figma.com to proceed."Could you help me understand what change was detected and what I need to do to proceed with publishing? I haven't intentionally changed any account details recently.Plugin name: RennuThanks for your help

Hi everyone - yesterday I ran into a FigmaMake warning when trying to run a prompt telling me "Couldn't summarize chat history, try again later" -- error code: 8cd2987f-7f38-4a23-8dda-797192746e1f -- screenshot below. For context, this happened to me about an hour after a coworker came to me with the same error. They were able to resolve it by duplicating the FigmaMake file and re-running the prompt, however I have tried everything I can find on the webs (which isn’t much) and a lot of other troubleshooting attempts beyond that to see if I can get past it.My last ditch attempt was deleting about 200 .md files from the Imports folder that were attachments from many of my prior prompts. That still didn’t do the trick. I’m at a loss. More context: I’m on version 1248 of the Make file, using the Opus 4.8 model, the prototype is about 18MB with ~600 files.Any and all help is appreciated!! Thanks all

Hi there!We have several Figma components that have their respective components in SwiftUI and Compose linked using Code Connect UI. However, when an AI agent uses the get_code_connect_map Figma MCP tool, it only returns the Android components. If I remove the Android components, only then do I get the linked SwiftUI component back.Have I misconfigured something or is there a bug with the get_code_connect_map tool? Specifying the clientFrameworks and clientLanguages parameters referenced here doesn’t change the result.

I just updated figma to the Figma Desktop App version 126.7.10. Now the plugins are not working. has this happened to anyone else? Is there a fix?

Hi team,We’re running into a really frustrating issue while viewing prototypes in Figma and wanted to see if anyone else is experiencing the same thing.Sometimes while previewing a prototype, the entire Figma prototype panel suddenly shifts completely to the left side of the screen. Once this happens, the view gets stuck — we can’t move or pan the prototype, and all prototype interactions stop working entirely. It basically becomes unusable at that point.What’s strange is that this doesn’t happen consistently at a specific step; it just happens randomly while viewing the prototype. Refreshing doesn’t fix it, and reopening the prototype is the only workaround for now.This issue is happening for multiple people on our team, so it doesn’t seem to be a single machine or account problem. We’ve also noticed that the same prototype works perfectly in Microsoft Edge, but the issue keeps occurring in Chrome and the Figma Desktop App.Attaching a screenshot showing how the panel looks after it sh

I'm experiencing an issue in Figma Prototype mode. When I click on a prototype interaction, then select the pop-up and click on the linked connection, the entire canvas unexpectedly shifts to the left. This makes it difficult to inspect or edit the prototype links, as the viewport keeps moving instead of staying in place.and this issue coming in my account .. and someone working along with me .. it not having issue so it the account issue i am facing 

Today I signed on to find that all of my FigJams that I own across multiple projects under my Education Account, have shifted to View/Comment Only. I went around and around with the Ai support chat and it could not help me with this issue. I have verified that my account is an Educator account, all of the Project files live under that account. The other issue that could be related is that my Share button times out and I cannot review access through that process. This happens on the Desktop Application as well as through the Browser. Any help would be wonderful!

 Hi Figma team, I got access to the Figma Agent beta recently and honestly I was really happy about it. Used it for the first two days, no issues at all. I thought finally, something that actually feels useful in my workflow. But from day three, every single attempt threw an error. A redbox with some numbers and a "something went wrong, try again" message. I tried multiple times thinking it was a one-time glitch but it kept happening every single time.So I figured maybe it's a cache issue or something on my end. I cleared everything, fully quit Figma, and reopened it. That's when things got worse. The Agents tab in the sidebar was just gone. Not just the on-canvas stuff, the entire thing. Sidebar icon, agent interface, all of it. Like it never existed. I'm on a Professional plan with a Full seat and the files I was using are under the same team that had access. Everything checks out on my end.I really want this back. Could someone check on the backend if my access got revoked or rolled

We can open this file: https://www.figma.com/design/NHx43wUY5QouROSxyaePAi/Webpage-UI--Appventurez--Inner-pages-?node-id=1305-6868&p=f&t=4J0wrfLp5zOtbFXD-0 and comments are visible, but the design itself shows as a black screen. This is happening for multiple team members, not just one person. We checked Trash and there is nothing there. We are using Mac. Please help us confirm whether this is a rendering issue, file issue, or permission issue.

I converted my header into code so that it will follow any viewports’ screen size. However, there’s a space between the header and my next section that I can’t remove. I tried using the AI to help me remove it but it’s not disappearing. It looks fine on my workspace but it appears when I preview and it’s also present in my published website. Any ideas how to remove it? How it looks on my workspace​​​​​ How it looks when I previewOther notes: Header and the next section has 0 padding and margin It still happens when I hide the next section (still a gap between the header and the footer) which leads me to believe the problem is in the footer I’d also appreciate if you guys know any other methods to make a frame fullscreen for any viewport size. Thanks! 

Everywhere I am seeing the release of the AI agent in Figma and how easy it is to use. In our paid organisation subscription it appears that it is not available. I am admin and can not figure out why this feature is not available. When and how can we access this?