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

Jake_Spillar
New Participant
June 20, 2025

Hey everyone, really appreciate you flagging this — we hear you! To help the team dig into this, it would be super helpful if you could share the URL of the file where you're seeing the slowdown. There are a few factors that might be at play, and having access to the specific file will help the team investigate more accurately.

 

Have also sent mine over via DM :)

Jake_Spillar
New Participant
June 25, 2025

Hey everyone, really appreciate you flagging this — we hear you! To help the team dig into this, it would be super helpful if you could share the URL of the file where you're seeing the slowdown. There are a few factors that might be at play, and having access to the specific file will help the team investigate more accurately.

 

hi Gayani - wondering if there has been any progress on this?

Gayani_S
Figmate
Community Support
June 26, 2025

Hey ​@Jake_Spillar, apologies for the delayed response! I’ve shared URL of the files you and ​@fencerzheng provided over with the team, and they’re currently investigating the issue. While I don’t have a timeline to share just yet, please know this is on their radar.

I understand how frustrating performance issues can be, and I truly appreciate your patience while we look into it. I’ll make sure to update you as soon as I hear more from the team.

dschambach
New Member
July 1, 2025

I have this issue as well. We are on iteration 275 and it’s almost unusable.
Asking Figma Make to break the code into smaller components did not improve performance. 

Shane_Jensen
New Member
July 2, 2025

Came here because I have also identified that the number of iterations is making it slow.

 

If you share the prototype and run that, it is super fast. But soon as you run it in edit mode, it takes ~30 seconds for typed text to come up. Everyone on our team is experiencing the same issue.

 

  • No way to remove old chat histroy/context
  • Duplicating prototype keeps history, so cant remove it that way either

(separate note - it can be nice to remove old context and add new chat history anyway, if I want to focus on a new area and not leverage the existing context for it).

dschambach
New Member
July 2, 2025

A temporary solution is to write your prompt into a text editor, then cut & paste.

New Member
July 2, 2025

I have the same issue, because the chat is too long probably over 200 versions… this is how you build a website no? lol
please add clean chat, or archive somehow, the context cant be infinite..
its soo slow no, take me 1 min to type my prompt ):

Jake_Spillar
New Participant
July 4, 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.

New Member
July 4, 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.

nice workaround!

Abod
New Member
July 7, 2025

hey, ye i also have that same problem its going really slow for me now also i think i am on version 360 and its almost like i have to wait 10 seconds after every click


please figure something out for this issue

 

Kind Regards, Abod​​​​​​