Figma tends to break at the worst possible moment — usually while you're sharing your screen and a client is watching. The canvas won't load, the file opens grey and stays grey, or "Connection lost" appears mid-edit and your colleagues' cursors freeze in place. And because Figma runs in a browser, the same file can be perfect in one browser and broken in the one next to it.

That is the key to fixing it. Figma is not a local application with a file on your disk: it's a browser app that keeps a permanent connection to the server and streams every change through it, and it leans hard on your GPU to render the canvas. So this guide is organized by browser — Chrome, Firefox, Safari — plus the Mac desktop app and the iPad, followed by the two problems nobody's checklist covers: "Connection lost" and fonts that refuse to show up.

Why is Figma not working? Find the layer that's actually broken

Figma sits on four layers, and each fails in a recognizable way.

Symptom Layer First thing to try
Canvas is grey or blank, UI works GPU / WebGL rendering Check hardware acceleration, update the browser
Infinite loading spinner at sign-in Extensions, cookies, tracking protection Test in a private window with extensions off
"Connection lost", cursors freeze Persistent connection to the server Check the network path, see the section below
Editor is sluggish, dragging lags Latency, or a very heavy file Close other file tabs, check file size
Installed fonts don't appear Font access, not the network Figma Agent in the browser, restart the desktop app

Before anything else, check status.figma.com. If there's an open incident, nothing local will help. Then try the same file in a different browser: that one test separates a browser problem from a network problem in thirty seconds.

Figma not working today: outage, file, or your connection?

Three checks, in order. First, the status page. Second, open a small, simple file — if a lightweight file works and a big one doesn't, you have a performance problem, not a connection problem: heavy files with thousands of layers, large embedded images and dozens of components will exhaust the browser's memory.

Third, switch networks — a phone hotspot is ideal. If Figma is stable on mobile data and unstable on your office network, the problem is that network: corporate proxies and filters frequently mishandle the long-lived connections Figma depends on. The tell-tale sign is "fine at home, broken at the office."

Figma not working in Chrome

Chrome is Figma's best-supported browser, which also makes it the one where problems are most often self-inflicted.

  1. Update Chrome. Figma requires a recent version — roughly Chrome 120 or newer for the current editor, and newer still for shader features. An old browser is the single most common cause of a blank canvas.
  2. Check WebGL. Open chrome://gpu. If WebGL is listed as software-only or unavailable, the canvas will not render. Then check chrome://settings/system → Use graphics acceleration when available → on, and restart.
  3. Turn extensions off. Ad and tracker blockers, privacy extensions and browser VPN extensions all interfere with Figma. Test in an Incognito window with extensions disabled; if that works, re-enable them one at a time.
  4. Clear site data for figma.com — padlock icon → Site settings → Delete data. Fixes stuck sign-in loops.
  5. Close spare Figma tabs. Each open file holds its own connection and its own chunk of memory; five heavy files in five tabs will crash the tab you care about.

Figma not working in Firefox

Firefox works, but two of its privacy features regularly break the editor.

  • Enhanced Tracking Protection in Strict mode blocks resources Figma needs. Click the shield in the address bar and turn protection off for figma.com specifically.
  • Resist Fingerprinting (privacy.resistFingerprinting in about:config) restricts canvas and WebGL access and will leave you with a grey canvas. If you enabled it, add an exception or turn it off while using Figma.
  • WebGL check: open about:support, Graphics section. Software rendering means poor performance or no canvas at all; update GPU drivers and confirm webgl.disabled is false.
  • Version matters: Figma expects a current Firefox — 128 ESR or later. Older builds aren't supported and misbehave in ways no setting fixes.

Figma not working on Safari

Safari is supported from version 17.4 up, so the first fix is a macOS/Safari update — older Safari is simply out of scope.

After that, three Safari-specific settings. Prevent cross-site tracking (Settings → Privacy) can break sign-in and plugin windows; turn it off for testing. Lockdown Mode disables web technologies Figma relies on, so it must be off. And iCloud Private Relay occasionally interferes with long-lived connections — disable it briefly to test. If Safari keeps struggling with a heavy file while Chrome handles it, that's a real difference in GPU-side performance, not something you can configure away.

Figma not working on Mac

On macOS you have two options — the browser and the desktop app — and they fail differently. The desktop app is the same web app in its own window, with one important addition: direct access to your local fonts.

If the app won't open but the browser works, reinstall it from the official site; it may be stuck on an old build. If both fail, the problem is the network or the account. Also worth checking: macOS 11 or later is the supported floor, and the canvas depends on the GPU — if you're driving several external displays on an older Mac, sluggishness in a big file is a hardware limit, not a bug. Clearing the app's cache from the Figma menu and restarting is the quickest generic fix.

Figma not working on iPad

Set expectations first, because most "not working" reports on iPad are about capability, not faults. Figma's tablet experience is built around viewing, presenting, commenting and FigJam — not the full design editor you get on a desktop OS. An iPad can open files and comment; it isn't the place to reorganize a component library.

If viewing itself fails: update iPadOS and the app, close other apps to free memory, and check the file size — very heavy files may not open on a tablet at all.

