Figma Not Working: Fix Files That Won’t Open and Memory Errors

When a Figma file will not open, the cause is usually one of four things: you lack access to the file (or it was deleted), the file has hit its memory limit, your connection is unstable, or Figma is down for scheduled maintenance. Check status.figma.com first to rule out maintenance, then confirm you are signed in to the right account, and if a memory warning appears, reduce what the file loads. Each case has its own fix, covered below.

Why does a Figma file show a 404 page or “You don’t have permissions”?

A 404 page on a file link almost always means you do not have access to that file or that someone deleted it, according to Figma’s help page on files that are not opening. Work through these checks:

1. Make sure you are logged in to the account that was invited to the file. People with a work and a personal account often hit this.
2. Check that you accepted the invitation to view or edit the file with that same account.
3. Look in your deleted files in case the file is there.
4. Ask the file owner to give you access again.

Keep the URL of any file that gives you trouble. If you end up contacting support, they will want the link.

How do Figma memory warnings work?

Figma tracks memory as a percentage of what your browser or device makes available, and it warns you at set thresholds before locking a file. Browsers set their own active memory limit, which varies by device, but the general figure Figma gives is 2GB per browser tab. The desktop app runs on the same browser technology, so the same limit applies there.

The memory in question is WASM (WebAssembly) memory, which Figma uses to draw layers on the canvas and run multiplayer editing. Usage is counted only for pages that have loaded in a file. Figma’s general help pages list banners at 60%, 75% and 100%. The memory guide adds that at 90% a red alert tile appears in the left sidebar and cannot be dismissed. If memory climbs quickly, alerts may arrive out of order, and you might not see one at all.

At 100%, Figma locks the file and says no memory is available. If the file is big enough to crash the browser itself, Figma will not show any memory banners first.

What happens when a file is locked at 100% memory?

What you can do with a locked file depends on whether you have view or edit access:

• View access: you get the option to reload. Reloading sometimes frees enough memory to keep viewing.
• Edit access: you can also reload. If that fails, Figma prompts you to enter recovery mode, as long as your browser version supports it.

Recovery mode works in Firefox 89+, Chrome 83+, Safari 15.2+ and Microsoft Edge 93+. On an older version, Figma asks you to update the browser or open the file in the desktop app. In recovery mode every page of the file loads and the Manage memory window opens. You have to bring usage below 90% to leave recovery mode, and the file reloads when you exit. Your work is kept.

How do I check and reduce memory in a Figma file?

Turn on the memory meter, find what is heavy, and cut it. To see the meter:

1. Open the Main menu and hover over View.
2. Choose Memory usage. A meter appears in the left sidebar.
3. Click Manage memory.
4. In the Manage memory window, switch on Show memory in layers panel to see how much each layer and component uses. The same window has memory-reduction tips.

Figma says no single number of layers or components triggers the problem, but some things weigh more than others:

• Hidden layers. Figma still stores and renders them, so delete the ones you no longer need. Boolean component properties can also cut the number of variants and layers in a design system.
• Big component or variant libraries. A few component sets with thousands of variants can hit the limit, because Figma loads every component in a set. Component properties mean fewer variants to load.
• Oversized libraries. If a library is still near the limit, split it into smaller libraries. Cut and paste the components into the new file, then publish the changes; instance links stay intact.
• Files with many pages or high-resolution images. Splitting them into smaller files, for example one file per page, helps.

Jumping between pages loads the rest of their content, so the memory panel numbers can rise as you browse.

Can a slow or missing connection stop Figma files from loading?

Yes. Figma needs a reliable connection and has no dedicated offline mode. On a weak connection, files load slowly, images show in low resolution and the canvas lags when you pan or zoom. Offline, you cannot open existing files unless you opened them while online, load pages that did not load before, see collaborators’ updates, search library components, install plugins, view version history or use multiplayer features.

Figma cannot be reached through a VPN or proxy service, and some browser extensions also cause trouble. If you need a VPN or proxy, add Figma to its safe list. The same kind of connection checks apply to other cloud tools; our guide to Google Drive files that will not open or sync walks through them.

What quick fixes does Figma recommend?

The Figma troubleshooting checklist lists steps that resolve most problems:

• Close Figma tabs you are not using.
• In a browser, force-quit and reopen Figma in a new window. In the desktop app, force-quit it and restart.
• Turn off multiplayer cursors, layout guides and effects.
• Split files to lower memory use.
• Clear the desktop app cache.

Also confirm your setup. Figma supports only stable releases of browsers such as Chrome, Firefox and Safari, not beta, developer or early-access builds, so update to the latest version. Figma is built on WebGL, which must be enabled; if it is enabled and Figma still fails, a Chrome extension may be blocking it. The desktop app on Windows needs a 64-bit system and does not run on 32-bit.

What happens during Figma scheduled maintenance?

During scheduled maintenance you cannot open files on Figma.com or in the desktop app, and it lasts anywhere from 30 to 60 minutes, according to Figma’s maintenance page. Figma restarts its platform to upgrade software. During the window:

• Figma.com shows an alert that Figma is unavailable.
• In the File Browser you can see teams and files but cannot open them.
• An open file shows a red banner until maintenance ends.
• Refreshing a Figma tab cuts you off from that file, and unsaved changes are lost.

Figma does not save edits made during maintenance and marks unsaved changes with a white dot next to the file name. To let them sync once service returns, keep file tabs open, do not close your computer or let it sleep, do not rename or move the file, and save a local copy after any changes. Renames and moves will not save automatically, so make them after Figma is back. When maintenance ends, the red banner and white dot disappear and your work syncs.

How do I contact Figma support about a file that will not open?

Send a request through Figma’s Support Hub with the file link and, if you found errors, an export of the Console log. Open developer tools with Command Option I on a Mac or Ctrl Shift I on Windows; failed actions show in red in the Console. If you lost the link, right-click the file in the file browser and choose Copy link, check your browser history, or search emails, chats and other Figma files where it was shared. Support cannot see your files by default and will tell you how to share the file with them. Figma does not charge you for its employees who get access to your account.

Quick answers

Is Figma down or is it just my file?

Check status.figma.com for live service status and scheduled maintenance. If Figma is up, the problem is likely access, memory or your connection. A similar status-first approach works for Dropbox sync problems.

Does the Figma desktop app avoid memory limits?

No. It uses browser-based technology, so the same per-tab limit applies.

Why don’t I see a memory warning before a crash?

Memory can rise too fast for an alert to show, and a browser-level crash skips Figma’s banners entirely.

Will I lose work made during maintenance?

Not if you keep the tab open and the computer awake. Changes sync when Figma is back, but refreshing the tab loses unsaved changes.

Checked against official sources in November 2026. Apps, menus and error codes change: check the official help page for the current steps.