Report a Problem

We’re seeing a recurring issue in Figma where files get stuck in a constant “syncing” state and fail to properly save changes. This creates several workflow blockers: Severe lag while working — interactions become slow or unresponsive during sync. Unable to close the browser tab — Figma prevents closing due to “unsaved changes,” even when everything should be saved. Version history overload — the system generates excessive versions because of the repeated auto-sync attempts, making the file history cluttered and harder to audit. As a design system designer managing component libraries, this issue becomes especially problematic. It interrupts handoffs, slows down updates to shared components, and increases the chance of file conflicts or outdated states being published. It directly impacts our ability to deliver high-quality, timely component updates.Requesting investigation into: Why files remain stuck in the syncing state Whether autosave is failing silently How version creati

Hello Figma Support,We recently transferred part of our Figma projects to the new workspace. We noticed that around 100 files still show the previous owner as: user@company1.comHowever, when we open the sharing settings and check “Anyone in [project name]”, we can also see the owner/account listed as: user@company2.comWe want to make sure we handle this correctly and avoid making any files ownerless or inaccessible. Could you please advise on the fastest and safest way to transfer ownership of these files from user@company1.com to user@company2.com?Specifically, we would like to understand:Is there a way to bulk transfer ownership for approximately 100 files?Can this be done through the Admin Console, or does Figma Support need to perform the transfer? Would removing or deleting user@company1.com from the organization automatically transfer ownership, or would the files become ownerless?Is the project-level owner shown under “Anyone in [project name]” enough to ensure the files are saf

I created an app with Figma Make and I'm trying to select an element inside a container with the pointer tool. However, because there's a shimmer effect layer over the container, I can't select any of the objects underneath, only this shimmer layer. How do I select the elements inside / beneath it?

I cant access Figma Agent. My figma app dont update to the latest version.

Hi everyone,for some time now my exports from Figma look noticeably blurry/pixelated.The canvas preview looks perfectly sharp, but the exported PNG/JPG does not.This happens across different files and export sizes (e.g. 1200×628, social assets).Has anyone experienced this recently? Could this be a rendering or export bug?Appreciate any insights.

Figma's MCP is incredibly difficult to use. Calling Figma MCP with ClaudeCode takes an extremely long time and consumes a lot of tokens when generating design files, and the generated quality is also low. All my design systems are actually based on Figma, and now I have to explore new design software such as Apple Pencil, Claude Design, and Open Design, migrating component assets elsewhere. It's heartbreaking. Figma could definitely be better than any other design tool; it's just really hard to use right now, and in the team's exploration of AI workflows, designers are forced to migrate assets.

Hi Figma Team, I kindly request that you provide your Certificates of Tax Residence for the 2026 for the purposes of tax reporting in Poland.These certificates are necessary to ensure proper withholding tax compliance and to fulfill our reporting obligations to the Polish tax authorities.I would appreciate it if you could send the documents in PDF format at your earliest convenience.Please let me know if any further information or documentation is required from my side.Thank you in advance for your assistance.Best regards,

한국시간으로 새벽 3시32분에16.32달러가 갑자기 결제됐습니다. 플랜구독취소도 했어서 무료 플랜으로 되어있는데  왜ㅜ결제된건지 모르겠네요.바로 환불부탁드립니다.

How do I export a Make file to Figma Design for FlutterFlow import?"

Using Figma Make for a long time now and for the first time it took all credits left in the account, but did not output any result. The prompt was optimized with Codex in PDF document, as usual, and did not demand major changes or creative work, just Design style change for existing page with no functionality change.How to get back these credits, if there is no result?How to avoid such mistakes from Figma Make in future?

요금제에 문제가 생겨 갖가지 방법으로 문의를 남기고 이메일을 보내도답변 없이 상담을 종결시키고있습니다.

I am experiencing a bug with the point and edit feature in Figma Make. I can select an element, but as soon as I try to move my cursor to the edit toolbar, the toolbar disappears and I can’t interact with it. This is happening both in the desktop app (MacOS) and on my browser (Firefox). 

Hi! I don’t know why, but I see notification about restricting file sharing option. Can anubody help me with this problem and remove the restriction - or at least explain why it has appeared and what to do with it.Best,Wojtek

I did downgrade of the version but it keeps send a message of the payments. I don't want the figma anymore. Solve my subscription problem ASAP.

Hello, the last invoice payment was not processed because another high amount payment. Now the credit on the card is enough. Will be another automatic payment attempt by your side ? I was in chat with “AI dumb agent” and it told me that issue was created, but nothing happened. The link is not working. Reply form AI: I can confirm you have an open ticket with Figma support: 1964830.Support is available Monday through Friday, excluding observed company holidays.You can track your case status or add more context here, and you can also reply to the confirmation email you received when the ticket was submitted.In the meantime, you can ask a question here, or post your topic in the Figma Support Forum, and a Figma Support Specialist will follow up.Is this about ticket 1964830, or do you have a different question?

