Skip to main content
Andrii Bozhenko
New Member
June 6, 2025
Question

Figma Make works slow after many iterations.

  • June 6, 2025
  • 38 replies
  • 2305 views

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?

This topic has been closed for replies.

38 replies

Josh22
Active Member
July 9, 2025

Is this actively being fixed? I’m roughly on version 200 in a file at it’s basically unusable. I only even have this many versions because either I ask singular small prompts at a time to avoid AI breaking something (the greater the prompt request, the more complex it becomes) or I am dealing with AI that impacts (breaks) other parts of the design for no reason so I have to ask it fix something it broke.

My files aren’t that large either, I’m only building out single pages for user testing allowing for more authentic interactions like search, filtering, and sorting data.

New Member
July 9, 2025

I have a solution to clone the entire project into a new Figma Make file - it’s the history that slows everything down. A colleague has created a guide for - this does work if you follow the instructions exactly. As a note to Figma - an option to clone a file without the conversation history would be very much appreciated.

 

The guide includes a series of prompts, and some manual copy-pasting, that'll help us migrate existing Make files into a new one while preserving file structure and code. I've tested it 5-6 times and each of those times it was successful!

 

The guide covers the following:

  • Exporting project file structure
  • Creating clean project blueprints
  • Automated file/folder creation
  • Code transfer process
  • Context briefing for Figma Make

đź“‘ Written guide link: Figma Make Project Migration Guide

 

Hopefully this helps someone until we have an official solution.

​@Gayani_S can you relay the “Context briefing” step (last step) to the team building the feature to help clear the history in the future, or at least be sure to consider it? 

Thank you ​@Jake_Spillar for the steps!

New Member
July 9, 2025

I’ve tried a different path since hitting the slowness.

 

I built a 3000 word prompt to kickstart an application wireframe in a single iteration. There are many slight differences between the results that can’t be controlled easily, but I’ve found this to be pretty good in the short term. The wireframe is recognizable.

This allowed me to create 6 different “branches” of the application in different files, where I iterated on specific features simultaneously. Being able to do these in parallel was helpful for productivity.

Now I want to merge some of these files that each have hundreds of iterations back into a single Figma Make file. I could see this need if a teammate branched off in a similar fashion.

I’m in a predicament now. I’d have to carefully re-prompt the original file to get all the files merged, but the iteration counts are prohibitive to attempting this.

So, don’t follow my path here unless small disparate Make files are sufficient for you.

 

Unless ​@Gayani_S can work some magic and build a merge feature for multiple Figma Make files! (?)

Yadu Rajiv
New Member
July 11, 2025

I’ve hit this wall now :| 

Hideki uxer
New Member
July 11, 2025

No AI editions anymore!!  always the same error TRY AGAIN WITH FEWER INPUTS.  Try to fix this but I can’t even telling to simply fix errors, two words nothing!

New Member
July 15, 2025

exported the code to cursor, could not do that anymore, too slow!!

edon.menezes
New Member
July 15, 2025

I'm also experiencing a lot of slowness in my Make file. My portfolio has become so slow that I stopped updating it until this issue is resolved. I've even split the files to try to improve performance, but it still hasn't worked.

Edwin Lirio
New Member
July 19, 2025

does anyone have a prompt structure technique to solve the recurring errors? it seems like it doesn’t end.

Peter Jaeger
New Member
July 21, 2025

​@Gayani_S is there any update on this matter ? I’m hitting the wall as well now. Tried to solve it with different user but no change in speed. Seems the file is out of “AI credits”… more than happy to slot in a few more bucks ;)

Matt W-P
New Participant
July 24, 2025

I have a solution to clone the entire project into a new Figma Make file - it’s the history that slows everything down. A colleague has created a guide for - this does work if you follow the instructions exactly. As a note to Figma - an option to clone a file without the conversation history would be very much appreciated.

 

The guide includes a series of prompts, and some manual copy-pasting, that'll help us migrate existing Make files into a new one while preserving file structure and code. I've tested it 5-6 times and each of those times it was successful!

 

The guide covers the following:

  • Exporting project file structure
  • Creating clean project blueprints
  • Automated file/folder creation
  • Code transfer process
  • Context briefing for Figma Make

đź“‘ Written guide link: Figma Make Project Migration Guide

 

Hopefully this helps someone until we have an official solution.


Just wanted to say thanks / give kudos for this - worked beautifully - I have a very complex site, it’s got a lot of moving parts and I was up to version 479.. and I was suffering with slow downs. This helped a lot so thanks :)Â