I believe that is because the Beta version it can undergo bugs/performance issues.

But, also in Figma, once your file gets bigger and bigger, it will require more CPU performance, so ideally, it is to start breaking the file interactions into smaller pieces to save memory.

Thank you! Any ways to break the file in Figma Make?

You can just prompt to Make asking to break the code into smaller components.

I just did it as a test, and it worked very well.

Hey ​@Andrii Bozhenko! 

I've gone ahead and flagged this with our team. They’ve asked if you’d be able to share the file key for the file where you're seeing this happen, having access to the specific file will help us investigate, as there could be a few different factors contributing to the performance issues. If you’d rather not post it publicly, feel free to DM me and let me know here.

Thank you, 

Gayani 

​@Gayani_S I have the same problem I’m up to version 367. Happy to share the file key for the file with you also.

I am also facing the slowness issue.

Is it going to remember every iteration.. forever?

Many iterations make it difficult to navigate the history. Most of that history isn’t even relevant anymore. It could be that I tried some things and then restored to a previous version or it’s just really old prompting that I don’t need to reference anymore. Would archiving history make it faster?

This is exactly what I’m looking for - or the ability to duplicate the file and have that duplicate as a new “baseline”, essentially version 1 again. 

scrolling the chat list becomes slow, and inputting prompts is also very laggy. It is recommended to consider introducing a ​​virtual list​​ to reduce DOM nodes.

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.

Thank you. I've sent you the URL via direct message. Looking forward to the fix.​

Have also sent mine over via DM :)

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

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.

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. 

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

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

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

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!

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​​​​​​

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.

​@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!

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! (?)

I’ve hit this wall now :| 

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!