Report a Problem

My Designs are Under Review from 2 days. Why ? Can you please upload them to Figma Community in normal way it was uploaded. Yesterday I try to upload a new design to Figma Community it says contact Figma support. 

I'm getting an error when calling figma.getNodeById, even though all functions in my plugin have been updated to async. The plugin works perfectly in my local environment and my manifest includes "documentAccess": "dynamic-page"), but the error only appears in the published version. The code.js in the dist folder is definitely using lastest build with the async functions. I've tried republishing multiple times, so it feels like a publishing issue,  almost as if Figma is still serving an older build.The full error is: Error: in getNodeById: Cannot call with documentAccess: dynamic-page. Use figma.getNodeByIdAsync instead. at <anonymous> (PLUGIN_1559_SOURCE:217:47)this is the plugin: https://www.figma.com/community/plugin/1137823695947414493/quick-table

We had a disgruntled employee permanently delete the majority of our files. I was working with a customer support person on Friday but they logged off for the day before it was resolved. He restored some files that were deleted but none of our primary ones were restored. This is urgent for my organization and represents years of work. Can someone jump on this issue ASAP to help me finish the process? The ticket number is: 1781840

I noticed that my Figma app hasn’t received some of the recent updates such as new left navigation bar and Slots for components.I’m using the desktop app, and I also tried installing the beta version, but the features still don’t appear in either version.To troubleshoot, I also reinstalled the application, but the issue remains the same.Are these updates still being rolled out gradually, or could this be related to account permissions, region, or workspace settings?Thanks in advance for your help! The actual left bar  No new UI in the help section 

I have a design system that I published as a library. I’m consuming this library in another file for a slide show. Up until now, I never got an error when trying to access variants in the slide show file. But as of today, I am getting this message for a seemingly random assortment of instances: “The properties and values of this variant are conflicting. Change the applied values on this variant to resolve this.” I don’t get this error when interacting with variants inside the authoring file.  I looked up this error message on the Figma forum, and it says it appears when Figma detects that two variants are identical, regardless of whatever they’re named. But in my case, the variants are absolutely not identical. They have many differences in names and values and they have never produced this error either on the authoring or the consuming side until now.  I saw that Figma dropped the “Slo

I’m seeing a mismatch between SVGs returned through Figma MCP and SVGs exported directly from the Figma UI.What I expectedWhen I request a vector/component asset through MCP, I expected the SVG export to preserve the same export box/canvas as the original Figma component/frame export.What happens insteadThe SVG asset returned through MCP appears to be tightly cropped to the inner vector path bounds, while the direct SVG export from Figma keeps the full component canvas.Concrete exampleI have an alphabet component where each letter is designed inside a 42x42 frame/component.the MCP asset is cropped to the actual stroke bounds the direct Figma export preserves the full 42x42 canvas and empty space/paddingWhy this mattersThis breaks 1:1 implementation workflows when layout depends on the original component export box. In my case, letters are

I can’t send my changes in inline "edit with prompt", and the chat doesn’t see elements that I select.the bug video

Greetings , I would like to know why Figma company are trying to take funds from my bank account, although I cancelled my subscription and deleted my credit card from my Figma account can you please stop trying to take funds from me because my cancelation was 1-2 weeks before my subscription ends, and thank you. 

Hello Figma Support,I am trying to recover access to a Figma account that was registered with the email address [redacted by moderator to remove personal information].The problem is that the company no longer exists, and the synapse.company domain is no longer active, so I cannot receive any verification emails or use that mailbox to log in.I would like to ask whether it is possible to restore access to this account or transfer it to a new email address: [redacted by moderator to remove personal information]I can provide any information needed to verify ownership of the account, such as: the old email address; the account name or profile details; billing or subscription information, if available; any other details that may help confirm that the account belongs to me.

Hey. When I open my project it is not loading. The app details in terms of the prompts I put in are available and I can see them on the left side but the app itself and everything I have created so far seems to be gone. There is a notification on the screen that says ‘I couldn’t solve this one. Ask Figma to fix it.’ Even the preview panel in the drafts no longer shows anything. It looks blank. Here is the link:  

When using get_design_context on a parent component that contains and exposes a nested component instance’s property, the nested component's variant props are not surfaced in the parent's generated props. The nested component is inlined with only a className prop, regardless of what properties the nested component has. Steps to reproduceCreate a component with a boolean variant (e.g., ChildComponent with isActive: true | false) Create a parent component that nests an instance of ChildComponent Expose the properties from the nested ChildComponent Call get_design_context on the parent component set Expected: Parent component props include a way to pass through the nested component's isActive prop, or the inline child function includes its variant props. Ac

Whenever I use the Glass Effect, I encounter the same problem. I create a frame, fill it with a color, and adjust the opacity. However, unwanted lines start appearing, even if I convert the frame into a component. This issue occurs every time, and I would like to understand the reason behind it and how to fix it.