"Connection lost" and why Figma needs an uninterrupted connection

Figma keeps an open WebSocket connection to its servers. Every drag, every property change, every cursor movement is sent up that channel in real time and pushed out to everyone else in the file. That's exactly how multiplayer cursors and live collaborative editing work — and it explains two things.

First, Figma needs a continuous connection far more than a fast one. Five seconds of instability you'd never notice on a normal web page is enough to drop the socket and show "Connection lost." Second, latency is felt directly: "the editor is laggy" is usually the round trip to the server, not your computer's CPU.

Your work isn't lost the instant it happens — the editor holds recent changes locally and reconnects, and the file lives on the server. But long disconnects during collaborative sessions are where version conflicts genuinely occur. If "Connection lost" is a daily event, that's a network-path symptom, not an account problem.

Figma not showing installed fonts

A different problem that wastes just as much time. In the browser, Figma cannot see your locally installed fonts without a helper: install Figma Agent (formerly Font Installer) from the official site, then restart the browser. In the desktop app, local fonts are picked up automatically — but a newly installed font only appears after you restart the app.

If a font still doesn't show, check that it was installed for all users rather than just your account, and that it's a supported format (OTF and TTF; variable-font support is limited). Fonts in a shared file that you don't have installed will render as a substitute for you and correctly for whoever has them — that's expected behavior, not corruption.

"Figma not working" on Reddit: what it usually turns out to be

Scroll enough threads and the same four resolutions keep coming back, which tells you where to look first: an out-of-date browser; a privacy extension or strict tracking protection blocking resources; a corporate network or a VPN extension mangling the persistent connection; heavy files exhausting browser memory. A genuine Figma outage is the rarest of the four — and the status page confirms it in five seconds.

The practical lesson: run the cheapest test first. Different browser, then a private window, then another network, then the status page.

Where a VPN helps with Figma — and where it doesn't

For a tool that lives on a permanent connection, route quality translates directly into working time.

  • Continuity: the editor doesn't drop into reconnect mode in the middle of an edit, and collaborative sessions survive.
  • Lower latency: the interface responds faster and dragging keeps up with the cursor.
  • Predictability: the file opens when the client is watching.
  • Privacy: design files are someone's intellectual property and often under NDA; an encrypted connection belongs in coworking spaces, cafés and hotel Wi-Fi.

One important caveat: use a full VPN application, not a browser extension. Extensions sit inside the browser's networking and are a frequent cause of "Connection lost" — they are the problem more often than the cure. And a VPN does nothing for subscription payments, a heavy file, or an outdated browser.

How to choose a VPN for working in Figma

  • Stability over peak speed. Orris VPN runs on VLESS, which holds a persistent connection steadily instead of dropping sessions.
  • An app, not an extension. Orris installs as a full application on Windows, macOS, Linux, iOS and Android — the right shape for a tool built on WebSockets.
  • Speed headroom: up to 1 Gbit/s and unlimited traffic, so heavy files and high-resolution exports aren't capped by the service.
  • Servers in many countries — pick the closest one for the lowest latency.
  • No logs. For work under NDA that's a practical requirement, not a slogan.

From about $1.7/mo, with a free trial and payment by card or crypto. For a working tool it pays for itself the first time a client call doesn't fall apart.

FAQ

Why is Figma not working today? Check status.figma.com, then open the file in a different browser, then on a different network. Those three tests identify almost every cause within a couple of minutes.

Why is Figma not working in Chrome? Usually an old Chrome version, graphics acceleration turned off, or an extension blocking resources. Update, check chrome://gpu for WebGL, and test in Incognito with extensions disabled.

Why is Figma not working in Firefox? Strict Enhanced Tracking Protection or Resist Fingerprinting blocking canvas and WebGL access. Add an exception for figma.com and confirm Firefox is current — 128 ESR or newer.

Why is Figma not working on Safari? Safari 17.4 is the minimum. Also check Prevent cross-site tracking, Lockdown Mode and iCloud Private Relay, all of which can interfere.

Why does Figma say "Connection lost" — will I lose my work? Files live on Figma's servers, so nothing disappears. Only the most recent unsynced edits are at risk during a long disconnect. Frequent disconnects point at the network path.

Why can't Figma see my installed font? In the browser you need Figma Agent from the official site; in the desktop app, restart it after installing the font. Also install fonts for all users, not just your own account.

Why does Figma work for my colleague but not for me? You're on different networks and possibly different browser versions. The path to Figma's servers differs between providers, which is why one file behaves differently for two people.

Will a VPN fix a declined Figma payment? No. Payment methods and network routing are unrelated.

The bottom line

Figma problems split cleanly in two. Grey canvas, spinning loader, missing fonts and a laggy interface are local: browser version, WebGL and graphics acceleration, extensions, tracking protection, file weight, Figma Agent. "Connection lost", collaboration that falls apart and an editor that's fine at home but broken at the office are about the connection — because Figma lives on a permanent connection and does not forgive interruptions.

For that second half, a steady encrypted route is the answer, and Orris VPN provides one as a proper app on every device you design on — up to 1 Gbit/s, VLESS, no logs, from about $1.7/mo with a free trial.

Read next: