Designers · problem and fix
Why is my Figma file so slow on Mac? Causes and fixes for 2026
Your Figma file is slow because the desktop app caps how much memory each open file can use. Figma says the active memory limit is 2GB per browser tab, and that the limit also applies to the desktop app. Big files reach that line through hidden layers, too many variants, heavy images and many pages.
The short answer
- Figma's desktop app runs each open file like a browser tab, with a 2GB active memory limit.
- At 90% memory, Figma shows a red alert you cannot dismiss. At 100%, the file locks.
- Most slow files carry hidden layers, duplicate variants, large images or too many pages.
- Read the memory meter and Activity Monitor before you change anything, so you can measure each fix.
- Most fixes cost nothing. Remove weight first, split files second, and reset the cache last.
What large figma file lags or crashes costs you
Hours lost to waiting
A file that costs you 10 minutes a day adds up. Over 250 workdays, that is about 42 hours. The BLS May 2025 median of $30.27 an hour for graphic designers prices that time at roughly $1,260 a year. The 250-day count is an assumption you can change.
Changes lost in a lock
At 100%, Figma locks the file and you cannot edit. Work that has not synced yet is the real risk. Figma's cache article does not mention unsynced changes, so do not assume a reset is safe. A few minutes of checking can save an afternoon of rebuilding.
Copies that drift apart
Teams often split a slow file by duplicating it. Two copies of a library drift apart over a few weeks. Someone updates one copy, and the other stays old. Splitting by copy only works if you keep one source of truth, so plan the split before you copy anything.
Stalls that break your focus
Nielsen Norman Group lists 1.0 second as the limit for keeping a user's flow of thought uninterrupted. A file that stalls on every drag breaks that limit again and again. You stop noticing the stall, and that is the expensive part.
Why it happens
The 2GB per-tab memory cap
Figma's help center says the active memory limit is 2GB per browser tab, and that the limit also applies to desktop apps. The desktop app is built on Chromium, so each open file behaves like a web page with its own budget. The limit can vary by device. A file that runs fine alone can lock once you add the libraries and images it pulls in.
Hidden layers that still load
Figma calls hidden layers a big contributor to memory usage. A hidden layer is still part of the file, so it still counts toward memory. Designers hide options during reviews and forget them. Months later, the file carries many shapes nobody can see.
Variants loaded as separate components
Figma says it loads every component in a set. A set with every size, state and icon combination creates many variants, and each one adds weight. Boolean component properties can switch an icon or label on and off without a new variant, which keeps the set small.
Heavy images and large imports
Figma's memory article says high-resolution images can cause performance or memory issues. Large imports of text, images and complex vectors with many points add weight too. A camera photo placed at full size costs far more than the small version your layout shows.
Many pages and stacked files
Figma says many pages can cause performance issues. A file that holds a year of explorations, a moodboard and a finished flow loads a lot when you open it. Several heavy files open as tabs add their memory together. Shiny measured three complex files at roughly 3 to 5 GB.
Limited RAM on the Mac
On an 8 GB Mac, Figma and your other apps compete for the same memory. Shiny says an 8 GB Mac may swap memory to the SSD, which slows everything. A 16 GB Mac rarely feels strain from these files, according to the same blog post.
How to fix it
These work with or without any app.
Delete hidden layers and dead variants
Open the layers panel and find the layers you hid. Delete any you no longer need. Keep old options in version history instead of the live file. Figma calls hidden layers a big contributor to memory usage, so this is often the fastest drop on the meter.
Use boolean component properties
Replace extra variants with boolean component properties. Figma recommends boolean properties that toggle visibility, instead of extra variants and layers. Turn one icon into a true or false property. Test the component on a scratch page before you delete the old variants.
Split pages into separate files
Copy a page, paste it into a new file, and check that the new file opens. Then delete the page from the original. Figma's help center describes this copy, paste and delete path. Move one page at a time, and keep the original file until the new one proves stable.
Split big libraries without breaking links
Figma's help center says a library can be split into smaller libraries without breaking instance links. Start with the component groups that change least. After you split, open a file that uses the library and confirm the instances still point to the main component.
Shrink images before they reach the canvas
Use the Downsize plugin, which Figma's help center names for compressing large images on the canvas. You can also shrink images in Photoshop first. Choose File > Export > Export As, set the size to the largest size your layout shows, and export a JPEG or PNG.
Open with thumbnails only or a lighter version
If the file locks, add ?thumbnails-only=1 to the end of the file URL. Figma opens it with low-resolution images, so you can reach the file and remove weight. You can also restore a version that uses less memory from version history, as Figma suggests.
Reset the cache as the last step
If the app stops responding, clear the desktop cache. Figma's path is Help > Troubleshooting > Reset Figma and Restart. Use the Terminal route only if the app stays frozen. Confirm your changes have synced first, because the article does not cover unsynced edits.
Most slow Figma files run into the same limit. The desktop app gives each open file a memory budget, and a big file runs into it. Figma's help center says the active memory limit is 2GB per browser tab. The limit can vary by device, so your Mac may hit it sooner than a colleague's. The good news is that most fixes cost nothing. You remove what the file does not need, split what is too big, and shrink images before they land on the canvas.
What a slow Figma file costs you
Lag costs more than annoyance. Nielsen Norman Group lists 0.1 second as the limit for feeling that a system reacts instantly. It lists 1.0 second as the limit for keeping your flow of thought uninterrupted. A file that stalls for a second on every drag breaks that flow again and again. You stop noticing after a week, and that is the expensive part.
Put a rough number on the time. The U.S. Bureau of Labor Statistics reports a May 2025 median pay of $62,960 a year for graphic designers, or $30.27 an hour. Say your file costs you 10 minutes a day in waiting and retries. Over 250 workdays, that comes to about 42 hours. At the median hourly rate, that is roughly $1,260 a year. The 250 workdays figure is my assumption, not a BLS number, so swap in your own days and rate.
Why Figma gets slow on a Mac
Figma's desktop app is built on Chromium, the engine behind many browsers. A Shiny blog post updated in April 2026 explains that each open document runs as a web page with its own rendering process. In Activity Monitor, these show up as Figma Helper (Renderer) processes. That is why the app behaves like a browser tab, and why its memory limit works like one too.
| Memory level | What Figma shows | What it means for you |
|---|---|---|
| Below 90% | No red alert in the left sidebar | Normal editing. Keep an eye on the meter. |
| 90% | A red alert tile that you cannot dismiss | The file is close to its limit. Remove weight now. |
| 100% | The file locks and reports no memory available | You cannot edit. Restore a lighter version or open with thumbnails only. |
File size changes the numbers. Shiny measured one simple Figma document at about 500 MB to 1 GB across all processes. A complex file with component libraries reached about 1 to 2 GB. Three complex files open as tabs used roughly 3 to 5 GB. These are one blog's tests, so treat them as a guide and check your own Mac.
2GB
Active memory limit per browser tab in Figma, which also applies to the desktop app
Reduce memory usage in files: Figma Help Center90%
Memory use where Figma shows a red alert tile in the sidebar that you cannot dismiss
Reduce memory usage in files: Figma Help Center3 to 5 GB
Memory used by three complex Figma files open as tabs, in one Mac blog test
Figma on Mac: why 'Helper (Renderer)' eats RAM (Shiny)$30.27
Median hourly pay for graphic designers in May 2025, per the U.S. Bureau of Labor Statistics
Graphic Designers: Occupational Outlook Handbook, U.S. Bureau of Labor StatisticsRAM matters too. Shiny says a 16 GB Mac rarely feels strain from these files. An 8 GB Mac may swap memory to the SSD, which slows everything, not only Figma. You do not need a new Mac to fix a file. You do need to know where you start, so you can tell whether the file or the machine is the problem.
Check the memory meter before you change anything
Start with a number, not a guess. Figma has a built-in memory meter, and macOS has one too. Use both. Then you know whether the file is heavy, or whether the whole Mac is short on memory.
- In Figma desktop, choose View > Memory usage to turn the meter on.
- Open Manage memory and enable Show memory in layers panel, so memory shows up next to your layers.
- Press ⌘ Space, type Activity Monitor, then open the Memory tab.
- Read the memory pressure graph. Green means fine. Yellow means the Mac may need more RAM soon. Red means it needs more RAM now.
Apple's Activity Monitor guide describes those colors the same way. Green means the Mac uses its RAM efficiently. Yellow means it might eventually need more. Red means it needs more now. If Figma's meter climbs toward 90% while the Mac graph stays green, the file is the problem. If both go red, close other apps first, then run the check again.
Causes: hidden layers, variants and heavy images
Hidden layers are the quietest cost. Figma's help center calls them a big contributor to memory usage. Hiding a layer with the eye icon keeps it in the file. It still counts toward the file's memory, so it still adds weight. Designers hide options during a review and forget them for months. Then the file carries shapes nobody can see.
Component variants add up fast. Figma says it loads every component in a set. A set with every size, state and icon combination can hold many variants. Each one adds weight, even when you only use two of them. Boolean component properties can switch an icon or label on and off without a new variant.
Large images are the next big cost. Figma says high-resolution images, many pages and large imports can cause performance or memory issues. Imports include text, images and complex vectors with many points. A camera photo placed at full size costs far more than the small version your layout shows. Shrink it at the source, not in the canvas.
Pages and stacked files are the last big cause. Figma says many pages can cause performance issues. A file that holds a year of explorations, a moodboard and a finished flow loads all of it when you open it. Several heavy files open as tabs add their memory together. Shiny's three-file test shows how quickly that total climbs.
Fixes you can do today without buying anything
Work from the lowest risk to the highest. Deleting dead layers is safe if you keep version history. Splitting files takes longer. Start with the quick wins, then read the meter again. Each step should lower the number you wrote down earlier.
Remove hidden layers and extra variants
Open the layers panel and find the layers you hid. Delete any you no longer need. Keep old options in version history instead of in the live file. For variants, Figma recommends boolean component properties to toggle visibility, instead of extra variants and layers. One icon toggle can replace two separate icon variants. Test the new component on a scratch page before you delete the old variants.
Split pages and libraries into separate files
To move a page, copy its contents, paste them into a new file, and check that the new file opens. Then delete the page from the original. Figma's help center describes this copy, paste and delete path. Libraries can also split into smaller libraries without breaking instance links, according to the same article. Check instances in other files after you split. Move one page first, then the rest.
Shrink large images before they reach the canvas
Figma's help center names the Downsize plugin for compressing large images on the canvas. You can also shrink images before import. In Photoshop, choose File > Export > Export As, set the size to the largest size your layout shows, and export a JPEG or PNG. Export retina detail only where the layout needs it. Smaller source files mean less memory for every collaborator who opens the file.
Open with thumbnails only or a lighter version
When a file locks, you can still reach it. Add ?thumbnails-only=1 to the end of the file URL. Figma opens the file with low-resolution images, so you can remove weight. You can also restore a version that uses less memory from version history. Work in the restored copy, and keep the original untouched until the fix holds. The restore steps for a previous version cover that route.
Reset the Figma cache as the last step
If the app stops responding, clear the desktop cache. Figma's help center suggests the built-in route first. In Figma, choose Help > Troubleshooting > Reset Figma and Restart. Only if the app stays frozen should you force-quit it, open Terminal, and run rm -rf "$HOME/Library/Application Support/Figma". Then relaunch Figma and check the meter.
Mac RAM and what to expect with big files
| Mac or setup | Typical load in the test | What to expect |
|---|---|---|
| 8 GB Mac | Three complex files as tabs use about 3 to 5 GB | May swap memory to the SSD, which slows the whole Mac. Close tabs first. |
| 16 GB Mac | Same kind of tab load | Rarely feels strain, according to the same post. |
| Any Mac, one complex file | About 1 to 2 GB with component libraries | Lower risk when it is the only file open. |
More RAM is a long-term help, not a first step. Figma says the limit can vary by device, so a bigger Mac may not change a file that hits its cap. Fix the file first. Then check whether the Mac still swaps when you work.
Mistakes that make it worse
- Hiding layers instead of deleting them. Hidden layers still count toward memory, so the meter stays high.
- Keeping old versions of a file open as tabs. Each open tab adds its memory.
- Resetting the cache first. It skips the cheap fixes and can put unsynced work at risk.
- Shrinking images by eye inside Figma. Resize them at the source so the output stays predictable.
- Blaming the Mac before reading Activity Monitor. Read the graph first, then decide.
- Splitting a library without checking the instances in other files.
Watch for the recovery step. Figma's help center says a locked file leaves recovery mode only after memory drops below 90%. If you see the lock, close other tabs, remove weight from the file, and check the meter again. Repeating the same action rarely helps, so reduce the file instead.
Where Lazur fits in this routine
Lazur is a voice assistant for the Mac. Hold ⌥ ⌘ to ask about anything on screen, and Lazur answers out loud. If you cannot find the memory panel, ask where it is. Lazur draws a circle and a label around it. For step-by-step help, ask Lazur to guide you. It guides one click at a time and waits for each click. Lazur does not click for you, so you still make each change.
Lazur can also start a cleanup timer by voice, since timers are one of its everyday actions. Hold fn to dictate a checklist at the cursor, such as the layers to review. Lazur can draft a short note to your team, and you review it before you send. It does not edit your Figma file or delete layers.
How to tell the fix worked
After each change, read the meter again and compare it with your first reading. A drop in Figma's memory number means the change helped. If the number does not move, the cause may sit somewhere else, often in open tabs or another heavy file. Write each reading next to the change you made. That log shows which fix mattered, and it makes the next slow file easier to diagnose.
What to do next
Start with the meter today. It takes five minutes and shows where the weight sits. If the file needs a lighter copy, read how to restore a previous version in Figma. For the rest of your Mac setup, see the Figma guide for designers. When you want voice help while you work, see Lazur pricing.
Faster with Lazur
Where Lazur helps with large figma file lags or crashes
Hold ⌥ ⌘ and say what you want. Lazur sees your Figma window. Lazur draws a circle and a label around the button or menu you need.
- 1
Hold ⌥⌘ and talk
- 2
Lazur draws a circle and a label around the button or menu you need.
- 3
You stay in Figma. Nothing to copy into a chat window.
More things to say in Figma
- “Where is the memory usage option in Figma?”
- “What does this memory number mean?”
- “Walk me through turning on the memory meter.”
- “Set a timer for the layer cleanup.”
- “Hold fn and dictate my list of layers to review.”
- “Draft a note to my team about splitting the file.”
Free for 3 days, then $18/month. Download for Mac
You say“Where do I turn on memory usage in this file?”
Lazur · points at itLazur circles the View menu and labels Memory usage, so you know where to click.
What designers say to Lazur for this
Each one is a single hold of ⌥ ⌘.
“Where is the memory usage option in Figma?”
Lazur circles the View menu and labels the item, so you know where to click. You make the click yourself.
Points at it
“What does this memory number mean?”
Lazur reads what is on your screen and answers out loud in plain words, such as what the red alert means.
Explains what's on screen
“Walk me through turning on the memory meter.”
Lazur guides you one click at a time and waits for each click before it moves on.
Walks you through it
“Set a timer for the layer cleanup.”
Lazur starts the timer by voice. You still do the cleanup in Figma yourself.
Handles the small stuff
“Hold fn and dictate my list of layers to review.”
Dictation goes in at the cursor in any app. Clean text lands where you are working, so you can paste it into a checklist.
Types what you say
“Draft a note to my team about splitting the file.”
Lazur drafts and types the text for you. You review it and decide what to send.
Drafts it
A plan you can start this week
- Day 1
Read the meter
Turn on Memory usage, then note the number with the file open. Time one slow action, such as moving a frame, and write the seconds down as your baseline.
- Day 2
Strip the file
Delete hidden layers and dead variants. Check the meter after each batch you remove, not only once when you finish the session.
- Day 3
Convert variants
Replace duplicate variants with boolean component properties. Test each component on a scratch page before you delete the old variants.
- Day 4
Shrink images
Export the largest photos at display size from Photoshop, then replace them in Figma. Read the meter again and log the change.
- Day 5
Split one page
Copy one page into a new file, check the instances, then delete it from the original. Split more only if the meter stays high.
- Day 6
Keep a lighter copy
If the file still locks, restore a lighter version from version history into a copy. Leave the original untouched until the fix holds.
- Day 7
Reset as a last step
If the app still hangs, confirm your changes have synced, then use Help > Troubleshooting > Reset Figma and Restart before any Terminal command.
Questions people ask
Why is my Figma file slow only on my Mac?
The desktop app runs each file in a Chromium-based process with a memory cap. Your Mac's RAM, your open tabs and your other apps change how close you get to that cap. Read the memory meter, then compare the same file on another machine if you can.
What does the red alert in Figma mean?
At 90% memory, Figma shows a red alert tile in the left sidebar that you cannot dismiss. At 100%, the file locks and reports no available memory. Remove hidden layers and split pages before you reach that point.
Does resetting the Figma cache fix a slow file?
Sometimes, when the app stops responding. Figma's help center says to use Help > Troubleshooting > Reset Figma and Restart first. Confirm your changes have synced before you delete anything, because the article does not mention unsynced work.
Will more RAM fix a slow Figma file?
It can help the whole Mac, especially on 8 GB machines that may swap memory to the SSD. Figma says its limit can vary by device, though, so more RAM may not change a file that hits its cap. Fix the file first.
Is the Downsize plugin the only way to shrink images?
No. You can export smaller images from Photoshop with File > Export > Export As before you place them in Figma. Figma's help center names the Downsize plugin as one option for compressing images on the canvas.
Should I delete old pages to make the file faster?
Move them first. Copy a page into its own file, check that the new file opens and the instances still work, then delete the page from the original. Keep the original file for a while as a backup.
Can Lazur fix a slow Figma file for me?
No. Lazur does not click buttons, edit files or operate other apps for you. It can point at the memory panel, guide you one click at a time, and answer questions out loud while you work.
Sources
- Reduce memory usage in files: Figma Help Center · Figma · checked 2026-11-07
- Clear the Figma desktop app cache: Figma Help Center · Figma · checked 2026-11-07
- Figma on Mac: why 'Helper (Renderer)' eats RAM (Shiny) · Shiny (Theodore) · checked 2026-11-07
- Check if your Mac needs more RAM in Activity Monitor, Apple Support · Apple · checked 2026-11-07
- Graphic Designers: Occupational Outlook Handbook, U.S. Bureau of Labor Statistics · U.S. Bureau of Labor Statistics · checked 2026-11-07
- Response Times: The 3 Important Limits, Nielsen Norman Group · Nielsen Norman Group · checked 2026-11-07
Fix large figma file lags or crashes with Lazur, free for 3 days
Hold a key and ask. Lazur sees your screen, points at the button and talks you through it, in any Mac app. No credit card.