Live check
Is Figma down right now?
Observed from Figma’s public feed by our independent monitor. Always confirm operational decisions on the official status page.
While you wait: the Figma incident checklist
- Scope which surface is failing. Figma's status page splits the editor, real-time multiplayer, file loading, authentication/SSO, and Dev Mode. 'Figma is slow' during a multiplayer incident is a very different problem than files not opening at all.
- Protect in-flight work. Figma autosaves to the cloud, but if sync is degraded your recent local changes may not have persisted. Avoid closing or hard-refreshing the tab on a file with unsynced edits until sync recovers.
- Separate auth from editing. Auth/SSO incidents block new logins while already-open sessions keep editing. If people can't get in but those already inside are fine, it's the auth component — not the editor.
- Unblock engineering handoff. If Dev Mode, inspect or the API is degraded, developers can't pull specs or assets. Have an out-of-band way to share the one screen they need rather than blocking the whole build.
- Don't fight a CDN incident. Missing images, fonts or thumbnails usually mean the asset/CDN path, not your file. Reloading in a storm won't help and adds load — wait for the component to recover.
What breaks when Figma has issues
A Figma incident is mostly an internal-productivity outage, not a customer-facing one: design work stalls, real-time collaboration freezes, comments and reviews stop, and engineering handoff via Dev Mode or the API blocks mid-sprint. Org SSO incidents lock people out entirely. The sharp edge is unsynced work — a hard refresh during a sync incident can lose local changes — so the safe move is to wait rather than force it.
FAQ
Is it Figma or my network?
Check status.figma.com. If the editor and multiplayer components are green, test another site and your own connection — a single user stuck while Figma is healthy is usually local network, VPN or a browser extension.
Will I lose unsaved work during an outage?
Figma autosaves to the cloud, so synced work is safe. The risk is edits made while sync is degraded — don't close or hard-refresh the tab until the multiplayer/sync component recovers.
Are plugins and Dev Mode affected?
They can be — plugins and Dev Mode depend on Figma's API and platform. If that component is degraded, inspect, code export and plugin actions may fail while basic viewing still works.
Can I keep working offline?
Only in a limited way. Figma is cloud-first; an open file may stay editable briefly, but new files, sharing and sync need the service. Treat offline as a short grace period, not a workflow.
Put Figma’s status in your toolbar
Is it you — or your vendor? You checked once. The extension watches Figma and the rest of your stack continuously — badge, popup and Side Panel, free for 5 vendors, no account.
Add to Chrome — free, no accountNot an outage? Track API changes before they become incidents.
VendorStatus shows when a dependency is failing now. Breakwater watches official developer changelogs and migration deadlines locally in your browser, so your team can plan the change before the next deploy.
Also on your stack?
Not affiliated with Figma. Status data comes from their public status page.