Perplexity Login with Google Not Working – How to Fix

Step-by-Step Fix for Perplexity Google Login Not Working

Google OAuth login failures on Perplexity almost always fall into one of three categories: the browser is blocking something, a permission was revoked, or a cookie/cache conflict. Work through these steps in order.

Step 1 — Check That Popups Are Allowed for perplexity.ai

Google OAuth opens a separate popup window to handle the sign-in flow. If your browser blocks popups, the button appears to do nothing.

1. Click the Google login button on perplexity.ai/login.
2. Look for a popup-blocked icon in your browser's address bar (far right).
3. Click the icon and select Always allow popups and redirects from perplexity.ai.
4. Click the Google login button again.
5. The Google account selection window should now appear.

If you do not see a popup-blocked icon, the browser may not be blocking it — move to step 2.

Step 2 — Enable Third-Party Cookies for perplexity.ai

The OAuth flow requires Perplexity to set a cookie during the redirect from Google back to Perplexity. If third-party cookies are globally blocked, this step silently fails.

Chrome:

1. Go to Settings → Privacy and security → Cookies and other site data.
2. Make sure "Block third-party cookies" is not set to block all. Or add [*.]perplexity.ai as an exception under "Sites that can always use cookies."

Firefox:

1. Go to Settings → Privacy & Security → Enhanced Tracking Protection.
2. Set protection to "Standard" (not "Strict") or add perplexity.ai as an exception.

Brave:

1. Click the Brave shield icon in the address bar.
2. Set "Cross-site cookies blocked" to "Allow all cookies" for perplexity.ai.

Step 3 — Re-authorize Perplexity in Your Google Account

If you or another process previously revoked Perplexity's Google access, the OAuth handshake will fail silently.

1. Go to myaccount.google.com/permissions (Google Account → Security → Third-party apps with account access).
2. Find "Perplexity AI" in the list.
3. Click on it and select Remove access.
4. Return to perplexity.ai/login and click Continue with Google again.
5. Complete the authorization prompt — you will be granting fresh access, which clears any corrupted permission state.

Step 4 — Clear Cookies for Both perplexity.ai and accounts.google.com

A corrupted cookie from a previous OAuth attempt can block new login attempts.

1. Open your browser's developer tools (F12 or right-click → Inspect).
2. Go to Application (Chrome/Edge) or Storage (Firefox) → Cookies.
3. Delete all cookies for both perplexity.ai and accounts.google.com.
4. Close developer tools and reload perplexity.ai/login.
5. Try Google login again.

Alternatively, use your browser's privacy settings to clear cookies for both domains simultaneously.

Step 5 — Disable Browser Extensions

Extensions that block trackers or scripts can intercept the OAuth redirect and break the flow.

1. Open your browser extension manager.
2. Disable all extensions, especially: uBlock Origin, Privacy Badger, Ghostery, Disconnect, or any firewall/VPN extension.
3. Try the Google login again.
4. If it works, re-enable extensions one by one to identify the culprit. Then whitelist perplexity.ai and accounts.google.com in that extension.

Step 6 — Try in an Incognito Window

Incognito mode disables extensions and starts with no cookies, isolating whether the issue is local.

1. Open an incognito/private window (Ctrl+Shift+N).
2. Go to perplexity.ai/login and try Google login.
3. If it works in incognito but not in normal mode, go back to steps 2–5 to fix the root cause in your regular browser.

Step 7 — Check Your Google Account Restrictions

If you are using a Google Workspace account (work or school), your administrator may have restricted third-party app access.

1. During the OAuth flow, look for any error message mentioning "admin policy" or "organization."
2. If you see such a message, contact your IT administrator and ask them to whitelist Perplexity AI in the Google Workspace admin console.
3. As a workaround, use a personal Google account or switch to Perplexity email/password login.

Step 8 — Contact Perplexity Support

If all steps above fail, reach out to support@perplexity.ai with:

• The exact error message shown during login
• Your Google account type (personal vs. Workspace)
• Which browser and OS you are using
• Whether incognito also fails

Why This Happens

