We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
Find solutions, get advice, help others.
I've been experimenting with the new Figma Make feature and noticed a recurring issue that's affecting usability: After about 8–10 successful prompts (each 1–2 lines long), Figma Make starts rejecting any further prompt with the message: "Try again, with fewer inputs." This happens even when the prompts are extremely short, e.g., "Create a dark-themed button component" or "Add a CTA section with three buttons." I’ve tested this across multiple projects and browsers. The issue persists consistently, and the only workaround seems to be refreshing the tab, which sometimes helps temporarily — but not always. Additional Context: Even though Figma Make is currently laggy while generating prototypes (which I can overlook), this input rejection bug makes it difficult to iterate quickly or finish design ideas. It feels like a silent rate-limit or session exhaustion issue that’s not clearly communicated to the user.
I was asked to open a file in recovery mode because it ran out of memory, i tried doing that but it still wasn't opening. so i checked online and i was asked to clear the figma app cache. I cleared the cache, and after doing that, the file opened, but now all the screens on that file are missing. i cant find them anywhere. pls advise on how to recover these files.
With the admin updates that came out on March 11, there is one new feature that we would like removed or able to be turned off by an org admin. When a user requests an upgrade in Figma, this new feature allows the user temporary access to the functionality of that seat for 3 days (unless the admin replies to the upgrade request sooner). Here is the description from this article: To ensure users aren’t blocked from collaborating while admins review their seat request, they’ll be able to use the functionality of the seat they requested temporarily for up to three days. During that time, they can create new files and edit any files where their teammates have given them edit access. They will not be able to edit files they do not have edit access to. The temporary access ends immediately if the request is denied or expires. Prior to the updates on March 11, this was the behavior for dev mode requests -- users would get temporary dev mode access for a short amount of time while they waited
Figma MCP Server currently only binds to 127.0.0.1 which makes it unable to listen on any other interface. WSL creates a virtual interface, to which the MCP Server must be able to listen, or Claude Code cannot connect to the MCP Server. Long story short, you need to make the MCP Server configurable. As it is now, it’s useless for Claude Code users on Windows.
The meta info of a comment link shows figma design file icon. Better UX:If a user has figma authenticated on their slack as an integration. The meta info should show the comment text truncated to 30-40 characters.
Hello, I’ve been playing with the new feature figma make, and when I upload a whole screen (frame) with a specific design, the redering comes out totally different and messes up the whole design. I’ve tried uploading a png instead of an image, and nothing, I’ve tried to “clean up” the frame and erase all the invisible elements of the frame, and nothing. Am I missing something? Is theres any way to make it work better? Any tips?
Very low performance speed in Figma Make when the thread reaches large sizes (currently 230+ iterations). All actions in the chat area occur with a significant delay (typing, scrolling, etc.), making it impossible to work. However, the prototype itself works well within FM. Has anyone encountered this? What could be the cause? Could it be related to the power of the laptop?
I’m just curious why this in the [padding] box 👇 is not here in the [gap] box too 👇 why I have to open the drop down for the variables when I can get it within a single click?
Organization would be immensely helpful if we could create folders for our drafts. I want to be able to organize my drafts into different categories (such as UI kits, Ideas, Wireframe kits, iOS, Android, etc…) so I can find files easily. Right now, the drafts page is a huge jumbled mess and I can’t create Team pages for everything. Maybe something as simple as being able to add ‘tags’ to each file, similar to Zeplin.
I was going to praise how neat the new Annotation feature is, when I realized the content is only visible to Dev Mode accounts. Are you serious? I understand you want to limit creating annotations to certain seat types, but viewing annotations should be a viewer-level feature. Come on Figma, there are better ways to convince your users to pay for a subscription. This is such a crooked move.
Truck Simulator Big Rigs Hi Figma Community, I'm working on a personal passion project – a UI concept for a game called "Truck Simulator: Big Rigs" – and I've run into a frustrating prototyping issue that I can't seem to solve. The Problem: I've built a series of interactive components for a vehicle customization screen (e.g., choosing paint colors, wheels, etc.). When a user makes a selection and navigates to the next screen, everything works fine. However, when they use the "Back" button to return to the customization screen, the components don't reset to their default state. They remain in the last selected state. What I've Tried: Ensuring the "Reset component state" checkbox is ticked on the "Back" button's Navigate To interaction. Rebuilding the interactive components from scratch. Testing the flow in a completely new, clean Figma file with just those components. Checking for any conflicting interactions on the frame. The issue persists, and it's breaking the user flow I'm trying
Does anyone have any idea why the default bold variant for Noto Sans seems to be the ‘Display bold’ and not just ‘Bold’? I can’t find a distinct ‘display bold’ font variant installed on my Mac and it doesn’t seem to be present as a selectable weight when I create a new text box and start typing - I just get ‘Regular’, ‘Bold’ etc. However, if I select some existing text set in Noto Sans and hit `command + B` I end up with the condensed, taller display weight variant. I genuinely have no idea where the display weights are coming from or how to turn them off. Does anyone have any idea? It is driving me a little crazy 😳
Hello, we are looking to set up a new Design System in my company and can’t decide on the 2 or 3 tier system for tokens. Due to very limited resources, we are leaning towards 2 tiers, but I really like the idea of Component-specific tokens (3rd tier). I have found a tutorial demonstrating the setup of Semantic tokens, but they were actually categorised and named as Component-specific (video link: https://www.youtube.com/watch?v=1O2sROtE3uI) Is this a usual practice? Could we define some Component specific tokens on the second level alongside Semantic tokens? Any advice is very welcome. Thank you.
Hi, I have a question about a variable/component I created. I’ve set up a condition where, when the toggle or switch is turned on, the dropdown menu becomes enabled, and when the toggle or switch is turned off, the dropdown menu becomes disabled. However, I noticed that when I turn the toggle off, the selected item in the dropdown resets to its default value. Why is this happening? Before [Condition Switch is OFF] After Switch to Active After [Condition Switch is ON] This is my Condition
APIs, guides, plugins, and more.
Find a virtual event that speaks to you.
Find answers, learn more.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
