Report a Problem

Hello,I would like to request a refund for a recent subscription charge on my account.I did not intend to continue the subscription, but it was automatically renewed and charged. Since I do not wish to use the subscription, I kindly ask for your understanding and request a refund.I would greatly appreciate it if you could review my case and consider making an exception.Thank you for your time and support.I look forward to your response.

I have the primitives component and when I update color of it and then there're no any update on the component. This is really big bug and make the Design System to become useless in the consistency context. This is the component before it is overwroteThis is the component after it is overwrote and I have updated the color in the master component. The color of the icon has been change to white but it was not updated in the component.  

I’ve been STUCK with this icon override issue for a week now and need help 🙃Context: I have an icon library structured as so:    In my button component, I’m using instances of this icon component and I’m applying specific tokens to override the default icon color.  What’s working: Switching between icon variants (same size, e.g. 24px → 24px) works as expected The icon correctly inherits the color token from the button The issue: When switching icon sizes (e.g. 24px → 16px), the icon resets to its default color It overrides the token that was being applied from the button This breaks the expected “inherit color” behavior What I’ve checked/tried: Verified layer structure is consistent across icons Confirmed the token is applied at the button level (not hardcoded on the icon) Instances behave correctly until the size variant changes Question:Is this expected behavior when swapping component instances across different sizes?Or is there a recommended way to structure icon compo

 IT appears to me that radial gradients in figma and the browser are rendered differently - or alternatively there is something wrong with the css parameters figma spits out.Have a look at the following screenshot:Left: Figma - Right: chrome/cssThis is a 272x56 rectangle, filled by a gradient.In figma defined like this:which in dev-mode spits out the code:background: radial-gradient(183.69% 86.67% at 30.59% 81.58%, #FFF 0%, rgba(255, 255, 255, 0.00) 100%);The that radial gradient in the web version clearly looks like it has a very different aspect-ratio (a lot wider, while in figma it appears almost circular)

 This popup does not go away. I have answered this question in every way possible and it keeps returning. Please turn it off. It is not clear what this is even referring to. My design? The Figma App design? Something else?

Hi, I encountered an issue while using the Figma desktop application where the Undo function intermittently stops working.After investigating, I found that the problem seems to be triggered by interacting with guides (rulers). Here are the steps to reproduce:Steps to reproduce: Perform several actions on the canvas Move or adjust a guide (ruler) Perform additional actions Start using Undo (Ctrl/Cmd + Z) Expected behavior:Undo should continue reverting actions step by step, including actions performed after moving a guide.Actual behavior:Undo works normally until it reaches the point where the guide was moved. At that stage, Undo stops functioning entirely and does not revert any further actions.Workaround:Disabling guides using Shift + R restores the Undo functionality.Additional notes:The issue appears specifically linked to guide interaction, as Undo behaves normally otherwise.

You can describe the issue as: "fast_apply_tool reporting success but not actually applying file changes, requiring multiple attempts for the same fix" The specific error pattern was: fixing JSX syntax onNavigateToNearest(() => to onNavigateToNearest={() => required multiple tool calls despite success messagesI have been using hours and Figma Make is fixing the same problem over and over again

I immediately hit the AI Credit  “limit” as soon as Figma started measuring yesterday. (hooray for the drug dealer approach to new feature releases). I purchased an additional amount of credits, they show as available, but i am still unable to use figma make to continue design and development work. This is a huge problem for my project and deadlines. Naturally, the “AI” support was completely unhelpful, and no one has responded to my support ticket in over 12 hours. This really doesn’t impress me as an enterprise-grade tool. Poor functionality, even worse support. I’ll just be here, paying for a product that doesn’t work, missing deadlines, and waiting around for figma to dignify me with a response. 

 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. 

FIGMA huina nichego ne rabotaet ja corner radius na 200 stawlu a on ne okruglaet ja sun presedenta ja skroju washu FIGMU i eshe osushdaju sa naswanie na nemeckom eto tipo FIG tipo tu da suda na balkionne ou ez a Ma eto mama.             SOHN VOM PRESIDENT   BEZ OBID MNE PROSTO NECHEGO DELAT 

Hi Team,I am facing persistent issues while working on my Figma Make file and need your guidance.Any changes made via prompts are not being reflected in the file. The file frequently crashes, and the preview does not load at all. I also noticed that some dropdown fields work correctly when the same link is opened using another Figma login, but they do not work when I open the same link from my account.I have been facing the prompt‑related issue for the last three days, and despite multiple attempts, the preview is still not loading or reflecting the latest changes.Could you please help me understand what might be causing this issue and suggest how I can resolve it?Thanks in advance for your support.Best regards,Richa

Figma has restricted you from sharing this file  

Hello! I have a ton of my work in it and the file is very important to my work. I hope you could help me retrieve it.

My entire team isn’t receiving any verification mails and we haven’t heard anything from support. We can’t use Figma

I am creating a website using “Figma Sites” and I placed a video which only start auto playing on the mobile browser, but on the desktop browser, it does not autoplay no matter what video format or file size or compression method I use. (it only starts playing in the desktop browser if the playback controls are showing and you press play)  

I recently purchased a subscription on my Figma account: Current account email: [redacted] Date of purchase: 20.03.2026 I would like to transfer this subscription to a different Figma account: New account email: [redacted] Could you please assist with moving the subscription, so that I can use it on my new account?Thank you very much for your help!

I am using a robust design system and token library with components that have variants for different states like active, hover, error etc. Our token library has theming for light and dark mode. I would describe our design system as robust and well made using best practices for a mid sized to large design system.I have exported the library for make and the library appears as an option when designing with Make. My issues is that the designs it creates do not resemble our design system. The text input components we use are similar to default Material 3 text fields. The designs created sometimes use a Material UI style but it uses outlined inputs or inputs with detached labels. The colors are sometimes close but it seems truly coincidental and not related to our actual token library.In fact after testing and prodding I see no difference in using our design system library and using no reference. My suspicion is that it simply does not understand our library and is moving forward with defaul

DO NOT use “Slots” after annotations are implemented !Problem Reproduction: (The actual use case is to design a "Grid Cell" type component to configure a table as desired. Component A: the editable content, Component B: the table cell, Component C: a variant component to manage the cell's normal and focus states.)1- First, create an autolayout component (A) with text. Add a “text property” to the text.2- Nest instance (A) within an autolayout component (B). Add a “swap instance property” to component (A) so that it can be swapped by any other component.3- Nest instance (B) within an autolayout component (C). An instance (C) should then be able to display the added editable properties (text and swap instance).To reproduce the problem and make it simple, there's no need to transform component (C) into a variant to fit my use case example.4- Next, let's assume we previously documented our component (C): add two "measurement" annotations to identify two random padding elements (not on inta

This is the SECOND type Figma just decided to WIPE a tsx file and then decides to restore it and use 300+ credits for it (AND the stupid “Continue” loops to add). This is unfair and frustrating - I worked on it for DAYS and then Figma messes it up. 

When exporting SVG to Vector drawable, the effects shown in Figma aren’t supported, and all effects are lost. The error appears for:<filter> <feFlood> <feBlend> <feTurbulence> <feDisplacementMap> <feMerge> <feMergeNode>

I added a slot in an accordion like component. Added padding to that slot in the instance. When I play the prototype, the values are not respected and no padding is shown.  

Figma Support, I just found out my Figma account [redacted by forum moderator to remove PII] that I have been using for months without any problems, was suddenly suspended as I was trying to log into it today. The error message says:“Signups from this email domain are forbidden. Please use an email on another domain.” I can understand blacklisting domains for new signups, but for an existing account!! All my files are now gone just like that, seriously?! Why did no one give me a heads up to change the email domain, not instanlty suspend me?!! Now I had to make this new account just to send you this. Unbelievable. Liam

Hi all 😀Our team has been tickering with the new Slots feature, and we love it a lot.We really try to keep everything detailed whenever we can, and we were overjoyed to see that each Slot property can get their own individual description on “How to use this slot”, just like the Components do. However, while the components description preview is truncated if it is too lenghty but clickable to display the whole text, the Slots description isn’t clickable, and there’s no way to read the whole documentation.Is this an oversight or is this the intended behavior? 

Drag-and-drop into the Figma Make code/file explorer used to work for me a few days ago. I could drag .tsx files directly from my computer into the Make file system. Now I can no longer drag even a very small file. I am not talking about attaching files in chat/prompt — I mean direct file import into the Make code/file explorer. Has this been removed, or is this a regression?