To strengthen Perplexity sign-in, secure the Google, Apple, or email account you use to authenticate. Perplexity’s current public documentation does not establish the native authenticator-app setup, QR code, or eight backup codes previously described here. It explicitly says that Perplexity does not support creating account passwords.
Official guidance checked October 14, 2026. The steps below are provider security settings, not a claim that a separate Perplexity TOTP feature has been enabled.
Understand which account supplies the security check
The Perplexity account guide documents email links or one-time codes and sign-in with Google or Apple. A code received by email is not, by itself, proof that a separate authenticator-based second factor is configured in Perplexity.
Check the address shown in Perplexity settings, then identify the provider protecting that mailbox or identity. If you use an employer’s account, its administrator may manage authentication. Do not replace a required organizational login with a personal one simply to bypass a security prompt.
Protect the email route even if you normally click Google or Apple. Adding security to one sign-in route should not lead you to ignore an accessible mailbox or an already-open session on a shared device.
For Google sign-in, review Google Account security
- Open your Google Account directly and select Security & sign-in.
- Under How you sign in to Google, open the 2-Step Verification setup or review its existing settings.
- Follow the offered verification steps and check your recovery options before leaving the page.
Use Google’s current setup guide for the methods available to your account. A passkey and a password-plus-second-step flow can look different; do not assume the absence of a separate code on every login means protection is off. Managed accounts may require administrator assistance.
Only approve a sign-in prompt you initiated. Keep recovery material private and separate from the device it is meant to recover. This is Google security configuration; it does not produce “Perplexity backup codes.”
For Apple or email sign-in, secure the underlying account
On an Apple device, open Settings (System Settings on Mac), select your name, then Sign-In & Security. Review two-factor authentication and the trusted contact methods. Apple’s documentation says most accounts already use it and Sign in with Apple requires it. Do not disable it to troubleshoot Perplexity.
If you sign in through an email link, use your email provider’s own security guide to enable its supported protection and maintain recovery access. The controls may be called two-step verification, MFA, or passkeys. Do not copy Google-specific menu paths into an unrelated mailbox service.
An Apple private relay address can be the registered Perplexity email. Check it before switching methods; a different address can lead to a different account rather than a stronger version of the original one.
Verify access without locking yourself out
Keep a working trusted session while checking recovery details. Then make one normal sign-in attempt on a device you control, verify the account email in Perplexity, and confirm expected content is present. An already-authenticated session may not ask for every factor again.
If an unexpected authenticator prompt appears, identify its actual domain and provider before entering a code. Consult the relevant provider or your administrator. Do not scan an unverified QR code from a tutorial, send backup codes to support, or install a browser extension that claims to add native Perplexity authentication.
Provider MFA improves the account’s protection but is not a guarantee against phishing, stolen sessions, or an unlocked device. Use a screen lock, avoid shared signed-in sessions, and review unfamiliar account activity through the provider’s official controls.
Glad it helped. Take a short break with a game:
Sorry about that. Search for the exact error message, or look for a tool that checks your device: