Report a Problem

Hello! My name is Maria Luiza and I signed up for SIGMA a month ago to do a final project for college.I signed up for the $5 plan because it was only for one job; my intention was to continue with Sigma for maybe another two months just to get to know its features.But today I received a charge of $35 on my credit card, I didn't understand it and saw that I was enrolled in a Premium subscription, which totaled $35.I would like to understand at what point this change of plan occurred, as I haven't accessed Figma since the academic work.I would like to say that the $5 plan was extremely clear about the price, but at no point was there a clear explanation of any additional charges without apparent reason. Please contact me by email [redacted]

I ran a moderated usability test this week using a prototype published via Figma Make's. On my own screen, everything displayed correctly during the session. However, one of the test participants experienced rendering issues on several screens: some elements showed incorrect/unrelated labels, and text was cut off in places.I wasn't able to reproduce the issue on my end, and a search through the community forum didn't turn up an exact match, though I found related reports about font-loading issues and Auto Layout/clip-content rendering differences between Design and Prototype mode. But since I built everything with figma make i'm not sure that's the case.Participant's environment:Browser: Google Chrome OS: WindowsQuestions for the team:Could this be related to font loading on the viewer's device? Is there a way to "embed" fonts so they render consistently for all viewers, regardless of local font availability?

Variant layer names in the format Prop=Value (e.g., State=Selected) work correctly and are reflected in the "Current variant" panel. However, simply clicking into the layer name field to select/focus it — with no actual edit — and then clicking away causes Figma to throw:"This layer has an invalid name. Make sure that all variant names are of the form: Prop=Value, Prop=Value, …"After this happens, the "Current variant" panel's State dropdown shows "—" (empty/unset) instead of the correct value.Steps to reproduce:Open a component set with a variant layer named in valid format, e.g., State=Selected (property recognized correctly, shown in Current variant panel as State: Selected). Click on the layer name in the Layers panel to select/focus it (do not type or change anything). Click away, back onto the canvas. Error appears: "This layer has an invalid name…" and the Current variant panel now shows State: "—".Expected behavior:Clicking into a layer name field without making changes should

Hi,I’m experiencing a strange account-specific access issue and would appreciate some guidance from the Figma team.Yesterday I suddenly lost access to two design files that I created myself.I use only one Figma account and I’m logged into the correct email address. One of the files was actively edited just before the issue occurred. Both files now show “Request access to this Design file.” They no longer appear in Recents and are not in Trash. My other shared files still work normally. The same issue occurs both in the desktop app and in the browser.I didn’t change ownership, move the files, or modify any permissions.Is there any way for the Figma team to check which workspace currently owns these files or what might have caused my account to lose access?

On Figma desktop the option to create a frame seems to have disappear.  

在使用 Figma Make 的 Make Kits 功能，基于「Meta Horizon OS UI Set」这套 Community 组件库创建设计系统套件（Design System Kit）的过程中，连续遇到了 4 类问题，具体如下：初始化生成的代码中，英文关键字 export 被替换成中文「导出」，导致代码语法错误、预览崩溃Guidelines 相关的 5 个文档（Guidelines.md / setup.md / styles.md / tokens.md / components.md）反复陷入「占位符循环」，一操作就报错AI 明确汇报「五个文件均已写入真实内容」，但实际逐一打开文件核实后，全部仍是系统默认的占位符模板，内容未发生任何变化在多轮「Fix for me」修复尝试后，错误数量不降反升，从最初的语法错误发展到最新一次出现 5 处新错误综合以上情况，判断该 Kit 在当前状态下已不具备继续排查、修复的性价比，遂决定放弃该 Kit 实例，并提交本反馈。

For this week I tried coping a group of text styles and colour styles from a file but i always get the”Copy Failed. Your selection might be too large for the clipboard”  error so i tried it for a single text style and the same error was displayed and i did the same for a single colour style and i still couldn’t copy the stylethis is a huge problem for me can anyone help me with a fix for it?

