Share Your Feedback

 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

Are customer inquiries or bug report requests originally this easily ignored?Is it because I can't speak English and translate it?Simple inquiries come in response, but reports and handling of bugs are ignored without reply, even though only manual answers are provided and additional answers are continuously requested.Is it always like that? I've raised the issue in Figma Make where I keep going back to the previous version of work and keep using credits repeatedly, and I've sent 3 additional requests for answers since the last message 22 days ago saying I'll look closely, but I'm being ignored.

Figma has been a pain in a**. The entire Figma feels shit. Figma never fails to disappoint me everyday. If you are giving big a** boxes then it should be entirely clickable why do I’ve to stick my cursor to text. It happens everywhere in layers, design panel, variables. For each select I’ve to press at least 3 times then it selects fully and that too when I hit that small clickable text area. Everything is so irritating. And after making components why the hell does it need to add useless “State=” word in it. I cant even batch rename it. The rename box should be expandable so I can see the entire name if its big. The color picker should’ve pin feature. Thousand time I’ve to click that color to open it. And in variable when we are adding colors it comes in the way of variables.  If I’ve created H1 regular Text Style and want to create H2 Regular Text Style, the duplicate option adds the same style inside the H1, it should create some H

I have noticed a regression on text property function in components. In the past, I was able to apply different text colors across variants, but this is no longer working. The text property now overrides styling in a way that prevents variant-specific color adjustments. In another case, the text property does not properly handle different variant states. For example, when creating an accordion component with open and closed states, the text property does not adapt correctly even though the text layer on the header remains the same. This limits the ability to manage dynamic components effectively and requires manual text update when designing variation of screen sizes and states. The text property was introduced to simplify updating text across multiple variants, but the current behaviour makes this workflow more difficult. At its core, this feature should allow users to update text values regardless of styling or variant differences, as long as the text layer is assigned to the prop

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

The Problem: When using the Auto Layout grid feature (e.g., creating a 3x3 product card layout), the actual dimensions of nested objects like buttons or text layers are hidden in Design mode. To see the exact width or height, you are forced to hover over the resizing dropdowns in the right sidebar.When a nested element is set to Hug or Fill, its absolute W and H values disappear from the right sidebar entirely, leaving only the X and Y coordinates visible. Furthermore, the dimension tooltip does not appear under the object on the canvas.Why this is an issue: It disrupts the workflow and feels inconsistent. The dimensions of the parent grid container are clearly displayed right below the bounding box on the canvas when selected, but for any item nested inside, this information is completely hidden. It would be much more convenient if the actual rendered dimensions of "Hug" and "Fill" elements remained v

Before: you could type a text style in the search and if it was the only result, hitting Enter would just apply it to the selected element. This still works fine for color styles/variables by the way.Now: you have to search, arrow down to select it, then hit Enter, even when there's literally only one result.Completely unnecessary extra step that breaks learned workflows.Please revert.

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.

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 really do not like the new confirmation dialog when deleting an account.  As an admin of an instance with 14k+ users, I delete people every single day and this new dialog gets in my way.

As mentioned in closed topic https://forum.figma.com/t/bug-autolayout-resizes-incorrectly-when-it-contains-no-visible-frames/14619, Is anybody facing the same problem? Even all contents inside “trailing-section” frame are invisible and frame resizing is set to “hug”, it still has 24 pixels of width.

I’m with Figma in this AI Design battle. I’d be happy to share my internal AI VScode + copilot workflow, maybe it would influence the Figma Make approach to what a designer needs from an actual “vibe designing”

I was looking at the release notes to double check my gut feeling that Figma itself has not been getting a lot of love lately. For my personal uses that has been the case. Only vague AI related things, which might be fine but makes me feel a lot of things are left behind. The trigger for posting this was looking at “Code Connect” after reading about a “bug” in Slots that seemed to be “intended behavior” (which is weird). This feature coming from 2024 (!) seems to be in Beta still (according to the blog post). The Github feels completely abandoned. This reminded me of things like branches (total abandonement), Percentage widths, Slots that feel half baked. The whole grid thing that seems to fizz out. New UI that was not a big success (I am still scanning everytime I select a diffferent layer where things are after all these years). Still not seeing the new App layout with the buttons on the left side (my team does, not me). Etc. Etc.I was just curious, I am getting the

The idea is to have “synchronized sections” (see Notion Synchronized Blocks) →I often need to have the same content in several files (maps, etc.), and synchronized sections would save me from having to maintain them all.  Notion Example:  

Just a thought, but the effect property in the annotation is very vertical. In general, when using variables/tokens, why are they not displayed in the annotation? Dev-team is referring to the token instead of the raw value. 