Loving Buzz, but there is a bug when viewing in Asset View. The content clipping doesn’t work and everything bigger than the canvas is low opacity - making it really hard to judge the content. In Grid View, it works fine and clips normally. Also every time I ‘flip’ through designs with up/down arrows it highlights the frame in blue - VERY distracting. The whole benefit of Buzz is seeing your posts as they would be published, but Buzz is making that VERY HARD to do. Is this a bug or am I missing something?Otherwise, such a great addition to Figma. Enjoying it. But these two are killers. 

DescriptionFor the past several weeks, my team and I have been experiencing an issue where prototype interactions do not consistently work in Preview mode, even though they are configured correctly in the Prototype panel.Issue DetailsInteractions are properly connected between frames. Navigation actions, triggers, and destinations have been verified multiple times. In some cases, the prototype connection appears correct in the editor, but the interaction does not respond when running the prototype preview. Recreating the connection sometimes resolves the issue temporarily, but the problem reoccurs. This behavior has been affecting multiple files and projects.Troubleshooting PerformedConfirmed all prototype connections are configured correctly. Deleted and recreated prototype links. Closed and restarted Figma. Confirmed I am running the latest version of Figma. Cleared and reopened files. Tested across multiple prototypes. Added additonal elements to the page or other prototypes that do

Component structure:I have an Input component.Inside Input: Slots Label The Label component is inserted into the slot.The Input component has two variants: Default Disabled The Label component itself does not have a Disabled variant.The text color is changed directly inside the Input variants. In the Default variant, the label text uses the default text color. In the Disabled variant, the label text uses the disabled text color.  label componentinput componenttext colors When I insert a copy of the component as a child element and switch variants, everything works fine.But if I change the text first and then switch the variant to Disabled, the text color does not change.  I tried the same setup without using slots, and everything works correctly. The text color updates as expected.HELPPPP!!!!

Hey there. I was testing Figma Agent and it was working properly except one thing. The only way it could change the labels and texts in my components was to override fonts with some public fonts that are already available in Figma.We’ve bought a licensed Font for our product. and currently, Figma only supports shared-font for Organization-level or higher plans. We are currently using Pro Plan.For now, Figma Agent can help for ideation, but when it comes to designing, I really don’t want to select all the texts made by Agent and style them one by one again. Figma (& Even Google) do not support many RTL Fonts by default. & Most of the popular Persian fonts are licensed & can’t be accessed publicly (“Yekan-Bakh”, or “Iran-Sans”; They are like “Roboto” & “Inter” but for Persian).I think Figma Agent should notice the local font somehow, because I really cannot afford Organization plan just to give Agent access to fonts. There should be a better way. 

This bug appears to be unpredictable, which makes it difficult to understand the root cause.I’ve created many components that contain one or more slots. However, when I make changes to the main component—such as updating colors, padding, borders, or other container-level styles—those changes are often not reflected in instances where the slot area has been configured.I would consider this a bug because it’s essential for us to be able to update the main container around a slot. It makes sense that the slot content itself remains configurable and does not automatically inherit every styling change made after customization. However, the parent component (for example, a card container) should still receive updates from the main component.What makes this particularly challenging is that the behavior is inconsistent. Some configured instances correctly receive the updates, while others do not. To clarify, I’m not referring to changes made within the slot content itself, but rather to update

I’m having an issue with code layers. As soon as I create one, it shows this error indicator, but I don’t see any actual error message. How can I fix this? I’m working on a project and this is a major problem for me.

The result is always the same:On the browser, the error message “Couldn't send to Figma" On Figma, a new completely blank file On Claude Code the mcp outputs “ Status for capture ID `d1ecf357-9ddb-4ecf-b704-c813feb3063e`: **processing**. “ in an endless loopIt NEVER works. Copying and pasting does, but that’s not much help. The whole point here is to have Claude moves stuff around, not people.Has anybody managed to get this thing working?Even a simple HTML/CSS page with no JS whatsoever fails. 

The generate_figma_design tool — documented as "Claude Code only, remote only" in Figma's developer docs(https://developers.figma.com/docs/figma-mcp-server/tools-and-prompts/) — is not available in my Claude Code session despite the Code to Canvas feature being officially announced on Feb 17, 2026. My setup:  - Figma MCP remote server is connected and working (all other tools like get_design_context, get_screenshot, whoami etc. work fine)  - Full seat on a Pro tier Figma plan  - Figma desktop app is running  - Claude connector browser shows Figma connector version 1.0.3 The tool simply isn't exposed in the tool list. Is this a version/rollout issue on the connector side, or are there additional requirements to access this tool?

you upgraded from View → Full seat and the MCP rate limit hasn't reset