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.
How can I edit a file created in Make in Figma?
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.
Since the liquid glass update, when I click on typography settings, they don’t open.
First of all, kudos to the Figma team for Sites, it’s an amazing product even in beta. I've been looking forward to Figma making this happen, an easy way to publish a website directly. I’ve been moving our website from Framer to Figma hoping to switch, however I encountered one issue: I have text styles with breakpoints for desktop, tablet and mobile. Everything looks good in the preview, however when I publish the site, styles use the values for the mobile breakpoints even on the desktop. Interestingly enough, if I resize the browser window to a smaller size and then back again, it works. So it looks like the first view is the one with the issue. At some point, I think it was working properly, but now this issue is back again. I can’t seem to see any correlations with anything else I’m doing. Anyone else experiencing something similar? Thank you,Panos
Hi, I’m trying to write a plugin that will create slide decks based off a template and spreadsheet of data. I want to write template slides that use some syntax such as `{{field}}` where anything in `{{}}` is considered the column name and for every row in the table a new slide is created with the placeholder replaced with the value from the spread sheet. I need to have more than one slide that is the template. So I want to be able to name the slides.Having looked around I should be able to rename the frame that represents the slide. However this isn’t possible.I’ve been following these instructions https://help.figma.com/hc/en-us/articles/360039958934-Rename-Layers The problem is the layer view doesn’t show me anything that represents the whole slide. Is it even possible to set the name of a slide?
Hello, I’d like to raise what I believe is a very reasonable and long-overdue request. Figma is a professional tool, widely used across design and development teams, and charged at a premium rate. Yet, it lacks a fundamental feature for UI design validation: the ability to float a frame or image in a transparent window above other apps, such as a mobile simulator. This is an essential need when comparing a design with a live implementation, particularly in mobile development. Tools like Overlay (which is currently unreliable), ScreenFloat, or even basic screenshots partially solve this—but these are third-party workarounds for something that should be native to Figma. I’m surprised this hasn’t been addressed yet. It would be extremely useful to: Export or pin a frame as a semi-transparent floating window. Overlay it on top of a running app or simulator to check pixel precision. Adjust opacity and toggle click-through mode for interaction below. Is there any official plan to support thi
This is a reference to a topic that was closed without resolution: Reorder objects in an autolayout component instance. Allow for order overrides Share an idea Reorder objects in an autolayout component instance. Allow for order overrides. Allow users to reorder (drag or arrow) objects inside a component instance that has auto-layout on it. Especially useful for components that have repeated elements, such as a dropdown menu or a group of form inputs, navigation. This would be much quicker than manually changing each of the elements in-between where the current element is and where the new position is. Or for users that don’t have patience and break… I can’t express how frustrating it is when a designer has to detach one of your components simply to add a tab in-between existing tabs or a dropdown option above existing ones. When I build a component I shouldn’t have to create 10 hidden layers as placeholders to make sure that the component works for a design with 2 dropdown options or
I am using Figma from almost 2 years. It’s a great tool. Previously I was using Windows 10 yet recently switched to Linux(Ubuntu). Figma doesn’t have any official release for Linux. There are some Unofficial desktop versions but they are “BUGGY”. I request you guys to release an official Figma desktop app for Linux.
Hello Figma team, I have suddenly started seeing red lines and a red dot on top of any object I hover over in a Figma file. Since this change, I am unable to move any objects with the move tool. I'm not sure if I accidentally clicked something that enabled a feature or changed a setting.
cmd + shift + enter, what would you expect that to do? what about cmd + enter? imo enter for sibling, tab for child. but up to y’all. rn it just feels unintuitive and a cumbersome
Is there a way to turn off the AI chrome when sharing the prototype in "Make"? When sharing in the prototype view, I was expecting it to just share the screens but when I shared the link, it showed the make file with the AI chrome. Is this a big? Or will this be an enhancement?
When I export any objects from Figma to PNG, the result files have the same transparent areas as in original objects. But not in PDF - transparent areas always replace with white color areas! Exporting from Figma, you can see the transparent area around the icon: Result (png), transparency saved: Result (pdf) transparency was replaced with white color:
I created variables for weight, font family, and sizes. In our design library, I updated all our font styles with variables. The variables are listed below. The problem is that sometimes, the fonts would show up as “Open Sans Condensed” instead of “Open Sans”. The only way to correct it was to break the link to the style and then reapply it. It broke many components and styles where this library was used. I disconnected all the variables from the font styles and defined them as one would normally. I published the library again. Updated the library within the file and the font on the text was still wrong. The fix is to select the component. Reset changes and then undo. Not sure what I did wrong or why it broke so much stuff. But, I would like to resolve it as we plan on making several different modes for different accessibility needs and this would save us a considerable amount of time. Note: Open Sans is not installed locally. The problem occurs on Mac and PC using Chrome, Firefox, and
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.
