Share Your Feedback

When viewing a spec, the big blue button is to request a full seat instaed of logging in or viewing the spec, which is the most likely case. This results in constant accidental ‘so and so as requested a full seat’ daily. Its the most annoying thing in the world and causes mistakes from my team members approving it.

The Issue: Currently, manual file organization (uploading/moving .tsx files into folders) is only available at the start of a project. Once a history is established, the UI forces users to use the AI agent to move files.Why this is broken: Credit Waste: The AI treats "moving a file" as a full generation task, often rewriting the entire code block. Using AI credits for basic file system management is inefficient and costly. Workflow Friction: Manual uploads are restricted to the root directory, preventing users from maintaining clean project architectures without burning through their prompt limits. Requested Fix: Enable a permanent manual file manager that allows users to upload, move, and organize files across folders at any stage of the project without invoking the AI agent or consuming credits.

 I ran into a font issue while working with MCP use_figma and wanted to share it here. I have a font installed on my system (Pretendard) that works perfectly fine in the Figma UI — it shows up as "Installed by you" in the font picker. However, it's completely invisible to the Plugin API when running through MCP use_figma. listAvailableFontsAsync() returns around 7,600 fonts, but none of them are locally installed ones. It seems to only return Google Fonts.loadFontAsync() also fails, and trying to appendChild a component instance that contains text using the font throws a font load error — even into a non-auto-layout frame. Steps to Reproduce 1. Install a local font on your system (I tried both ~/Library/Fonts/ and /Library/Fonts/ on macOS) 2. Confirm the font shows up normally in the Figma UI 3. Run the following via MCP use_figma: const fonts = await figma.listAvailableFontsAsync(); const r

Hey everyone. I am Alexander and I built a plugin called Design System Sync. I was honestly just tired of manually copying variables over to developers every time I changed a simple hex code. So basically I made a tool to fix this massive pain point.The plugin grabs your Figma design tokens and variables. Then it automatically creates a pull request in GitHub or Bitbucket with the updated code. Your developers just review the code changes and hit merge.Here is what it can do for your workflow:Automatic PR generation saves you from sending zip folders or raw text files on Slack.W3C Design Tokens and CSS Variables support means it works with most modern code setups.Multiple mode export handles your light and dark themes perfectly.Visual change detection shows exactly what you modified before you send it off.The free tier gives you 5 exports a month and includes all the exp

With the strict enforcement of AI credit limits starting March 18, I’ve been looking at our organization's options for scaling usage. The current pricing structure for additional credits vs. adding new seats seems completely disconnected from reality for power users.Let’s look at the numbers for a Professional Plan (2026 pricing):Option A: Add a Full Seat. Cost: $16/mo. Cost/credit: ~$0.005 Cost for 3,000 credits: $16 Option B: Pay-As-You-Go (Overage). Cost/credit: $0.03 Cost for 3,000 credits: $90 Option C: Shared Credit Subscription. ​​​​​ Cost: $150/mo for 5,000 credits. Cost/credit: $0.03 Cost for 3,000 credits: ~$90

I was having internet connectivity problems, so I was met with the Connection Error screen:Connection error screenshotThe “Try again” button doesn’t seem to do anything.I had to go to the tab, right-click it and use the “Reload Tab” option. 

I’ve found slots incredibly buggy right now unfortunately. I love the idea, but they’ve been rather frustrating lately.I’ve had two bugs that seem related I have repeatedly had, but am unable to set up a test file for these. Slot sizes not adjustingSomething like this hierarchy. Despite the fact the two components are bound in an autolayout with gutter, it doesn’t seem to paint properly. I often have to double click the children components individually.Component >↪ Slot↪↪  Rows [Autolayout]↪↪↪ Row [Autolayout]↪↪↪↪ [Component]↪↪↪↪ [Component] Slot content not refreshingSometimes a colleague uses my account on their computer to check something. When checking an instance of a component with a slot, sometimes they see the default content and not the content I’ve put in there. Despite it being saved. I have found no solu

Hello,I have always been a big fan of your platform, especially because it was one of the few that had not given in to the model of charging subscriptions for standard use.However, it is now no longer possible to create more than three FigJam files, which seems to me like the beginning of changes that may gradually reduce features that were previously free.I have always recommended Figma and would not like to stop. Please do not follow this trend, as this was exactly what set you apart from others.I am Brazilian and used a translator to write this message.

Hello, good day.I’m experiencing serious issues with the new Figma UI update. Many essential tools — such as padding controls — are missing or hidden.Please do not enforce this new version. The previous UI was much better, clearer, and far more efficient for designers.This new version has no advantages, feels confusing, and makes our workflow significantly harder.

I have been working with Slot for a while, introduced it in our component library too.Here are a couple of observations:The magenta outline feels too prominent and interferes with design and understanding of space, padding, etc. I would have preferred a subtle affordance that slot exists.While selecting things on canvas, earlier entire frames, components would easily get selected but with slots in those components, when I drag and select, selection happens randomly, sometimes, only slot layers are getting selected instead of entire frame or component which is not what I expect. And, it just messes it up. Cmd+X / Undo doesn’t work properly if I delete something from slotted component. There is not an easy way to return to previous state.

