Figma Weave Can't Sign In: Step-by-Step Troubleshooting

If you are locked out of your Figma Weave developer environment, stuck in an endless authentication loop, or encountering persistent error codes during the login phase, you are dealing with a local state mismatch or an enterprise configuration block.

Because Figma Weave interfaces directly with both your Figma design space and enterprise-level directory services (like Okta, Google Workspace, or Azure AD), a minor sync failure can prevent the secure token handshake from completing. Use this independent troubleshooting guide to resolve the block and sign back in.

1. Clear Site Data and Revoke Stale Tokens

A corrupt session token stored in your browser's local storage is the most common cause of the "stuck on loading redirect" loop. A standard browser refresh does not clear these deep-level keys.

1. Open your browser and navigate to the Figma Weave login page.
2. Open your browser's Developer Tools (press F12 or Cmd + Option + I on macOS).
3. Go to the Application tab (Chrome/Edge) or Storage tab (Firefox).
4. In the left-hand sidebar, expand Local Storage and select the Figma/Weave domains.
5. Click Clear All or manually delete keys starting with auth_, token_, or session_.
6. Repeat this process under the Session Storage and Cookies dropdowns for the same domains.
7. Close the browser tab, open a new Incognito/Private window, and attempt to sign in again.

2. Enable Cross-Site Tracking and Cookies

Figma Weave relies on cross-origin resource sharing (CORS) and cookies to verify your identity across the primary Figma platform and the Weave runtime environment. If your browser blocks third-party cookies or cross-site tracking, the login window will fail silently.

• For Safari Users: Go to Safari > Settings > Privacy and uncheck Prevent cross-site tracking.
• For Chrome Users: Go to Settings > Privacy and security > Third-party cookies and select Allow third-party cookies (or add [*.]figma.com to the allowed sites list).
• For Brave/Firefox Users: Temporarily lower your shields or set tracking protection to "Standard" instead of "Strict" while attempting the initial login handshake.

3. Disconnect and Re-authorize Third-Party Identity Providers

If your organization uses Google Auth or an SSO provider, an outdated OAuth grant can cause a silent rejection during the sign-in redirect.

1. Sign out of your master identity provider account (e.g., your Google Workspace or Okta dashboard).
2. Navigate to your provider's security settings panel (for Google, go to myaccount.google.com/permissions).
3. Locate Figma or Figma Weave in the list of third-party apps with account access.
4. Click Remove Access or Revoke Authorization.
5. Return to the Figma Weave sign-in page. This forces a brand-new OAuth handshake.
6. Grant all requested permissions when the prompt reappears.

4. Verify License Allocations in the Admin Console

If you can sign in to Figma's main web app but get a "Not Authorized" or "Access Denied" screen when accessing Weave features, your user seat might not have the correct permissions allocated.

1. Ask your Organization Administrator to log into the main Figma Admin Console.
2. Have them navigate to the Members or Billing tab.
3. Check your user account status to confirm your seat is active and not set to "Viewer-restricted."
4. If your company utilizes Weave via an Enterprise beta or developer add-on, confirm that the administrator has explicitly turned on the "Weave Integration" toggle within the integration policies panel.

When to Escalate

If you have cleared your browser state, verified cross-site cookies, and re-authorized your identity provider but still cannot sign in, the issue likely points to an active billing hold or a platform-wide SSO certificate expiration.

First, check with your internal IT department to see if they have updated security certificates or restricted external API integrations. If your internal IT confirms everything is green on their end, compile your console logs (press F12 to open Console, take a screenshot of any red error text) and contact Figma Support directly through their official help portal.