It would be great if I could use my right mouse button to drag the page like you can do in Miro. 

Hello,I’m really excited about being able to use AI to edit our app screens. It would make important stakeholders able to work by their own.However, for now, the results I get are far from being usable.First, despite the announcement, I have no icon related to this… strange.But it’s accessible through the cmd-k menu → “first draft” or “make a change”My first “first draft” was a banger. With only a vague prompt, it created a neat design with nice architecture (better than those of most of designers I’ve worked with ;-) )But as soon as I use the “make a change” menu, which is where the work begins, it’s really bad. Most of the time it doesn’t stick to the selection I gave and change something else. It doesn’t understand some basic command (selecting a menu, I just ask to add 2 entries… it renamed the others and change the colors...).So, am I missing or mis-using something? Do you have similar experiences or much better?Peace

I cannot understand the following. Figma Make makes a destructive mistake and uses credits. It then uses additional credits to fix the mistake it made. If it applies the wrong “fix”, it uses even more credits to address the issue. If it recognizes it’s addressing an issue caused by the AI, why does it continue charging a user to address the problem. This is my hugest pain point with this product and pricing model.

I upgraded my seat to `Dev` on 9. May 2025 expecting to use the Figma MCP server for development work. Despite the upgrade, MCP calls to files outside my organisation are still rejected with a "View seat" rate-limit error, even though whoami confirms my seat type as Full.I specifically upgraded to access that one single file. As the designer continues working on that file I can keep duplicating it into my own team, so, there is a clear workaround, but it’s ugly. This is causing me inconvenience and I won’t be continuing with my Dev plan after this month.I don’t see any value for Figma, other than trying to push their customers to upgrade through annoyance and inconvenience. Also, I feel misled, as I specifically upgraded to access with MCP this one file, and in the end I could but I am jumping through hoops.

안녕하세요원래는 첫 번째 사진처럼 한 페이지 안에 많은 섹션/프레임/이미지들이 삽입되어 있었습니다.작업하던 도중 갑자기 두 번째 사진처럼 대부분의 프레임 및 이미지들이 오류가 떠서 보이지 않고 창이 튕기면서 계속 저 상태로만 뜹니다.아주 일부의 사진/프레임만 뜨고 클릭, 확대/축소는 모두 가능한데 다른 작업물들이 보이지 않습니다.아주  급한 작업이라 최대한 빠른 해결이 필요합니다.조언 부탁드립니다. 

And the unwarranted billing situation continues. Despite downgrading my subscription and the lack of a live person to respond to several follow up requests to cancel, I am now disputing the charges with my credit card company. Figma, figure this out. 

Issue: After a recent Figma Make update (approximately April 30, 2026), the application now blocks all attempts to edit .html files, incorrectly identifying them as incompatible with a "TypeScript + React application."Error Message:PreToolUse:Edit hook error: [${CLAUDE_PLUGIN_ROOT}/hooks/block-bad-file-extensions.js]: Blocked: This is a Typescript + React application. Please write to a TSX file instead.Impact:Cannot edit legitimate HTML files used for third-party platform integrations Breaks existing workflow that has functioned correctly for months Forces use of workarounds (command-line editing) instead of standard editing tools Affects regular maintenance tasksTechnical Details:What's Happening: The Figma Make plugin added a

I want to share my experience with Figma subscriptions so other designers and freelancers know what to expect before paying for Pro.I purchased a Figma Pro seat for one month (around $20) specifically to complete a client project. Everything worked fine while subscribed. But after the billing period ended and I chose not to renew, I discovered something frustrating:My files became heavily restricted Editing/export access was limited I couldn’t properly continue working on my own project files Downgrading back to a normal free workflow was not straightforwardThe biggest issue is this:If a project was created while paying for Pro, users should still be able to access basic editing/export functionality afterward — especially for files that are no longer using paid-only features.For freelancers and agencies working on temporary projects, this can become a serious workflow problem because your work effectively gets h

Hi,I’ve encountered this bug testing out slots.  I’ve created a desktop component with a slot that uses components and both have variable widths for desktop and mobile. If I drag that instance with slotted components into a frame/section that’s set to mobile it will shrink down, but if I drag it out, the slotted components remain mobile size.Attached is a screenshot of the discrepancy.The instance functions perfectly fine if I manually set the desktop/mobile modes through the appearance panel though. Ps. I love the possibility of slots and can’t wait when it’s out of beta.

I’m often facing this problem. When I tried to resize the layers panel, it sometimes accidentally dragged the slide which is really annoying. Furthermore, the cursor hitbox for resizing the layers panel is too narrow (it’s really on the edge of the layers size) so that the cursor turns into vertical double-sided arrow. I hope Figma can figure out to fix the layers panel resizing issue.