Figma Make Not Working? How to Fix It

"Figma Make works slow after many iterations" has about 2.3k views and 38 replies on the Figma forum. People report typing and scrolling lag once a file reaches a couple of hundred prompts, while the app in the preview still runs fine. Figma support asked for file links and said several factors may be involved. What has helped users:

• Duplicate the file. Keep working in the copy. Forum users report this clears the lag, which points at the chat history.
• Split the code. Ask Make to break large files into smaller components. One user reported it sped things up, and smaller files are cheaper for the model to read on each prompt.
• Draft long prompts elsewhere. If the text box lags, write the prompt in a notes app and paste it in.
• Reload the tab or restart the desktop app. Rule out the general causes in Figma slow and using too much memory.

There are two different limits.

• Out of AI credits. Every Make prompt spends credits. Figma's examples are about 30 or more for a simple task and 100 or more to generate an app. When your monthly credits run out you see an in-product message and can't prompt again until they reset, unless an admin buys more or raises your limit. Check your balance from the main menu under AI balance. See Figma AI credits.
• "Too many prompts, wait and try again soon". This is a short-term rate limit for sending many prompts quickly. Figma hasn't published the numbers. Forum staff advise waiting a few hours, or until the next day.

To make credits last: write one clear prompt per change, use the Edit tool for small visual tweaks, attach one frame at a time, and don't ask Make to regenerate the whole app to fix one bug.

Libraries reach Make through Make kits, which bundle your library's variables and styles with npm packages and guidelines. If the option is missing or the import fails, check:

1. Your seat. Make kits need a Full seat on a paid plan.
2. AI settings. On Organization and Enterprise, AI features must be on for the organization. An admin turns them on in Admin > Settings > AI. Figma staff on the forum confirmed this hides the export option when it's off.
3. The library is published and has components, styles or variables in it. See Figma library not showing.
4. Your app is up to date. Update the desktop app or reload the browser tab. A past "Import from Figma" bug was fixed with a reload.
5. Education plan. Most AI features, including bringing library styles into Make, aren't available on Figma for Education.

While you sort it out, copy frames from the library file and paste them into the chat. Make picks up their styles, though not as reliably as a kit.

• Wrong in the preview. Make reads fonts installed on your computer through the Figma desktop app or font installer. If Figma Design can't see the font, Make can't either. Fix that first with Figma fonts not showing, then name the font exactly in your prompt or pick it with the Edit tool.
• Wrong in the published app. Visitors don't have your fonts. Click Settings, then Fonts, and upload a .woff or .woff2 file for each one. Publish again. The publish dialog warns about missing fonts under Typography.

• Paste the error into the chat. Make can often fix its own build errors if you give it the exact message.
• Go back a version. If one prompt broke the app, restore the previous version from version history instead of prompting in circles.
• Check the Code view. Click Code to see which file changed. You can fix a small typo by hand instead of spending a prompt on it (editing code needs a Full seat).
• Ask for less. Huge attachments and prompts that change many screens at once fail more often. Figma recommends smaller attachments and building layout first, behaviour second.

• No Publish button. Publishing needs a Full seat on a paid plan. Dev, Collab and View seats can't publish. On Starter, you can publish to the public web only if you also publish to the Figma Community.
• Testers see a Figma sign-in page. You sent the Make file link. Publish the app and share the figma.site link. Public published apps don't need an account.
• Internal-only apps. On Organization and Enterprise, an app published to your organization requires sign-in, and guests can't open it. Use a password-protected public app for outside testers.
• Changes not showing. A published app doesn't update on its own. Click Publish, then Update.

For a walkthrough of the basics, see how to use Figma Make. If Figma Design itself is misbehaving, try Figma not working.