Perplexity's Google login uses the standard OAuth 2.0 flow: clicking "Continue with Google" opens a popup to accounts.google.com, you approve access, and Google redirects back to Perplexity with an authorization token. This flow fails when any link in the chain breaks — blocked popups, disabled third-party cookies, revoked permissions, or a browser extension that intercepts the redirect URL. Because the error often appears as a silent failure (the button does nothing) rather than an explicit message, users frequently do not know where the break occurred.

Common Mistakes to Avoid

• Clicking the Google button multiple times rapidly — this can create multiple conflicting OAuth sessions. Click once and wait up to 10 seconds for the popup to appear.
• Using a Workspace account without checking admin restrictions — work and school Google accounts often have app access restrictions that silently block Perplexity's OAuth.
• Not clearing both perplexity.ai and accounts.google.com cookies — clearing only one side leaves a mismatched session state that continues to block the login.
• Forgetting that re-granting Google access is safe — revoking and re-granting permission in myaccount.google.com/permissions does not delete your Perplexity account or data. It simply refreshes the authorization token.
• Assuming a different Google account will work automatically — if third-party cookies or popups are blocked, the issue will occur with any Google account until those browser settings are fixed.
• Running in Strict mode on Firefox — Firefox's Strict tracking protection mode blocks many OAuth cookies as cross-site trackers, which breaks the login redirect chain.

Google Workspace Accounts: Special Handling

Google Workspace accounts (work email or school email managed by an organization) follow different OAuth rules than personal Gmail accounts. Perplexity's Google login fails silently for Workspace users more often than for personal account users, and the fix is different.

Why Workspace Accounts Fail

When you sign in with a Workspace account, Google checks your organization's App Access Control policy before completing the OAuth handshake. If your IT administrator has set the policy to "Restricted" (only approved apps can connect), Perplexity will fail during the authorization step with an error such as:

• "Admin policy prevents access to this app"
• "Your organization has restricted access to this application"
• "Access blocked: This app's request is invalid for your organization"

This is not a Perplexity bug or a browser issue — it is an explicit restriction set by your organization.

What to Do If Your Workspace Account Is Blocked

Option 1: Ask your IT administrator to whitelist Perplexity. Your administrator can approve Perplexity in the Google Workspace Admin Console under Security → API controls → App Access Control → Manage third-party app access. They need to search for "Perplexity AI" and set access to "Trusted." This takes effect immediately and allows all Workspace users at your organization to connect Perplexity via Google login.

Option 2: Use a personal Google account. Create a separate personal Gmail account and use that to sign in to Perplexity. This keeps your Perplexity account separate from your employer's Workspace account, which may actually be preferable from a data-privacy standpoint — queries you run on Perplexity using your personal account are not associated with your employer's Google environment.

Option 3: Switch to Perplexity's email/password login. If your organization controls your Google account and you would prefer not to mix personal and professional accounts, create a Perplexity account with an independent email and password. Go to perplexity.ai/login, click "Sign up with email," and create credentials that are not tied to any Google account. Note that this creates a new account and does not merge with any existing Perplexity account you may have.

Workspace Accounts That Work Without IT Action

Some Google Workspace configurations allow users to self-authorize third-party apps. If your organization uses the "Unrestricted" or "Limited" App Access Control policy, you may be able to complete the Perplexity Google login without involving your IT department — Google will simply ask you to confirm that you want to grant Perplexity access, and you can approve it yourself.

If you are unsure which policy your organization uses, attempt the Google login and observe whether you are prompted to "Request access" (restricted) or simply asked to "Allow" (unrestricted). If you see "Request access," your IT administrator must approve it.

Verifying Your Google Login Is Working Correctly

After successfully logging in with Google, confirm the connection is stable:

1. Go to perplexity.ai/settings and check that your account shows the correct email address under your profile.
2. Visit myaccount.google.com/permissions and confirm "Perplexity AI" appears in the list of connected third-party apps with a recent authorization date.
3. Log out of Perplexity and log back in with Google — this verifies the session can be re-established without errors.

If all three checks pass, your Google login is functioning correctly and should remain stable for approximately 30 days before requiring re-authorization.

View all Perplexity guides