Can you please do something about the broken dashed strokes? I made nice dashed stroke in Figma make but when I export it in my design, it’s broken. And it’s always like this - when I create one directly in design or import an svg stroke… It’s really annoying :(Figma make: Exported in design:  

When rearranging components with slots i.e moving them from section to another removes properties from those slot layers. In the error toast, when I click “undo” it moves it back into it’s original section.Is this the intended behaviour for slots - if so what purpose does it serve? 

I'm experiencing an issue with the Figma Desktop App where images are not loading properly.When I open a Figma file, images remain as gray placeholders and do not load. The issue continues even after waiting for several minutes, which prevents me from properly viewing and editing my designs.I noticed an unusual behavior: when I connect to a VPN, the images immediately start loading and appear correctly again. Without a VPN connection, the images fail to load and remain as gray placeholders.Details:Platform: Windows Desktop App Issue: Images stay as gray placeholders and do not render. Internet connection is stable. Restarting the app did not resolve the issue. The problem occurs without VPN but works normally when VPN is enabled.This makes me suspect there may be a network, routing, or connection issue affecting Figma's image servers in my region/network.Could you please help me identify the cause and provide a solution? I can provide screenshots, logs, or any additional information if

I have a design library with styles, tokens, variables, components etc all set up and published.I’m trying to use this to create a kit in Figma Make but when I choose the design library, when I click in the components folder, it says ‘no components were extracted from this library’ and I don’t know why.

Hello Figma Support,I am writing to request a full refund for my recent subscription upgrade.I upgraded to Professional on 7/21/2026 (today) with the goal of exporting production-ready design assets for a web development project. However, after using the product, I found that the exported SVGs were not optimized for web use and required the same manual cleanup I was already doing without a paid plan. For my workflow, the paid features did not provide the value I expected.I have not used the premium features extensively and would like to cancel my subscription and receive a refund if possible.My account email is: [redacted PII - DJV 02/21/2026]Thank you for your time and assistance.Best regards, April Itriago

Hi,We are currently migrating our company email domain from @brainr.co to @brainr.com and would like to understand the recommended process for updating the email address(es) on our account(s).Could you advise on the following:Is it possible to update the email address directly on the existing account, or does a new account need to be created? If the account was created via Google SSO, is there a specific process to follow to avoid losing data or history? Is this something we can do self-serve, or does it require assistance from your support team? Are there any steps we should take before making the change to ensure a smooth transition?Thank you,

Every time when I open figma it shows me an error of “Possible network issues detected”, because of this error I am not able to see figma make preview generated by make. 

Hi Figma Support Team, I would like to request a refund for the recent subscription charge on my account. I initially subscribed and paid only for the first month. However, I was not aware that the subscription would automatically renew, and I recently discovered that my account had been charged again. More surprisingly, the amount charged was significantly higher than I expected. I have not used Figma at all during this renewed subscription period, and as soon as I noticed the charge, I immediately canceled the subscription.Given that the subscription was not used and was canceled promptly after I became aware of the charge, I would sincerely appreciate it if you could review my case and consider issuing a refund. Thank you for your time and understanding. I look forward to your response. Kind regards, 

Hello Figma Support team,I've identified a reliably reproducible bug in my design system library: every time I double-click a variant in the left panel to edit it a second time, the variant name breaks.The Prop=Value, Prop=Value name format (e.g. Type=Regular, State=Default) gets overwritten and replaced with just the values, without the property names (e.g. Regular, Default). The right-hand panel then shows "This layer has an invalid name" and the property dropdowns switch to "—".I tested this on 2 component sets to confirm reproducibility before risking further damage across the rest of the library — the bug happens consistently, so I consider my entire library at risk if I continue editing variants normally.Steps to reproduce:Open an existing component set with variants already correctly named (Prop=Value, Prop=Value) Double-click a variant's name in the layers panel to edit it a second time The name gets overwritten automaticallyWhat I need:Confirmation/fix for this bug before I co

Hello,I need help recovering missing content from a Figma Design file.On July 22, 2026, at approximately 11:40 AM, my internet connection became unstable and Figma froze while I was editing the file. During the freeze, all objects and frames disappeared from the page named “новый душ”.Figma showed an option to undo the deletion, but the application was frozen, so I could not click it. After reloading the file, the objects were still missing and Undo no longer worked.The relevant checkpoint is visible in Version History, but I cannot restore it because it is older than 30 days and the file is on the Starter plan.The exact error message is:“Failed to restore file checkpoint via Sinatra API: HTTP API error (endpoint: RestoreFileCheckpoint, response: ApiResponse { status_code: 400, message: ‘Please upgrade to a paid team to get access to history beyond 30 days.’ })”The missing content is not on another page, and the recent versions do not contain it. This was not an intentional deletion; i

Hello,I would like to inquire about my recent credit usage.Previously, I typically used around 1,000 credits over approximately five days. However, after upgrading my plan, I consumed 2,000 credits in just two hours, which seems highly unusual.Could you please help me understand:How credits are calculated and consumed? Why my credits were depleted so quickly? Whether it is possible to review or roll back the credit usage if there was an unexpected issue? Whether there are any best practices or settings to help reduce credit consumption?I upgraded to the highest plan because I intend to continue using your service, so I would greatly appreciate any guidance on how to manage my credit usage more efficiently.Thank you in advance for your assistance.

Figma Motion is a great feature, and I know it's still in beta. However, please fix this issue the current time input box overlaps other UI elements, which affects usability.

Hi Figma Support Team,I hope you’re doing well.I’m currently facing an issue while trying to add more credits to my Figma account. Despite multiple attempts, I’m unable to complete the process successfully.Could you please help me understand why this is happening and guide me on how to resolve it? Let me know if you need any additional details from my side.Looking forward to your support.

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.

Hello Figma Team,I recently noticed that recurring subscription fees have been charged to this account by mistake. I accidentally upgraded/created a paid plan and have not intentionally used the paid features during this period.Please review the payment history associated and help me process a refund for the unintended charges.Thank you for your support.

When a component’s location is changed to another page within the same file, annotations previously attached to that component disappear from view.After the move, the previous annotation only becomes partially visible while adding a new annotation to the same component and the new annotation popover is opened. Even then, the previous annotation is not clickable or editable in any way; it appears but cannot be accessed or modified until adding new annotation action is completed.Is there a workaround to reach the content of previous annotations without adding another annotation, or to keep them fully functional after moving a component to another page?Any guidance would be appreciated.

(screenshot redacted by the moderator due to PII)I changed the seat as you instructed, so why are you still saying the same thing and not processing my refund? Why are you replying without even checking my account?Please refund me immediately.

We are experiencing the same issue with SF Pro.In our case, SF Pro is uploaded to our Figma Organization Fonts, so everyone should be using the same cloud-hosted font files. This means that a mismatch between different locally installed font versions is unlikely to be the cause.The letter spacing becomes visually tighter than expected, even though the font, font weight, text style, and letter-spacing values remain unchanged. The text can appear different after selecting the layer or entering text-edit mode.We experienced essentially the same issue a couple of years ago. It was later fixed, but it appears to have returned during the past two weeks.We have not changed our typography setup, text styles, font files, or the way the font is distributed for several years. The issue started appearing again without any changes on our side, so this looks like a regression in Figma’s text rendering or layout caching rather than a problem with the font itself.Could the Figma team investigate this