How to fix Perplexity error?
Start by checking whether the issue is caused by account access, plan status, browser state, or a temporary service incident. Then follow the step-by-step checks below to isolate the root cause quickly.
Complete guide — how to use Perplexity, fix common errors, manage billing, and get the most out of every feature.
Start by checking whether the issue is caused by account access, plan status, browser state, or a temporary service incident. Then follow the step-by-step checks below to isolate the root cause quickly.
Start by checking whether the issue is caused by account access, plan status, browser state, or a temporary service incident. Then follow the step-by-step checks below to isolate the root cause quickly.
Start by checking whether the issue is caused by account access, plan status, browser state, or a temporary service incident. Then follow the step-by-step checks below to isolate the root cause quickly.
Start by checking whether the issue is caused by account access, plan status, browser state, or a temporary service incident. Then follow the step-by-step checks below to isolate the root cause quickly.
Start by checking whether the issue is caused by account access, plan status, browser state, or a temporary service incident. Then follow the step-by-step checks below to isolate the root cause quickly.
Start by checking whether the issue is caused by account access, plan status, browser state, or a temporary service incident. Then follow the step-by-step checks below to isolate the root cause quickly.
Start by checking whether the issue is caused by account access, plan status, browser state, or a temporary service incident. Then follow the step-by-step checks below to isolate the root cause quickly.
Start by checking whether the issue is caused by account access, plan status, browser state, or a temporary service incident. Then follow the step-by-step checks below to isolate the root cause quickly.
Perplexity 'Access Denied' errors indicate either a geographic restriction or an account permission problem, while 'Session Expired' simply means your 30-day login session has ended and you need to sign in again. For Session Expired, just log back in — your data is safe. For Access Denied, try disabling your VPN first, then check whether your account or subscription is in good standing at perplexity.ai/settings.
Perplexity creates a separate account each time you sign in with a different method — for example, if you first used Google and then tried email/password, you have two accounts at different email addresses. The fix is to always use the same login method you used at sign-up. To merge accounts or migrate Pro access, email support@perplexity.ai — there is no self-serve merge tool.
Perplexity Pro users get 200 Pro searches per week (resetting every Monday at 00:00 UTC); API (Sonar) users have a default cap of 50 requests per minute. If you hit a rate limit, wait for the reset window or switch to Standard search mode to continue immediately.
If you see a duplicate charge or were billed for the wrong Perplexity plan, email support@perplexity.ai immediately with your account email, the charge dates and amounts, and your Stripe receipt numbers. Perplexity support typically resolves duplicate charge issues within 1–3 business days. Duplicate charges most commonly occur when a payment fails and Stripe retries, or when a user subscribes twice under different accounts. Do not file a credit card dispute until support has had 7 business days to respond.
Fix Perplexity billing issues by confirming the purchase channel, verifying the card/bank auth, refreshing your subscription status (sign out/in), and checking for pending vs posted charges. If access is still locked, contact support with the receipt/transaction ID.
To view your Perplexity billing history, go to perplexity.ai/settings → Subscription. Perplexity automatically sends a receipt email via Stripe every time your subscription renews — check your inbox and spam folder for emails from receipts@stripe.com. PDF invoices can be downloaded directly from each receipt email. For invoices with company name or VAT number added, email support@perplexity.ai with the billing period and your business details.
Access your Perplexity billing page by going to perplexity.ai/settings and clicking the Subscription tab. There you can see your current plan (Free or Pro at $20/month or $200/year), next billing date, saved payment method, and download past invoices. If the page fails to load, disable browser extensions or open an incognito window — Stripe's billing iframe is blocked by many ad blockers.
Perplexity offers three plans: Free (unlimited standard searches, 5 Pro searches/day), Pro at $20/month or $200/year (300 Pro searches/day, 20 Deep Research reports/month, advanced AI models, file uploads), and Enterprise (custom pricing, team features). Upgrading takes effect immediately after payment — go to perplexity.ai/settings → Subscription → Upgrade to Pro.
To upgrade Perplexity from Free to Pro ($20/month or $200/year), go to perplexity.ai/settings → Subscription → Upgrade to Pro. Upgrades take effect immediately — your 300 Pro searches per day activate within 5 minutes of payment. To downgrade, click Cancel Plan; your Pro access continues through the end of the current billing period and no data is lost. You cannot lose searches, history, or saved threads by changing plans.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Contact Perplexity billing support by emailing support@perplexity.ai — include your account email, the charge date and amount, a screenshot of your Settings page, and a copy of your Stripe receipt. Response time is typically 1–3 business days. For urgent disputes, you can open a credit card chargeback after 7 business days with no response, but exhaust the support email route first.
Perplexity Pro costs $20/month or $200/year and bills automatically through Stripe. To fix billing issues, go to perplexity.ai/settings → Subscription → Billing, update your payment method, and retry. If you were charged but Pro features are still locked, sign out and back in — provisioning can take up to 10 minutes. For duplicate charges or unresolved issues, email support@perplexity.ai with your transaction ID.
To cancel Perplexity Pro and stop future charges, go to perplexity.ai/settings → Subscription → Cancel Plan and confirm the cancellation. You will receive a confirmation email immediately. Your Pro access continues until the end of the current billing period, then the account reverts to Free automatically and no further charges occur. Canceling before your renewal date is the only way to prevent the next charge — Stripe does not reverse charges after they are processed.
Try incognito mode, clear cookies for the service, disable extensions, and retry. If you use Google/Apple login, re-authorize the provider and check for outages.
If you can't log into Perplexity, the three most likely causes are: account temporarily locked after multiple failed attempts (wait 15–30 minutes), email verification not completed at signup (check your inbox for a verification link), or an OAuth account conflict where you signed up with Google but are trying to log in with a different email. Identify which scenario applies, then follow the targeted fix below.
Perplexity citations fail to load in over 70% of cases because an ad blocker or privacy extension is blocking the source-fetching requests that run alongside the AI response. Disable your ad blocker (uBlock Origin, AdGuard, Ghostery) for perplexity.ai, reload the page, and run your query again — citations should appear as numbered blue links below the answer. If the problem continues, switch from Pro Search to Standard Search as a quick test, then clear your browser cache.
Refresh the page, reduce request size, try another browser/network, and disable extensions. If the issue persists, check the status page and retry later.
Fix Perplexity errors by hard-reloading, clearing cache, reducing request size, and testing another browser/network. Capture the exact error text + timestamp for support if it persists.
Perplexity error 401 means Unauthorized — your session has expired or your API key is invalid. For web users, log out at perplexity.ai/settings/account, clear cookies, and log back in. For API users, check that your key is active at perplexity.ai/settings/api and that you are sending it as a Bearer token in the Authorization header. A 401 error is never caused by Perplexity's servers — it is always an authentication issue on your end.
Perplexity error 403 means Forbidden — your request was understood but blocked. The three most common causes are: regional restrictions (Perplexity is unavailable in some countries), account-level restrictions (your account was flagged or your subscription lapsed), and content policy blocks (the specific query was rejected). Start by disconnecting any VPN, then checking your account status at perplexity.ai/settings/account, then clearing cookies and logging back in.
Refresh the page, reduce request size, try another browser/network, and disable extensions. If the issue persists, check the status page and retry later.
Perplexity error 500 is an Internal Server Error — the problem is entirely on Perplexity's servers, not your device or network. There is no local fix. Check perplexity.ai/status to see if an incident is active, then wait 5 to 15 minutes before retrying. Most Perplexity 500 errors resolve automatically within 15 minutes as the server recovers. If the error persists beyond 30 minutes, report it at perplexity.ai/contact.
Refresh the page, reduce request size, try another browser/network, and disable extensions. If the issue persists, check the status page and retry later.
The 'Error in Processing Query' message on Perplexity appears when your query is too long or complex for the model to process, contains phrasing that triggers content filters, or when a backend service times out mid-response. The fastest fix is to shorten your query to under 500 characters, remove ambiguous or sensitive phrasing, and resubmit. If the error persists across multiple queries, check perplexity.ai/status for an ongoing service incident.
Perplexity error messages fall into three groups: rate limit errors (too many requests — wait 60 seconds or upgrade your plan), service errors (something went wrong, network error — refresh the page or check perplexity.ai/status), and query errors (error processing query, content policy — rephrase or shorten your search). The fix depends on which error you see. This guide covers the 10 most common Perplexity error messages with specific solutions for each.
Refresh the page, reduce request size, try another browser/network, and disable extensions. If the issue persists, check the status page and retry later.
The 'Something Went Wrong' error on Perplexity signals a technical failure in the backend — typically an API call failure, model endpoint timeout, or web retrieval service error — rather than a user-facing input problem. This error is distinct from the generic 'Error in Processing Query' message, which usually involves query content. For 'Something Went Wrong,' wait 30 to 60 seconds and retry; if the error persists for more than 5 minutes, check perplexity.ai/status for an active incident.
Refresh the page, reduce request size, try another browser/network, and disable extensions. If the issue persists, check the status page and retry later.
Fix Perplexity errors by hard-reloading, clearing cache, reducing request size, and testing another browser/network. Capture the exact error text + timestamp for support if it persists.
To check whether Perplexity is down right now, go directly to perplexity.ai/status — this is the official status page maintained by Perplexity's engineering team and shows live incident reports. If the status page shows all systems operational but you are still experiencing errors, the problem is likely specific to your account, browser, or network rather than a platform-wide outage.
Most Perplexity errors resolve in under 5 minutes by following this order: identify the error type (401/403/500/network), refresh the page once, clear browser cache and cookies, switch to a different browser or network, then check perplexity.ai/status for any active outage. If the status page shows no incident, the error is almost always local — a cache or network fix will resolve it.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
To report a Perplexity bug effectively, email support@perplexity.ai with 6 pieces of information: the exact error message text, the time and date of the issue, your browser and OS version, the steps needed to reproduce the bug, whether it occurs in an incognito window, and a screenshot. Perplexity's support team typically responds within 24 to 48 hours on business days. For widespread outages, also tag @perplexity_ai on X for faster acknowledgment.
Perplexity file analysis fails most often because the uploaded file is password-protected, corrupted, or exceeds the size limit — PDF files must be under 25 MB and must not have DRM or password protection. Remove the password using your PDF viewer, re-export the file at a smaller size, and upload again. If the error persists on a valid file, clear your browser cache and try uploading from an incognito window.
Perplexity Pro supports file uploads up to 25 MB per file. Supported formats include PDF (text-based, not scanned), plain text (.txt), and Word documents (.doc and .docx). File upload is a Pro-only feature — free plan users do not have access. If your file exceeds the size limit or is in an unsupported format, compress it or convert it to PDF before uploading. Alternatively, paste the text content directly into the search bar, which works for most analysis tasks.
If Perplexity keeps logging you out, the most common cause is browser cookies being blocked or cleared automatically. Fix it by going to your browser's cookie settings and allowing perplexity.ai to store cookies, then disable any 'clear cookies on close' setting. Browsers in private/incognito mode always log you out on close — this is by design. If you use a normal browser window but still get logged out, the issue is typically a cookie-blocking extension or a strict browser privacy setting.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Perplexity Labs features such as Comet have a strict daily cap — typically 5 to 20 uses per day depending on the feature — separate from your standard 200 Pro searches per week. Labs limits reset at midnight UTC every day. When you hit the cap, switch to standard Pro search or Deep Research mode for the rest of the day, then return to Labs after the UTC midnight reset.
Perplexity's 'limit exceeded' message has three distinct causes: (1) Pro search weekly quota of 200 searches exhausted — wait until Monday 00:00 UTC; (2) Deep Research monthly quota of 20 sessions used up — wait until the 1st of next month; (3) Free plan daily quota of ~5 Pro searches reached — wait until 00:00 UTC tonight. Switch to Standard search to continue immediately in all three cases.
Perplexity temporary restrictions are triggered by 3 main behaviors: submitting more than 20 to 30 queries in a short period, repeatedly switching between VPN server locations during a session, or using browser automation scripts that mimic bot traffic. If you are flagged, stop all activity and wait 1 to 4 hours for the restriction to lift automatically. Do not attempt to bypass the block by creating a new account — this risks a permanent ban. For persistent restrictions, email support@perplexity.ai.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Check the exact account, plan, and environment first. Then isolate whether the issue is caused by login/session state, billing/permissions, browser or app behavior, or a platform-side restriction. Use the steps below to narrow it down quickly.
Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Start by isolating whether the issue is caused by account state, plan limits, browser/app behavior, or a temporary platform-side problem. Then follow the steps below to narrow down the root cause quickly.
Perplexity desktop login failures are caused by 4 main issues: browser extensions blocking OAuth requests, expired SSL certificates on corporate networks, corrupted cached session data, or an enterprise firewall intercepting the authentication redirect. Start by opening an incognito window and trying to log in — if that works, a browser extension is the cause. If incognito also fails, test on a mobile hotspot to rule out network-level interference.
Perplexity mobile login fails for different reasons on iOS and Android. On iOS, the most common cause is that Sign in with Apple is misconfigured or your iCloud account is logged out, which prevents the Apple ID handshake. On Android, outdated Google Play Services breaks Google sign-in. In both cases, force-close the Perplexity app, clear the app cache, and try again — if that fails, uninstall and reinstall the app to get a clean authentication state.
Perplexity Google and Apple OAuth login failures have 3 primary causes: a browser extension or popup blocker preventing the sign-in window from opening, third-party cookies being blocked (required for OAuth to complete the session handshake), or Perplexity's access being revoked in your Google or Apple account settings. Open an incognito window and try logging in — if it works, a browser extension is the cause. If not, check that third-party cookies are enabled for perplexity.ai.
Try incognito mode, clear cookies for the service, disable extensions, and retry. If you use Google/Apple login, re-authorize the provider and check for outages.
Fix Perplexity login problems by clearing site cookies, disabling extensions/VPN, completing OAuth re‑authorization (Google/Apple), and trying a different network. If you’re stuck in a loop, reset the session and verify you’re using the same login method as the account.
If the Perplexity login page at perplexity.ai/login is not loading, the fastest fix is to clear your browser cache and cookies, then disable any VPN or ad blocker. In most cases, a full cache clear resolves the blank-page or infinite-load issue within 60 seconds. If the page still fails, check status.perplexity.ai for ongoing incidents before troubleshooting further.
Try incognito mode, clear cookies for the service, disable extensions, and retry. If you use Google/Apple login, re-authorize the provider and check for outages.
Perplexity Google login fails most often because the browser is blocking the OAuth popup, third-party cookies are disabled, or Google has revoked the app's permission. The fix takes under 2 minutes: allow popups for perplexity.ai, enable third-party cookies, and re-authorize Perplexity in your Google account's security settings at myaccount.google.com/permissions.
Try incognito mode, clear cookies for the service, disable extensions, and retry. If you use Google/Apple login, re-authorize the provider and check for outages.
Perplexity email and password login fails for three distinct reasons: the password is wrong, the email address is not registered, or the account was originally created with Google or Apple sign-in and has no password set. If you are certain your email is correct, go to perplexity.ai/login → Forgot password to reset it. If the reset email never arrives, check your spam folder — it comes from noreply@perplexity.ai within 5 minutes.
Perplexity login failures are fixed in over 90% of cases by clearing site cookies and trying an incognito window. If you use Google or Apple OAuth, the most common cause is a blocked redirect — disable your ad blocker and VPN before clicking the login button, then complete the OAuth prompt in full without switching accounts.
Perplexity Pro's message limit dropped from 600 to 200 Pro searches per week in May 2026, resetting every Monday at 00:00 UTC. When you hit the limit, switch to Standard (Default) search mode immediately — it is unlimited and free. To check how many searches you have left, go to perplexity.ai/settings/account.
A Perplexity network error means your connection to Perplexity's servers is being interrupted — the problem is between your device and Perplexity, not on Perplexity's servers. Fix it in this order: disconnect your VPN completely, switch your DNS to 8.8.8.8 or 1.1.1.1, clear your browser cache, then switch to a different network such as your phone's mobile hotspot. If Perplexity works on mobile data but not your main connection, the issue is your router, ISP, or corporate firewall.
Perplexity goes down for 1–4 hours a few times per month; if the site loads but searches fail, the fastest fix is opening an incognito tab, disabling browser extensions, and switching to a different network. If that does not help, check status.perplexity.ai and wait for the incident to resolve — forced retries will not speed up recovery.
Perplexity payment declines are most commonly caused by your bank blocking the international recurring charge, a 3D Secure verification step that was not completed, or an expired card. To fix: call your bank to authorize the charge, then retry at perplexity.ai/settings → Subscription → Billing. If the card still fails, switch to PayPal as an alternative payment method.
If your Perplexity Pro subscription is active but features like model selection, file uploads, or Deep Research are still locked, the most common cause is that you are logged into a different account than the one that holds the Pro subscription. Verify that the email shown in your profile icon matches the email on your Stripe receipt. If they match, sign out completely and sign back in to refresh the session. If features remain locked after signing back in, email support@perplexity.ai with a screenshot of your Settings page and your receipt.
Perplexity Pro search limits changed in late 2025 from a daily cap to a weekly cap. As of 2026, Pro subscribers get approximately 200 Pro searches per week (not per day), with file uploads capped at 50 per week. Quick searches remain unlimited. Limits reset weekly, not at midnight UTC daily. If you hit the cap, switch to Quick search or wait for the weekly reset.
As of May 2026, Perplexity Pro includes 200 Pro searches per week (down from 600) and 20 Deep Research reports per month (down from 50); limits reset every Monday at 00:00 UTC. Standard searches are unlimited on all plans. When you hit the cap, switch to Standard mode or wait for Monday's reset — there is no way to purchase additional Pro searches mid-cycle.
If Perplexity Pro did not activate after payment, wait 5 minutes then sign out and sign back in — this forces the account to sync with Stripe and activates Pro in over 90% of cases. If Pro still does not appear after 30 minutes, clear your browser cache, close all tabs, and sign in again. If it still shows Free after 1 hour, email support@perplexity.ai with your Stripe receipt and a screenshot of your Settings page — support can manually activate your account within 1–3 business days.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Perplexity Pro gives you 200 Pro searches per week; the counter resets every Monday at 00:00 UTC. If you hit the cap, switch to Standard mode immediately — Standard searches are unlimited for Pro users. For temporary 429 errors caused by sending too many requests too fast, wait 60 seconds and slow down your request pace; this is rate throttling, not a quota exhaustion.
Perplexity Free gives you unlimited Quick searches with the default Sonar model. Perplexity Pro ($20/month) adds 300 daily Pro searches using premium models like GPT-4o, Claude 3.5 Sonnet, and Gemini — plus unlimited file uploads and image generation. For casual use, Free is enough. For research, document analysis, or daily power use, Pro pays for itself quickly.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Perplexity's 'rate limit exceeded' error has three causes: (1) sending requests too fast in the API — wait 60 seconds and retry with exponential backoff; (2) exhausting your weekly 200 Pro searches — switch to Standard mode or wait until Monday 00:00 UTC; (3) exceeding the API default of 50 requests per minute — slow your request rate to 1 request per 1.2 seconds. Each scenario has a different fix.
Perplexity rate limits are triggered when you send too many searches too quickly or hit your plan's daily Pro search cap (300/day for Pro users). Wait for the throttle to clear, switch to Quick search (unlimited), or slow down your request pace.
To avoid hitting Perplexity throttle limits, default to Standard mode for routine searches and reserve Pro mode for queries that genuinely need deeper web access. Pro users get 200 Pro searches per week (resets Monday 00:00 UTC), so spreading them across 5 days gives you a safe budget of 40 Pro searches per day. Use batch-style queries — combine multiple related questions into one well-structured prompt — to get more value from each Pro use.
Perplexity does not have a published refund guarantee, but first-time subscribers who request a refund within 30 days of their initial charge are usually approved. Email support@perplexity.ai with your account email, charge date, Stripe receipt number, and reason for the refund. Approved refunds return to your original payment method within 3–10 business days via Stripe.
To get a Perplexity Pro refund, cancel your subscription first at perplexity.ai/settings → Subscription → Cancel Plan, then email support@perplexity.ai within 30 days of your charge with your receipt and account email. Monthly refunds ($20) are more commonly approved than annual refunds ($200) for mid-cycle requests. Approved refunds process through Stripe in 3–10 business days.
Perplexity has no published refund policy with a guaranteed window, but in practice the support team approves refunds for first-time subscribers who request within 30 days of the charge. Annual plan subscribers ($200/year) may receive prorated refunds for unused months. There is no self-service refund button — all refunds require emailing support@perplexity.ai with your transaction ID and cancellation confirmation.
Perplexity has no automatic refund button — you must request a refund by emailing support@perplexity.ai. First-time subscribers who cancel within 30 days have the highest success rate. The process takes 3–5 business days to get a response, and refunds reach your bank in 3–10 business days after approval. Include your account email, transaction ID, and reason for cancellation in your message.
When Perplexity shows a blank page or the search results area stays empty after submitting a query, the cause is almost always a JavaScript rendering failure — not a problem with Perplexity finding results. The fix in 80% of cases is disabling your ad blocker for perplexity.ai and doing a hard reload (Ctrl+Shift+R or Cmd+Shift+R). If that does not work, clearing your browser cache and testing in an incognito window will isolate whether an extension or corrupted cached file is preventing the page from rendering.
When Perplexity returns no results, the most common causes are a network connectivity issue, an overly long or complex query that times out, or a temporary service disruption. In most cases, shortening your query to under 100 words and refreshing the page resolves it within 30 seconds. If results are consistently empty, check perplexity.ai/status for active incidents and try switching from Pro Search to Standard search mode.
When Perplexity shows 'Something went wrong' alongside a network error, the most likely cause is a DNS resolution failure, a VPN or proxy interrupting the connection, or a corporate firewall blocking Perplexity's API endpoints. Disconnect your VPN, switch to a public DNS server (8.8.8.8 for Google or 1.1.1.1 for Cloudflare), and reload the page. If the error appears on a work or school network, test via mobile hotspot — if it works on hotspot, the institution's firewall is the cause.
The 'Something went wrong' error on Perplexity is a generic server-side error that resolves on its own in over 80% of cases with a simple page refresh. If refreshing does not help, the three most common root causes are: a temporary service disruption (check perplexity.ai/status), a VPN or network interference blocking the response stream, or an expired login session. Reload the page, clear your browser cache, and log out then back in — most users are back to normal within 2 minutes.
Wait for the limit to reset, reduce request frequency, and avoid rapid retries. If you hit a hard cap, upgrade your plan or use a backup workflow until the window resets.
Perplexity Sonar API defaults to 50 requests per minute (RPM) and 1,000 requests per day on the base tier. When you exceed either limit, the API returns a 429 Too Many Requests error. Fix it by implementing exponential backoff with a minimum 1-second delay between retries, reducing request concurrency, and applying for a higher-tier limit increase through the Perplexity developer portal.
Perplexity processes refunds on a case-by-case basis through support@perplexity.ai — there is no self-service refund button. First-time subscribers who cancel within 30 days and have not heavily used Pro features are most commonly approved. Monthly plan refunds typically credit back to your card within 3–10 business days after approval. Annual plan refunds for unused months are evaluated individually. Email support with your receipt, account email, and a one-sentence reason to start the process.
A Perplexity 'Too Many Requests' or 429 error means either you sent requests too fast (API: wait 60 seconds, then retry with backoff) or your weekly Pro search quota of 200 searches is exhausted (wait until Monday 00:00 UTC or switch to Standard search). Temporary burst limiting clears in under 2 minutes; quota exhaustion lasts until the weekly reset.
Perplexity Pro allows file uploads up to 50 MB per file, with a limit on total uploads per session or week. When your upload quota is exceeded, the fastest workarounds are: paste the text content of your document directly into the chat instead of uploading the file, split large documents into smaller chunks and upload them in separate sessions, or use URLs to share online documents rather than file uploads.
Perplexity Pro allows 200 Pro searches per week (reduced from 600 in May 2026) and 20 Deep Research reports per month; limits reset every Monday at 00:00 UTC. Free users get approximately 5 Pro searches per day. If you hit your cap, switch to Standard search mode to keep working until reset — Standard searches never count against your quota.
Perplexity has three separate usage limits depending on what you hit: Pro search quota (200 searches per week for Pro users, resets Monday 00:00 UTC), Deep Research quota (20 sessions per month for Pro users, resets on your billing date), and free tier Pro search (approximately 5 Pro searches per day, resets daily at midnight UTC). Standard searches on the free tier are unlimited. Identify which limit you hit, then follow the matching fix below.
Perplexity has two distinct restriction mechanisms that are frequently confused: usage limits (your weekly Pro quota of 200 searches is fully depleted — only resets Monday 00:00 UTC) and throttling (too many requests sent in a short burst — clears in 60 to 120 seconds without any quota impact). Distinguishing them is the first step: if Standard mode still works but Pro is blocked, it is a usage limit. If all searches fail briefly then recover, it is temporary throttling.
Try incognito mode, clear cookies for the service, disable extensions, and retry. If you use Google/Apple login, re-authorize the provider and check for outages.
Perplexity's 'Verification Limit Exceeded' error is a security lockout triggered when too many login verification attempts — email codes, SMS codes, or CAPTCHA completions — are made in a short period from the same IP address. The lockout typically clears after 1 hour. To reset it faster, switch to a different network (mobile hotspot) and attempt login from there; the lockout is IP-based, so a new IP bypasses it immediately.