Hello,I’m trying to enable Gemini 3 Pro in Figma Make, but the “Experimental models” section isn’t showing up in my Settings menu. I’m using a education account. I checked in both the browser and desktop app. I’m working inside a Figma Make file, not a regular design file. My admin has enabled AI features for our team. I’ve refreshed the page and restarted Figma, but the Experimental models toggle still doesn’t appear. Is this feature being rolled out slowly, or is there something I need to adjust in my workspace or team settings? Any advice would be appreciated! Thank you.

Hello,I’ve upgraded my seat to developer and re-authenticated in Claude Code to the Figma MCP server. But I still get rate limited on the very first call. According to the table I should get at least 10 calls per minute.Annoying paying money for the pay wall, results in the same pay wall.

.

I just published the library but I don’t have the option to export. After clicking publish, I went back into my assets tab and saw that the option to “publish” appears again...so I tried clicking on it but then the new window I have unchanged components (which is true) and the blue publish button is greyed out. Is this a bug of some sort? I tried closing out of Figma entirely a few times and that still didn’t work. Over in the Figma Make tab, it doesn’t acknowledge the library at all.(I’m not on an edu. account but a company account) Thank you!

Hello, my friend and I made a D&D adventure inside of Figma for a class project. We had some major issues with it at the end. There are a lot of frames, like 120ish. We’re in college and are on the student account versions.We’ve had some problems with stuttering inside the frames and some animations being cancelled out. But those aren’t the major problem. My major problem is this weird error in my prototyping links that I cannot understand. Every prototyping variable for all the frames work perfectly fine except those. (That I know)When you die in the Boss fight against the Primordial you get the death scene from the Crab fight. At first I thought it was something to do with the Flow Chart order or specifically with the Crab frames. But the Bug fight against the big mantis gives you the death scene from the Snakeman fight. I cannot figure out why this is. I have gone through and removed the death scene transitions for both the Boss and Bug fights, but the

Locked layers cannot be selected from the canvas but are still selected using the “Select All with Same...” . So I am not sure how to select all the layers with a certain e.g. Fill but only change the color of the unlocked ones. Am I the first one to think/stumble on this?

This just happened.We were using slot beta. The library file has slots in the component, and now when we publishing the library, the slots revert back to normal container in the other files, and shows component error.The file updates resets tons of designs we already laid out!

 I have created a frame inside a main component but i don't see the slots feature when i right lick the frame which is inside the main component. 

Hi everyone, I have this PAINFUL BUG! that is killing my work flow.I’m super used to use [ , ] , cmd + [ , cmd + ] to move objects / groups / etc arround.On my personal computer they work as intended, but on my work computer 3 of 4 of em work.the CMD + [ for some reason that I cant wrap my head around is triggering the Text > Adjust > Decrease IndentationI’m totally clueless why this is happening.Here is my keyboard shortcuts layout on figma and on the mac.PLZ help me out to find a way to fix this, those shortcuts are kinda the bread and butter of my workflow! 

Here is the forum post with the full technical section added:Title: Branch merge broke all component instances across all working files — conflict error on every instance, restore & republish did not helpHey Figma Community,I'm dealing with a critical issue and would really appreciate any help or shared experience.What happened: I merged a branch back into my main library file (we work with a large design system, 100+ components). The branch only contained changes to one component (Segmented Control). After merging and publishing, every single component instance across all consumer/working files now shows this error:"The properties and values of this variant are conflicting. Change the applied values on this variant to resolve this."This affects every component — not just the one I worked on.What I've already tried:Restored the library to mult

I’ve created a simple CMS collection and added a CMS list to my site’s homepage. When clicking into either of the CMS items (labeled case studies), the page loads but none of the CMS content. I have to manually refresh the page and only then content loads. When I inspect the page, the content is there, it’s just not being displayed.Furthermore when a user is on a CMS item page, and attempts to click the logo in the nav bar to access the homepage, the CMS list that loads only displays a single item listing (which doesn't retain styling , nor imagery). Can someone help figure out how to resolve?

Description: Hi everyone, I’m experiencing a frustrating issue with Figma’s AI features and I’m hoping someone here can help.I used Figma’s AI to generate a complete dashboard layout. It worked great — I even asked the AI to create additional sections that I could later fill with data. Everything looked correct while I was working on it.However, after I published the file, all of the AI‑generated sections I added later suddenly disappeared. The main dashboard is still there, but the extra areas I created with AI are completely gone.This means I’ve lost several hours of work, and I can’t figure out how to restore those sections. I’ve already checked version history, but I can’t see the missing elements there either.Has anyone experienced this before? Is there a way to recover AI‑generated content after publishing? Any advice or workaround would be greatly appreciated.Thanks in advance!