Step-by-Step Fix
Google and Apple sign-in failures on Perplexity follow predictable patterns. This guide covers the full set of causes — popup blocking, third-party cookie restrictions, revoked permissions, and network-level interference — and tells you exactly how to fix each one.
Step 1: Check for and Allow Popups from Perplexity
Both Google and Apple sign-in open a popup window to complete the authentication. If your browser's popup blocker prevents this, nothing happens when you click the login button.
In Chrome:
- Click Continue with Google or Continue with Apple
- Watch for a popup notification in the address bar (right side) — it looks like a small rectangle with an X
- Click the notification and select Always allow pop-ups and redirects from perplexity.ai
- Click the login button again
In Firefox:
- When the popup is blocked, Firefox shows a yellow bar at the top of the page
- Click Allow or click Options → Allow pop-ups for perplexity.ai
- Try the login button again
In Safari:
- Go to Safari → Settings → Websites → Pop-up Windows
- Find perplexity.ai in the list and change the setting to Allow
- Reload the page and try again
Step 2: Enable Third-Party Cookies for Perplexity
The OAuth handshake that Google and Apple use relies on third-party cookies to pass the authentication token back to Perplexity. If third-party cookies are blocked, the popup will open but fail to complete.
Chrome:
- Go to Settings → Privacy and Security → Cookies and other site data
- If set to "Block third-party cookies," either switch to "Allow all cookies" or add an exception:
- Click Add under "Sites that can always use cookies"
- Add
perplexity.aiand[*.]google.com
- Reload perplexity.ai and try logging in
Firefox:
- Go to Settings → Privacy and Security → Enhanced Tracking Protection
- If set to Strict mode, switch to Standard or Custom
- Alternatively, click the shield icon in the address bar on perplexity.ai and toggle off Enhanced Tracking Protection for this site
Edge:
- Go to Settings → Cookies and site permissions → Cookies and data stored
- Under "Allow" add
perplexity.ai - Ensure "Block third-party cookies" is not enabled for Perplexity
Step 3: Test in an Incognito Window
Incognito mode disables most extensions and uses default cookie settings, making it a reliable diagnostic tool.
- Press
Ctrl+Shift+N(Chrome/Edge) orCtrl+Shift+P(Firefox) to open an incognito window - Navigate to perplexity.ai/login
- Click Continue with Google or Continue with Apple
- Complete the authentication and check whether it works
If incognito login succeeds, an extension in your regular browser is blocking the OAuth flow. Proceed to Step 4. If incognito login also fails, proceed to Step 5 (network or account issue).
Step 4: Disable Extensions One by One
If incognito works but your regular browser does not, isolate the problematic extension.
- Go to your browser's Extensions page (Chrome:
chrome://extensions, Firefox:about:addons) - Disable all extensions
- Try logging in to Perplexity — if it works, an extension was the cause
- Re-enable extensions one at a time, testing Perplexity login after each
- When login breaks again, you have found the culprit extension
- Add perplexity.ai to that extension's allowlist/whitelist
Common problematic extensions: uBlock Origin, AdGuard, Ghostery, Privacy Badger, NoScript, Disconnect, and any VPN browser extension.
Step 5: Check Your Google or Apple Account Permissions
If the issue is not extension-related, your account may have revoked Perplexity's OAuth access or have a pending verification requirement.
For Google:
- Go to myaccount.google.com → Security → Third-party apps with account access
- Look for Perplexity in the list
- If it is not there, this is normal — click "Continue with Google" on Perplexity and it will ask for permission again
- If it is there but showing a warning or error, click it and remove access, then re-authorize from the Perplexity login page
- Also check that your Google account does not have a pending security action (password change, recovery phone verification, etc.) that would block third-party app access
For Apple:
- On iOS, go to Settings → [your name] → Sign in with Apple
- Find Perplexity in the list — if it is not there, you have not signed in with Apple on this device before
- If you see a warning, tap Perplexity and tap Stop Using Apple ID, then re-authorize from Perplexity's login page
- On macOS, go to System Settings → Apple ID → Password and Security → Apps Using Apple ID
Step 6: Test on a Different Network
OAuth redirects can be blocked by network-level filtering, especially on corporate or university Wi-Fi.
- Disconnect from your current network
- Connect via a mobile hotspot or a different Wi-Fi network
- Navigate to perplexity.ai/login and attempt OAuth login
- If it works on the alternate network, your primary network is filtering OAuth traffic
Google's authentication endpoint (accounts.google.com) and Apple's endpoint (appleid.apple.com) must both be reachable for OAuth to succeed. Corporate networks that use content filtering may block these domains in certain configurations.
Step 7: Clear Browser Cache and Stored Credentials
Stale authentication data in your browser's cache can create conflicts during the OAuth flow.
- Open browser settings and navigate to the Privacy/History section
- Clear cookies and cached data for the last 7 days (or "All time" for a thorough reset)
- Also clear any saved passwords for perplexity.ai in your browser's password manager, as incorrect stored credentials can interfere with OAuth
- Restart your browser completely and try the login again
Why This Happens
Perplexity uses OAuth 2.0 for Google and Apple sign-in, which requires a multi-step exchange: Perplexity redirects you to Google or Apple's login page, you authenticate there, and then Google or Apple sends a token back to Perplexity confirming your identity. This process depends on three browser behaviors working correctly: popups being allowed (so the Google/Apple window can open), third-party cookies being enabled (so the token can be passed back to Perplexity's domain), and no extension intercepting the redirect request. When any of these three conditions fails, the login either appears to do nothing (popup blocked) or starts but never completes (cookies blocked or redirect intercepted). Because modern browsers have become progressively stricter about popups and third-party cookies as privacy protections, these failures have become more common even without user action.
Common Mistakes to Avoid
- Clicking the login button repeatedly when nothing happens. Multiple clicks initiate multiple parallel OAuth sessions, which can create state conflicts. Click once, wait 15 seconds, and if nothing opens, look for the popup blocked notification.
- Resetting your Perplexity password when using OAuth login. If your account was created with Google or Apple, you do not have a Perplexity password to reset. The password reset flow only applies to email/password accounts.
- Blocking third-party cookies globally without adding exceptions. A global third-party cookie block will break OAuth login on Perplexity and many other sites. Add a site-specific exception for perplexity.ai rather than changing the global setting.
- Testing on the same network and browser after failing. If your first test fails, changing only one variable at a time (browser, then network, then extensions) is the only way to isolate the cause. Testing on the same setup with the same conditions will always produce the same result.
- Assuming the problem is with Perplexity's servers. OAuth failures are almost always client-side (browser or network), not server-side. Perplexity's servers rarely cause OAuth failures during normal operation. Check status.perplexity.ai only after ruling out browser and network causes.
- Trying to sign in with Apple on an Android device without a two-factor authentication device nearby. Sign in with Apple requires two-factor authentication. If you do not have access to a trusted Apple device or phone number, you will not be able to complete Apple sign-in on any platform.