I’d like to share feedback regarding the implementation of AI credit limits in Figmake. As a designer managing multiple complex projects, I believe credit restrictions would greatly undermine Figmake’s usefulness in real-world design and prototyping workflows.  1. Most AI usage is for fixing bad or incomplete output, not luxury use.  In practice, a large percentage of AI prompts in Figmake are iterative—used to correct layout issues, rebuild misinterpreted elements, or align behaviors with visual intent. Each refinement quickly consumes credits even though the output quality depends on that iteration. Penalizing iteration limits the model’s ability to produce accurate prototypes, especially when the AI output is imperfect through no fault of the user, making credit usage really unfair and frustrating.2. Predictability becomes impossible, discouraging adoption.  With a credit cap that no one knows how to predict and calculate ahead of time, I can’t plan how

I would like to provide feedback on  support experience.I wanted to pay for Figma but both payment methods were declined. I was told that problem is with my bank and I need to contact them or use another card, thats all we are closing you case.I contacted my bank which confirmed there are no declines or restrictions on their side.I tried another card but I cant pay in euros from ukrainian card according to Figma restrictions and I cant change currency in invoice according to Figma restictions again!I contacted support once more and all I get was the same “contact your bank or use another card” without any real investigation of the issue.This has been time-consuming and frustrating.Could this case please be escalated to someone from billing or a support manager who can properly review it? Because it looks like you dont need your customers to pay you.

The management of seats is absolutely terrible. We have unused seats, and there is no way in the user interface to remove them to avoid being charged in the next billing cycle. If this is automatically not charged, it is not explained anywhere. The most terrible experience I had managing subscriptions after 25 years of actively using internet.  

The Figma MCP server fails to authenticate when using opencode, returning a 403 Forbidden error. To Reproduce1. Configure Figma MCP in opencode.json:{  "mcp": {    "figma": {      "type": "remote",      "url": "https://mcp.figma.com/mcp",      "enabled": true,      "oauth": {}    }  }}2. Run: opencode mcp auth figma3. Error received: HTTP 403: Invalid OAuth error response: SyntaxError: JSON Parse error: Unexpected identifier "Forbidden". Raw body: Forbidden Expected behaviorOAuth authentication should succeed, as it does with other MCP servers like Context7, Sentry, etc. Root causeAccording to Figma's documentation (https://help.figma.com/hc/en-us/articles/32132100833559), Figma only supports a pre-approved allowlist of MCP clients:- Claude Code ✓- Cursor ✓  - VS C

Figma, Auto jump to next comments when previous comment is resolved is frustrating to use. Most of the times when we resolve a comments we tend to look and ponder on screen if we want to add any new comments. When it auto-jumps we need to search for the section again which is really bad experience. Please look into this. 

Hello Figma Community,I’m currently enrolled in the Google UX Design course on Coursera and have been using Figma Education Pro through this program.I received an email asking me to re-verify my student status, so I selected “Bootcamp / Online Program”, but I got the message:“Bootcamp students & educators: You cannot self-verify, you must be verified by your bootcamp. Please reach out to them directly with any questions.”Since Coursera is an online program, not a traditional bootcamp, I don’t have an admin to verify me. Coursera support says I should self-verify, but Figma doesn’t allow it for online students.I want to know: How can online course students like me maintain Education Pro access? Will our accounts automatically downgrade to Starter after Sept 29 if no verif

This new feature disrupts my usual workflow of clicking outside the hex color value box to change the color. As a result, I often end up selecting a color from the list unintentionally.I called this feature “Annoying color style dropdown I didn’t ask for”. 

I want to organize my components into Icons, Buttons, Fields etc but these are already inside a folder and figma does not let me create any more nested folders so I need to browser all my 200+ components from one heap? And I’m not going to move them out from the folder because I need the parent folders too. Very bad designer experience!

We have a general collection of colors but for my specific file I want to add more variables. However this is not possible with extended collections. My work around is to use less frequently used variables (button-hover) for my usecase (color-bold) and this makes it very confusing and limiting.

While using Claude.ai with the Figma connector Claude told me it wasn't able to programmatically insert the contents into the slot inside a component “because Figma protects slot nodes from plugin writes”. If this limitation is intentional, why? It serious limits the usefulness of the connector. Please allow the connector to write to slot nodes.

When a change is made to an instance, any updates made to the original component after that do not carry over. This is very frustrating and results in me updating each instance. 

Hey everyone. I want to share some feedback on the current Figma Make credit system, and provide a literal step-by-step escape route for anyone else who feels trapped.I absolutely love(d) Figma Make for the initial 0-to-1 build. Figma successfully built "vibe coding" into their platform, which is incredibly cool. But what isn't cool is blocking users from actually using it that way. The entire value proposition of Figma is rapid iteration. Yet, I hit my third lockout this week after spending nearly 100’s on credit expansions in a two weeks.Almost all of those credits were spent on debugging, QA, and fixing logic—not building new features. The usage-based pricing essentially acts as an "iteration tax" that actively discourages you from polishing your app.If you are building a complex web app, you have to eject your code to finish it. I was intimidated by this at first, but Claude Code and Gemini (which gave me easy instructions) literally walked me throu

This button is too close to the flow starting point section. I almost never want to send to figma make. Make this dismissable or hideable. I just want to make this frame a flow starting point.