Report a Problem

Hello Figma Support,Members on our team were automatically upgraded to paid seats without our intention or explicit approval. We would like to request a refund for the newly added seats and have the unintended paid seats removed or downgraded.Invoice ID: SVPHCIIZ-0006Invoice date: July 25, 2026Invoice total: $36.33Please review the automatic seat upgrades and refund the charges associated with the newly added seats. Please also confirm how we can prevent members from being automatically upgraded to paid seats in the future.Thank you.

I’m writing to ask for some advice as I’ve recently run into a couple of frustrating issues while managing our Design System (D.S.). Every time I publish and update, things keep resetting, which makes me honestly afraid to touch any other components. 🥹Here is a summary of the two issues I'm experiencing: 1. GNB Component Properties Resetting to Default Context: About 3–4 months ago, I created a GNB component in our D.S. Figma file, pulled instances into our actual working design files, and set different properties (e.g., Menu A Selected, Menu B Selected) for each screen. Issue: Last week, I made some updates to the GNB in the D.S., published the changes, and updated them in the working files. Surprisingly, all the custom properties I had carefully set per screen reverted back to the D.S. Default! In the past, screen-specific property settings were preserved, but this time everything changed, forcing me to manually reconfigure the properties for every single screen. 2. Token Componen

When auto-keyframe mode is enabled in Figma Motion, property changes made through the Plugin API behave inconsistently:Stroke width (strokeWeight) — changing this via plugin correctly adds a keyframe at the current playhead position  Position (x, y) and Rotation (rotation) — changing these via plugin does NOT add a keyframe, even with auto-keyframe toggled on Steps to reproduce:Enable Motion mode and turn on the auto-keyframe toggle Select a node From a plugin, set node.strokeWeight = someValue → keyframe is added automatically From the same plugin, set node.x = someValue or node.rotation = someValue → no keyframe addedExpected behavior: All property changes made via the Plugin API should respect the auto-keyframe toggle, just like changes made through the UI do.Workaround: Manually call applyManualKeyframeTrack for TRANSLATION_X, TRANSLATION_Y, and ROTATION at the desired time — but this requires knowing the current playhead position, which is also not exposed in the Plugin API (a sep

I need to update my payment details because the “Ship To” and “Bill To” addresses on the receipt must be the same.However, when I tried to use the same Visa card, Figma informed me that the card had been declined.I may have entered the wrong expiration date several times while trying to recall it. In my bank’s app, I could see that Figma had attempted to place a pre-authorization hold, but the bank declined it because the expiration date was incorrect.I later found my physical card and entered the correct expiration date, but Figma still showed that the card had been declined. I contacted my bank manager, who confirmed that the bank had not received any further payment or authorization requests from Figma after that.Could you please check whether there may be an issue or restriction on Figma’s side that is preventing the card from being processed?

I accidentally moved my package.json file while organizing imported images, due to some images glitching back outside the folder. I worked too fast, and moved the package.json into the folder instead.Since then, my preview has been broken and the AI cannot fix the error by itself.Duplicating the Project only recreates the same situation, and the rollback to another version is equally impossible, as I simply get a “unable to restore version”. Another possible solution, which is to open the project with preview disabled and then try to roll back, produced the same results.  Is there a feature for this? Or does it have to be handled by support? I already opened a case, but it appears this takes quite a while.

I have a component (Select Field) that is appearing correctly in the library, however when designers at my org bring it over into their files via the asset panel, it shows up without the actual field- just the title and supporting text. When inspecting the layers, the field layers are not present in the component.Beyond that, when a user pastes in the component directly from the library file, Figma prompts them with an update that incorrectly removes the layers again.Does anyone know what is happening? I have never seen this one before and have no idea how to go about fixing it.

 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?

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