Share Your Feedback

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

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”. 

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.

Our team is attempting to migrate our Sales Team presentations from Google Slide to Figma Slides.Good Things:The design control is soooo much better than Google Slides. It’s so easy to bring in work from a regular design file allowing us to have beautiful slides.  Animations are cleaner and simpler to work with than Google Slides. Although not as sophisticated as Keynote or PPT.  Nesting slides is nice; especially when we made a Master Deck File that houses 100+ slides for the Sales team assemble decks from. Feedback:Linking is currently not a pleasant experience. 1. You can only link text links which underlines the text by default (but you can toggle the underline off). You cannot add a link to objects/images.  2. It is easy to add a slide # links, however if you duplicate a presentation file the links created stay with the original file. So you have to manually change each link again making it super

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

 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

Hi, I have a component that has a video (in order to play it in prototype mode). In today’s update, it’s displaying a “video” label and a big “play” icon on the canvas. While I think it’s nice to preview a live video on the canvas, I also want the ability to hide this elements (since they’re not part of the design specs). I was wondering if there’s a way to hide this? (the attached screenshot is a good example of specs that I often attach and I don’t want developers to think that those elements are part of the design).   

Is everyone around here ever able to use Template styles in Figma Slides? EVERY time we paste a slide from another presentation, it creates a ‘new’ template so we end up with a dropdown full of slightly similar templates styles and it is impossible to delete them unless I switch every culprit style to the ‘main’ style. But doing usually changes things around so we just gave up trying to use them 😭 Here is a screenshot of the dropdown in most of our slide decks: 

We just wrapped the big announcements at Config, and we know there’s a lot to take in.This thread is your space to share reactions, ask questions, and let us know what you're excited about (or still curious about) with regard to Figma Draw. Our team will be actively reading and sharing relevant takeaways with the product team. What we’d love to hear from you:What aspects are you most excited about — and why?

 Can we merge all Figma skills into a single one? Otherwise there are too many skills in Codex, all of which are Figma‑related, and they take up too much space.

Greetings, I’ve been using an AI agent to develop a prompt to review figma concepts to cover the following: UX heuristic using NNg as the foundation, UI errors, and Grammatical errors. The prompt needs to be copied from the Ai tool and implemented in Figma Make. Figma Make has to recreate the reviewed design exactly before this prompt is implemented to review the design. This is a lot of steps to review a designs. Will Figma introduce a a feature to fully review designs on an artboard covering those items? UX errors, UI errors, and grammatical errors?

Currently, when we have many files open in Figma (which is not uncommon in a work context), we tend to lose visibility and access to some of them when trying to switch tabs.Intuitively, I try to scroll horizontally through the open file tabs with no success, which makes navigation quite difficult. As a result, I either have to drag the entire Figma window to the side to expand the view or feel forced to close files just to access others.Is there any plan to improve this usability?Thank you.

This is so annoying! Each month I need to search for the invoice in your unfriendly interface. Seriously now! Better unsubscribe the service than getting such frustration.

Hi! Has the canvas panning keyboard shortcuts changed recently? I use Ctrl+Space+scroll wheel to pan and zoom the canvas but now that keyboard shortcut puts me into a Keyboard picking mode. Is this new? It really gets in the way of working.

Hi,When I want add a PDF to a Figjam board I see a modal window with a few options (see attachment). I do not always want to convert the PDF. And when I want to convert the PDF I noticed that the file is not converted the correct way. Is there a way to add PDF without converting? 

So currently there is no Desktop app (except the unofficial version) for Linux, which is very sad! We need official desktop App for the linux. 

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

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.

It is annoying when I have to libraries connected to my project, but it always autosuggests the wrong library when selecting another text style. I want it to show me the selection of text styles from the library that the text is already using – not text styles from the other library. This happens also when selecting color. This issue wasn't an issue before. As you can see in the video attached, the library I want based on the component selected is collapsed. I want to library that is already used for the object in question to be expanded.

There are several collections hidden behind the expand buttons without any clear indication in the UI.It took me a few minutes to find hidden collections. It’d be great to add more affordance somewhere so that a new team member knows there are hidden collections under “Variables” window.  

I was very excited to hear that grids were coming to Figma. CSS Grid was introduced years ago and brought with it many things that flexbox was incapable of doing, so I was hoping for a similar level of new capabilities here, and I genuinely cannot believe that this feature is being shipped in its current state (even as a ‘beta’). This is a very long post, but I feel like this feature has been implemented so poorly that it legitimately sows doubt in Figma’s capabilities to deliver features in the future.Inability to ‘hug’ contents Both rows and grids themselves are unable to resize themselves to match their contents (‘Hug”). Row heights must be either “Auto” (1fr) or a fixed height, meaning that if you want your rows to be sized per their elements, you’ve now manually defined each row height in px (not even a variable value), and instead of getting a clean CSS output, now you have however many rows defined in exact values, destr