Why is Figma using so much memory and CPU on my Mac?
Last reviewed: 19 November 2026.
Figma loads the whole design file, its images, components and layers, into memory and draws it with WebGL on the GPU, so large files with many frames and high-resolution images use the most memory and make panning and zooming slow. Figma measures each file's memory use against what is available and shows warnings at 60%, 75% and 100%, locking the file at 100%. Splitting large files and closing unused Figma tabs are Figma's main recommendations.
How does Figma measure memory?
Figma's troubleshooting guidance describes an active memory limit of 2 GB per browser tab, which can differ between devices, and shows memory use as a percentage of available memory. Banners appear at 60% and 75%; at 100% Figma locks the file and tells you there is no available memory.
In Activity Monitor, the Figma desktop app's total is the sum of its own process and its helper processes. Each open file adds to it.
Why is Figma slow or busy?
- Large files. Many pages, frames, component instances and images in one file.
- Visual extras. Figma lists multiplayer cursors, layout guides and effects among the things you can turn off to improve performance.
- Many open tabs. Each open file keeps its contents loaded.
- Network. Figma notes that unreliable connections cause slow file loading and lag when panning and zooming.
How do you reduce Figma's memory and CPU use?
- Close Figma tabs you are not using. Each open file holds its own memory.
- Turn off visual extras. Hide multiplayer cursors, layout guides and effects while you work on a heavy file.
- Split large files. Move pages or sections into separate files. Figma names this as the way to bring a file's memory use down.
- Restart or reset the desktop app. Force quit Figma and reopen it. If the app is unresponsive, Figma documents clearing its cache by quitting it and running
rm -rf "$HOME/Library/Application Support/Figma"in Terminal; if the app still responds, use the reset option in its Help menu instead.
When should Figma's resource use concern you?
Memory banners on a specific file are a sign that the file has grown too large rather than a problem with the Mac. High CPU with a small, simple file open is not typical: check that WebGL is working (Figma requires it) and that a browser extension is not interfering if you use Figma in a browser.
How can Thrum help with Figma?
Thrum's Memory tab shows memory pressure, swap, and the eight processes using the most memory, so you can see how much Figma holds and whether the Mac is short of memory. An optional alert tells you when memory pressure turns critical. Click Figma in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.
Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.
Questions
What happens when a Figma file reaches 100% memory?
Figma locks the file and tells you there is no available memory. Splitting the file into smaller files is the fix.
Does Figma need the GPU?
Figma runs on WebGL, which must be enabled. It uses the GPU to draw the canvas.