Share Your Feedback

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:  

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

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. 

This update is genuinely one of the most frustrating UX changes I’ve experienced in a professional design tool 😡 😡 😡The new left-hand navigation panel permanently steals ~60px of horizontal space on small screens, which is completely unacceptable. That space is my primary working area — the canvas. I am literally losing room to do my job so a panel can sit there doing nothing most of the time.Yes, Variables, Files, Assets, Find, and Library are important.No — they are NOT minute-to-minute actions.They do not deserve permanent, always-visible real estate. This panel is idle 90% of the time, yet it constantly punishes my workflow.On smaller displays, this feels especially hostile. Instead of prioritising the canvas (the entire reason Figma exists), the UI forces a bulky navigation column that adds zero value moment-to-moment and actively makes precision design harder.

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. 

My userflow is large, when I make it in FigJam then export it took 45k x 4k pixel to Figma, Figma design cap it on 4k for exporting image, so my imported png looked pixelated into oblivion. Could you Figma team make it seamless to add connector in Figma design like it was in FigJam? I just want to show my userflow in my portfolio in Figma design before upload it into Figma site.

Took me a minute this morning to find the new placement of the publish button for figma make prototypes. This is an action I am frequently doing as I push changes/updates to those who have access to the designs. I liked the old placement of this much better which wasn't buried two levels deep. With this latest change, putting it under the share button > publish > 1st line item - it is less clicks to change the URL of the prototype which is share button > ‘update’ icon, which is an action I would never want to do. If anything updating the URL of the prototype should be several levels deep; not publishing changes. 

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 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,This has been driving me (and apparently hundreds of others) crazy since 2021: there is STILL no native way to properly move or duplicate an entire page from one Figma file to another.Copy-paste or “Select All” destroys page background/grid/rulers, breaks prototypes, loses comments, turns library styles into local duplicates, and forgets locked/hidden layers. Duplicating the whole file then deleting pages is the only “workaround” — but it’s a nightmare with 50+ page files or design systems.I’m a fellow designer who’s fed up and seriously considering building a free Figma plugin called PagePort that would let you:Export any page (or batch multiple pages) with 100% fidelity (layers, auto-layout, constraints, page props, prototypes where possible) Import into any other open file in one click Choose Move (delete from source) or Copy Smart remapping for styles/variables/libraries + basic prototype r

As a viewer, I need to understand the design system variables—using the built-in variable manager—so I can clearly see the token architecture and color relationships across modes. This helps me decide which tokens to apply to custom components and how they will behave in both light and dark modes.

I’m trying to create a horizontal scroll section (basically a simple carousel) in Figma Sites, but it looks like this interaction isn’t supported at the moment.Has anyone managed to make horizontal scrolling work?If it’s currently impossible, is there any workaround or alternative to simulate a carousel?

I’m working on the initial ideation and brainstorming solutions using Figma for the product I’m working on. I’m genuinely happy with the results it has generated on rough level, it has helped in making my execution process faster. But I have been consistently seeing a pattern where in certain designs it provides certain features or context which are unexplained or we’re unable to understand. I tried asking within the chat itself to explain what exactly that feature means and how is it relevant in our product but it wasn’t able to answer. Also the point and edit features has been working very slow. I was assuming if it is getting heavy for make to prompt and edit / also answer questions about feature’s vagueness in the same chat estate. Shall we have a different chat estate just to ask questions about what features it has exactly designed, if it has ability to explain the context it will be helpful for us to use it or rather shape and align with our use case if it shall surpass.