Skip to main content

Performance Degradation Due to Excessive Make History

  • March 27, 2026
  • 3 replies
  • 85 views
lzx

Issue Summary
I'm experiencing severe performance issues in a Figma Make file that has accumulated naerly 700 context versions. The file frequently freezes, becomes unresponsive, and consumes credits at an unusually high rate, making it nearly impossible to continue working.

What I've Tried
- Using the desktop app instead of the browser (still laggy)  
- Clearing cache and performing hard refreshes  
- Avoiding large batch prompts – the problem persists  

Root Cause (Suspected) 
The excessive number of Make conversation versions appears to be the main bottleneck. I understand that users cannot manually delete version history, and the current file size (or context length) is causing the editor to struggle.

My Requests  
1. Reset / purge the Make conversation history for this file from the backend to restore performance.  ONLY keep version 689
2. Advise on best practices for cleaning up and structuring the code generated by Make. The codebase has become quite messy after many iterations, and I'd like to know if there are recommended workflows (e.g., exporting structure, refactoring prompts, organizing components) to keep the project maintainable as it scales.

Thank you for your help. I'm happy to provide any additional details if needed.

    3 replies

    Tom Reem
    Figmate
    • Tom Reem
    • Figmate
    • March 29, 2026

    Hi ​@lzx — welcome to Figma Forum and thanks for taking the time to flag this issue, along with all of the troubleshooting you've already tried. Sorry for the disruption this is causing.

    I went to check on this for you and, while I can't access or share account or file specifics, I can see that you were able to connect with the Technical Quality team by the time I got to your post here. When you have a moment, please check your inbox associated with your Figma account for your case number: 1817924. A team member reached out with more details and next steps specific to the file you're working in.

    Please don't hesitate to reply if any questions remain, or if you notice any improvements. Appreciate your patience as we look into this together.

    Adam Howard
    • Adam Howard
    • New Member
    • April 7, 2026

    Hi ​@Tom Reem Are there any best practices around maintaining a Figma Make file of this size? I’m also at  +700 version history. While I have not yet experienced noticeable performance issues (beyond the initial load) I worry that it’s not far away, esp if the number of versions is causing performance issues. Thank you!

      Tom Reem
      Figmate
      • Tom Reem
      • Figmate
      • April 7, 2026

      Hi ​@Adam Howard — great question, and glad to hear things are running well for you!

      I don't have specific guidance to share on version history limits at this point, but this blog post from the team covers practical tips for working efficiently in Make and getting the most out of your prompts: 8 essential tips for using Figma Make.

      If you do start noticing issues down the road, here's the quickest way to get a closer look from our Technical Quality team:

      1. Head to the Support Hub
      2. Where it says “Tell us about your issue,” type: report a bug
      3. Click Start a chat
      4. Select Enter
      5. Respond to the following question with: yes
      6. Complete the form and be sure to include the URL of the Figma file where this is happening
      7. Press Submit

      That'll connect you with the team who can dig into your file specifically. Appreciate you thinking ahead on this — don't hesitate to reach out here if anything changes.

      Terms & ConditionsCookie settingsAccessibility statement