Hii Figma. Files in Figma takes so much time to load. I’ve checked my Internet connnection and I’ve found out that there is no problem with the Internet. After Adobe bought Figma, I’m experiencing this. Please solve this issue asap @Figma_Support
5 Likes
Same. Started for me right after the updates came in during last Config
3 Likes
Hi all,
Thanks for flagging this!
Can you please try clearing out your cache in the browser and Desktop app and check if this helps?
You can clear the desktop app cache on a Mac in the Help menu under Troubleshooting. If you’d prefer to manually clear your cache you can:
- Quit the Figma desktop app
- Open Terminal.app and enter the following command: rm -rf “$HOME/Library/Application Support/Figma”
- Try opening the desktop app again
You can clear the desktop app cache on Windows under the toggle-arrow at the right of the top toolbar under Help > Troubleshooting. If you’d prefer to manually clear your cache you can:
- Close the Figma desktop app
- Open the Start menu, and paste in this, followed by enter: %APPDATA%\Figma
- In the window that opens, delete the Desktop and DesktopProfile folders if they exist
- Launch the desktop app again
If it still doesn’t help, please reach out to our support team
(with URL link to the file which is effected, share a quick screen recording or screenshots demonstrating this issue and precise if this is happen in the browser, desktop app or both) so they can investigate further here: https://help.figma.com/hc/en-us/requests/new?ticket_form_id=360001744374
4 Likes
I expereinced this laggy desktop Figma when I updated my graphics Driver. Turning Off the “Background Application Max Frame Rate” option in Nvidia Control Panel fixed it for me.
1 Like
Hey there, it appears I don’t have a “Library/Application Support/Figma Support” folder - is there some other option for Mac users?
Hey Alex,
Hmm this looks odd. Can you make sure that you:
- Quit the Figma desktop app
- Open Terminal.app and enter the following command:
rm -rf “$HOME/Library/Application Support/Figma”
and not $HOME/Library/Application Support/Figma - Try opening the desktop app again
Let me know if it works!
1 Like
Any luck on this? Why does Adobe kill everything?
2 Likes
It is not working…
Stuck here…
If it still doesn’t help, please reach out to our support team
(with URL link to the file which is effected, share a quick screen recording or screenshots demonstrating this issue and precise if this is happen in the browser, desktop app or both) so they can investigate further here: https://help.figma.com/hc/en-us/requests/new?ticket_form_id=360001744374
Please make sure you use the email associated with your Figma account, include links to the file in question, and share access with support-share@figma.com. Don’t worry, inviting us to view your file won’t impact your billing.
Thanks,
Toku
1 Like
Hi all, is Figma under any update or why it’s lagging so much? I do not have large components yet I have just started the project. I can not make a 3 layer side navigation with nested components… I have done dropdown variants for navigation, but prototyping does not work on every item… and Figma is lagging so much even can not struggle with micro animation of burger menu on hover. making it slowly and stack. Please help, I have cleaned app cahs already still no results
Hi Figma, Same problem Im facing at my end, whenever I try to switch between pages or reload project file it take a tons of time to load and keep stuck on loading animation of Figma, Please fix this issue 
1 Like
Hi everyone,
Thanks for reaching out to the community and sorry for the troubles!
As mentioned, if the workaround doesn’t help, please reach out directly to the support team so they can investigate further your issue by filling this form here. This will help us to identify the root cause of your issue.
Another workaround would be also to reduce memory usages in files. As reminder, Figma is a browser-based app, which means it’s subjected to a 2GB available memory limit that applies to each browser tab, including those in our Desktop App. When loading or editing Figma files nears or exceeds this memory limit, it can cause performance issues like long load times or crashes.
If loading a file exceeds the browser’s available memory, you will need to restore a previous version of this file from the file browser. Here’s how to do this:
- Hold down the modifier keys and click on the file in the file browser
- Mac: ⇧ Shift ⌃ Control ⌥ Option
- Windows: Alt Shift
- Select Restore from version.
- Click Restore next to the appropriate version
You may need to go back to more than one version to find one that loads.
Once you’re able to load your file, our Help Center article on how to Reduce memory usage in files has helpful information on how to avoid hitting this limit again. You can find the tips: here. Hope this helps!
It’s not in the “top toolbar”, it’s in the top tab bar. For Windows
It isnt getting better likewise, exactly after the update, its like Figma working in 0.25x
1 Like
I’m using Figma desktop app on MacOS and am having similar performance issues with lag. It works fine in Chrome browser. After trying to troubleshoot with the suggested solutions, I think there are only workarounds.
This appears to be some compatibility issues with MacOS display settings for external monitors under scaled resolutions and how Figma renders in the app.
- You can set the resolution to 1920x1080 and it’ll work fine.
- You can also try a ‘low resolution’ scaled resolution and it won’t lag.
This happens in Figma design files and FigJam.
What I noticed is the Menu UI works fine but anything in the canvas lags. Hope that helps narrow down the Figma dev team to fix this issue.
Thanks.
1 Like
I totally concur. I’m using Mac desktop. Was super laggy. I switched my secondary monitor to 1920x1080, and now it works fine. Thank you Rudy!
I’m experiencing this exact same issue and it’s almost unworkable. A scaled 4k resolution and the mouse lag on the Figma canvas is horrible. And I don’t experience in any other system or application.
Setting it to a low resolution, or my monitors unscaled resolution (around 3800px) the issue no longer occurs. But either end of those resolutions are not usable for any UI work.
1 Like