Skip to main content
Question

Figma Make works slow after many iterations.

  • June 6, 2025
  • 38 replies
  • 1658 views

Show first post

38 replies

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


Tom38
  • New Participant
  • August 29, 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.

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. 
 


Gayani_S
Figmate
  • Community Support
  • September 5, 2025

Hey everyone, thank you for sharing your experiences here, we’ve been listening closely.

 

The team has now rolled out performance improvements aimed specifically at reducing lag in files with large chat histories. In many cases, this should bring the experience back to a much more usable state. Please give your file a refresh and try it out.

If you’re still running into problems, we’d really appreciate it if you could share your feedback in this thread.

 

Thanks again for your patience! 


MySmile
  • September 5, 2025

Still didnt find a proper solution for me :(

­


Tom38
  • New Participant
  • September 5, 2025

Hey everyone, thank you for sharing your experiences here, we’ve been listening closely.

 

The team has now rolled out performance improvements aimed specifically at reducing lag in files with large chat histories. In many cases, this should bring the experience back to a much more usable state. Please give your file a refresh and try it out.

If you’re still running into problems, we’d really appreciate it if you could share your feedback in this thread.

 

Thanks again for your patience! 

Hello Gayani, very nice to read that! I tested it, first prompt was nice and quick but then it started to lag again. I have to close and open the file again to continue work. First but simple prompt goes through but once I start asking more complex things it keeps lagging and thinking and working for uncommonly long time. 


Wendy Chen
  • New Member
  • September 5, 2025

 (currently 230+ iterations).

Andrii, how can we know how many iterations have we done? Manually check?


Tom38
  • New Participant
  • September 5, 2025

(looks better now?!)


Shane_Jensen
  • New Member
  • September 23, 2025

Hey everyone, thank you for sharing your experiences here, we’ve been listening closely.

 

The team has now rolled out performance improvements aimed specifically at reducing lag in files with large chat histories. In many cases, this should bring the experience back to a much more usable state. Please give your file a refresh and try it out.

If you’re still running into problems, we’d really appreciate it if you could share your feedback in this thread.

 

Thanks again for your patience! 

It Works!

I wish I saw this 18 days ago (I didn’t receive a notification). Thank you for fixing this.


  • New Member
  • December 3, 2025

I’m on version 377 now and it’s been stuck on the “reasoning” stage for an hour. I can’t pause it. I even tried duplicating the file, but the new one is also stuck on reasoning with the same prompt. Any idea how to fix this?