Figma Out of Memory in Chrome? 5 Fixes That Work (2026)

You are mid-edit in Figma when a Figma out of memory warning in Chrome stops the canvas — the frame you were placing is stranded, and the usual loop of closing tabs, reloading, and restarting Chrome starts again. Figma’s guidance points to a 2GB active memory limit per tab, so separate file-side pressure from machine-side pressure first.

Fix 1: Recover the File With a Lighter Load

Open the file URL with ?thumbnails-only=1. Figma’s memory guidance says that query parameter loads the file with low-resolution images. Use it when the file is large, because the lighter image load can restore canvas access while you inspect the file.

If the tab is already dead, reload once first. A single reload can restore the session when the error was a one-off event on an otherwise healthy setup. If the file is consistently heavy, the reload is a bridge while you cut the file-side load in Fix 2.

If Figma’s recovery path says the browser version is not supported, update Chrome or open the same file in the desktop app. The desktop route is a separate recovery path, so use it while the browser warning is tied to the version.

Match the Error to the Pressure Side

Use this diagnostic before closing random tabs. The right first move changes with the pressure source, so match the symptom to the side first.

The table keeps the file-side route first. A consistently heavy file is not solved by suspending other tabs, even when the browser itself is under pressure.

A reload can still be the whole fix when the session is otherwise healthy. It does not repair a file that is consistently heavy, but it puts you back in the canvas while you identify the actual pressure source.

Fix 2: Cut What the File Is Loading

Figma’s own memory guidance names the file-side drivers that usually push a tab toward the ceiling: hidden layers, component count, variant count, page count, and high-resolution images. Hidden layers still store and render information even when they are not visible, so hiding a group leaves information loaded in the file.

The heaviest part is often hidden. Delete layers that are not part of the active design, and move frames that are rarely used into a separate file instead of keeping them as extra pages.

Start with the parts of the file that do not need to stay loaded. Reduce components and variants where component properties can carry the variation, and split a large file into smaller files when one file carries many pages or lots of high-resolution images.

A split file lowers the standing load. It also makes the next recovery easier, because the tab is carrying one working set of frames instead of the entire archive.

Fix 3: Use Chrome’s Built-In Memory Saver

Freeing other tabs does not raise the 2GB active memory limit on the Figma tab that is already close to it. The built-in path helps when system-wide memory pressure is making several tabs struggle at once. It does not help a single file.

Chrome’s Memory Saver deactivates tabs you are not using, and it automatically reloads them when you access them. To keep the design tab from being deactivated, add it to the Always keep these sites active exclusion list.

The Chrome support page describes the three Memory Saver levels in relative terms — no minute value and no recovered-memory figure is published. Choose the level that matches your tab habits, then verify that the design site is excluded from deactivation.

If your session is mostly a few important tabs, Chrome’s native setting may be enough. If the error came from one heavy file, move back to Fix 2 first, because the file-side load is the constraint.

Fix 4: Release Idle Tabs on a Timer

SuperchargePerformance suspends idle tabs with chrome.tabs.discard() — that call ends the renderer process for the suspended tab, and the browser keeps only the tab entry. The suspended tab releases roughly 90-95% of its own RAM, and the scope of that figure is per discarded tab. The low and medium tiers suspend after 15 and 5 minutes, while the PRO tier is user-set in seconds.

The per-tab scope makes this step a machine-side move. It reduces demand from other tabs while the active Figma tab remains outside the automatic-discard path.

Thirty-four web-app domains are auto-protected from suspension, and figma.com is one of them. The design tab is exempt from automatic discard, but that exemption does not make the Figma tab perform better, load faster, or survive a memory event.

Treat the timer as a machine-side reduction in demand from other tabs.

Fix 5: Update Chrome or Switch to the Desktop App

Chrome 154 is the current stable milestone as of September 2026. If Figma’s recovery mode tells you the browser version is not supported, update the browser first, then reload the file. If the file still will not recover, open the same file in the Figma desktop app.

The desktop app is a separate recovery route when the browser warning is tied to the version. Use it to continue while you reduce file-side weight, because it keeps the working file accessible while the browser path is repaired.

Read the 2GB Limit Correctly

Treat the 2GB figure as the ceiling that Figma’s guidance associates with a browser tab. Figma’s guidance notes that the limit can differ across devices, so treat 2GB as a general figure rather than an exact threshold for your machine.

That distinction is why the diagnostic table forces you to separate one bad file from a crowded browser. The same warning can point to a heavy file, a crowded tab set, or a one-off allocation that a reload clears.

Pick the Branch That Matches Your First Test

If the problem follows one file, use the file-side route from Fix 1 through Fix 2. Browser-side tooling does not change that file’s load. The file edit is the durable fix.

If every heavy tab struggles and your session carries many tabs, use the idle-tab release route from Fix 3 and Fix 4, with figma.com excluded from automatic discard. The native saver and timer reduce surrounding demand.

If the error was a single one-off event on an otherwise healthy setup, a reload is the whole fix and nothing further is needed. Stop there.