Skip to main content

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?

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


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.


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


@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 ;)


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 :) 


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.

I am about 70 versions in and Editor started to be laggy.
Your workaround helped but once I started to fix errors that occured it started to be laggy again. So it doesnt seem its history slowing down but rather some function in the code. I will keep investigating. 
 


Reply