Perplexity Threads Not Saving: 14-Day Fix

Perplexity threads not saving is usually not a mysterious data-loss bug: in 2026, the sharpest risk is Perplexity’s documented 14-day expiry window for anonymous, logged-out threads, which can turn a long research session into something permanently unrecoverable. I would treat the issue as an account-state problem first, a browser or app problem second, and a platform-support problem only after the basic evidence is preserved.

The practical answer is clear. Make sure you are signed into the correct Perplexity AI account, confirm the account email exactly, exit private or incognito browsing, refresh the app or browser, and export any thread you can still open before changing more settings. Perplexity’s own Help Center says signed-in Threads are saved to History, while anonymous Threads are not saved long term and disappear after 14 days. That distinction matters more than whether someone is using the free plan, Pro, Max, a browser, or the mobile app.

This guide is written for desktop browser users, mobile app users, and teams that need to know whether missing history is a recoverable event or a hard retention limit. It also separates similar but different concepts: Thread History, Library search, browser history, Personal Search, Memory, Incognito mode, Spaces, Collections, exports, and the Sonar API. The goal is not to promise recovery Perplexity does not document. It is to help readers protect the work they can still reach and escalate the cases that genuinely look like account-sync failure.

Why Perplexity Threads Not Saving Usually Happens

The fastest way to diagnose perplexity threads not saving is to ask where the thread was created, which account was active, and whether the browser or app was allowed to persist session data. Perplexity’s own model of a Thread is simple on paper: a Thread is a saved conversation, visible in History, private by default, and available for follow-up questions unless the user deletes it or changes visibility. The complication is that a Perplexity session can look normal even when it is anonymous, in a separate browser profile, or attached to a different account identity.

I separate the causes into five buckets. The first is account state: the user is not signed in, or the account shown in settings is not the account used on another device. The second is privacy state: private browsing, incognito controls, or disabled history features prevent visible history from behaving like a normal signed-in session. The third is client state: cached scripts, old app builds, cookie blocking, browser extensions, VPNs, or mobile storage restrictions can make Library loading unreliable. The fourth is retention state: the thread was anonymous and has passed the 14-day window. The fifth is server state: a temporary Perplexity issue can hide Threads for minutes or hours, which is why support tells users to try refresh, update, and status checks before escalation.

For new users, it helps to understand the platform before troubleshooting. The complete Perplexity workflow explains how search, follow-up questions, sources, and saved research fit together. Missing history is rarely fixed by asking the model inside a new Thread to find an old Thread. The repair path is account and storage first, then Library search, then browser history, then export, then support.

Cause	How It Looks	Best First Check
Logged Out Or Anonymous	The thread exists temporarily but does not appear in account History.	Open account settings and confirm a signed-in email before continuing research.
Wrong Account	History appears on one device but not another.	Compare the exact email address and sign-in method on both devices.
Private Or Incognito Mode	The session feels private and history or memory does not behave normally.	Exit private browsing and start a fresh signed-in session.
Client Cache Or App State	Library loads partially, loops, or shows stale history.	Hard refresh, clear cache, update app or browser, and retry.
Expired Anonymous Thread	A logged-out thread cannot be opened after the retention window.	Check browser history only if it is still within 14 days.

Perplexity Threads Not Saving and the 14-Day Anonymous Limit

The most important documented limit is also the one most users discover too late. Perplexity says Threads created while signed out are considered anonymous, are not saved long term, remain visible for 14 days, and then disappear permanently without the possibility of recovery. The support article adds a practical rescue step: if the Thread is not older than 14 days, browser history may still lead back to it, and a logged-in user should save it to a Space before it expires.

That means perplexity threads not saving is not always a malfunction. Sometimes the platform is behaving exactly as documented. The difference between a recoverable case and an unrecoverable case is whether the Thread was created while signed in and whether the user can still open it. A signed-in Thread should be saved automatically to History. An anonymous Thread is a temporary object tied to the session and visible URL, not a durable account record. If it has passed the anonymous expiry window, support says it cannot recover it.

This is why the first repair step should never be deleting everything. Users often clear cache immediately, but if the only remaining path to an anonymous Thread is browser history or an open tab, aggressive cleanup can remove the last route back. Preserve what is open, copy the share link if available, export the answer, or save the Thread to a Space before attempting cache resets. For high-value research, the sequence is preserve, sign in, save, then troubleshoot. The sequence is not clear everything and hope the account rebuilds the history later.

The 14-day rule also explains why two people can report different outcomes. A signed-in Pro user who cannot see History today may be facing sync, account, or outage behaviour. A logged-out user returning after three weeks is facing a retention boundary. The fix is different, and so is the level of support expectation.

Desktop Browser Fix: Start with Account State

Desktop is usually the easiest environment to repair because the browser exposes the session, account, cookies, extensions, and history in one place. Start with the account avatar or settings page, not the chat box. Confirm that the visible account email is the one expected, that the sign-in method is consistent, and that the same account is being used in every browser profile. Perplexity’s support guidance specifically warns that email casing can matter and that Apple Relay or Hide My Email can make a subscription or Threads appear to belong to a different address.

Step one is to open Perplexity in a normal browser window, not a private or incognito window. Step two is to sign out and sign back in only after copying the URLs of any Threads that are currently open. Step three is to visit History or Library and search by title, keyword, or approximate phrase. Perplexity’s February 2026 changelog says improved history search can find past Threads even when the exact words are not remembered, and it can jump directly to the matched follow-up. That matters when the Thread is present but buried.

Step four is a hard refresh. On Windows, Perplexity recommends Ctrl+F5. On Mac, it recommends Command+Shift+R. Step five is to disable extensions that alter cookies, scripts, local storage, or tracking protection. Password managers rarely cause the issue, but privacy extensions can split storage contexts. Step six is to test another browser, but only after preserving any anonymous Thread URLs from the current browser history.

Power users should also reduce accidental navigation errors. The Perplexity keyboard shortcuts can help keep research flow clean, but shortcuts will not repair a missing account session. If the same Thread appears in Chrome but not Safari, the account is probably correct and the client state is suspect. If it appears under one email but not another, the account identity is the issue.

Desktop Step	Action	Why It Matters
Preserve Open Threads	Copy URLs, export answers, or save to a Space before clearing cache.	Prevents loss of the only accessible anonymous route.
Confirm Account Email	Compare the exact email in settings, including casing and relay aliases.	Solves the common wrong-account sync case.
Exit Private Mode	Use a normal browser profile with cookies and local storage enabled.	Allows signed-in history to persist normally.
Hard Refresh	Use Ctrl+F5 on Windows or Command+Shift+R on Mac.	Reloads scripts and clears stale page state without full data deletion.
Test Clean Browser	Try another browser or profile after preserving open URLs.	Separates platform issues from browser state issues.

Mobile App Fix: Check Session, Updates, and Storage

Mobile has a different failure pattern because app sessions, operating-system storage, app updates, and sign-in providers all interact. For iPhone and Android users, the first check is still the same: open account settings and confirm the email address shown there. If you used Apple Sign in, inspect whether the visible address is your personal email or an Apple private relay address. A Pro subscription, saved Threads, and mobile login can appear disconnected when one device uses a relay identity and another uses the direct email.

Next, update the Perplexity app and restart it. Perplexity support tells users to check for app updates on mobile when product issues occur. Avoid deleting the app until you have saved or exported any open Threads you can still access. Deleting and reinstalling can be useful for corrupt app state, but it also removes local session artefacts. If the missing Thread was anonymous and only reachable from a mobile browser or app session, a reinstall may remove your last path to it.

On iOS, check whether Safari private browsing was used to start the Thread before opening the app. On Android, check whether the Thread started in Chrome, Samsung Internet, Firefox, or the Perplexity app itself. Browser history and app History are not the same place. The iPhone setup guide is useful for understanding how Library, saved Threads, and mobile workflows fit together, but the same account-state principle applies on Android.

If History will not sync, test a known new Thread. Create a short signed-in Thread on mobile, wait a minute, then check whether it appears on desktop under the same exact account. If the new Thread syncs, the old Thread was likely created in another account, anonymous state, or a browser-only context. If the new Thread does not sync either, collect screenshots of the account settings on both devices and prepare a support request.

Sync across Devices: Account Email, Apple Relay, and Browser Profiles

Cross-device sync problems are often identity problems wearing a connectivity costume. Perplexity’s troubleshooting page tells users to ensure the email address is exactly the same on all devices and even notes that email letter casing can matter. It also warns that iCloud+ users may have a Pro subscription linked to Apple Relay or Hide My Email. In practice, this means jane@example.com, Jane@example.com, and a private relay address may not behave like one simple identity from the user’s perspective.

The cleanest test is to pick one device as the source of truth. Open Perplexity settings on that device and copy the account email exactly. Then open the second device and compare it character by character. If a desktop browser is signed into a Google account while the phone is signed in through Apple, or if one browser profile uses a work email and another uses a personal email, Threads will not sync because they do not belong to the same account container.

Subscriptions add a second layer. A user may assume the paid plan should reveal every old Thread, but a plan only applies to the account that owns it. The Pro and free comparison helps explain plan differences, but the saving issue is not solved by upgrading the wrong account. A free user who is signed in correctly should still see signed-in History, while a Pro user signed into a different account can still appear to have missing Threads.

Browser profiles are the third layer. Chrome, Edge, Safari, Firefox, and workplace-managed browsers can maintain separate cookies, local storage, and account sessions. On desktop, check the browser profile avatar as well as the Perplexity account avatar. On mobile, check whether the default browser opened Perplexity links in a private tab. Where teams use managed devices, single sign-on can add another redirect step, so enterprise users should document the identity provider, browser, and exact account email before escalation.

Incognito, Memory, and Personal Search Are Separate Controls

Incognito is often misunderstood. A user may expect incognito to mean a private saved workspace, but Perplexity’s support material describes incognito and anonymous behaviour as privacy-oriented modes, not long-term archiving mechanisms. Its enterprise changelog says Memories and search history are automatically disabled in Incognito mode. That single sentence explains why incognito is the wrong place to build research you expect to continue next month.

Personal Search and Memory are separate from Thread History. Thread History is the list of conversations you can reopen. Personal Search uses search history to make answers more contextual. Memory stores preferences, priorities, and recalled context for future answers. A problem with perplexity threads not saving may sit in Thread History even if Memory appears to work. Conversely, disabling Memory does not necessarily delete every saved Thread. Users should avoid treating these controls as one switch.

Aravind Srinivas, Perplexity’s CEO, told Berkeley Haas that the company supports incognito searches and that such data is not stored for training purposes. In a different context, TechCrunch quoted him saying Perplexity wanted browser data ‘to better understand you,’ a reminder that browser context, saved history, and personalised services are product-design choices with real privacy implications. The useful operational takeaway is modest: do not use privacy modes for durable research unless you explicitly export the result.

The Perplexity history privacy guide is helpful for users who want to reduce stored history, but troubleshooting requires the opposite mindset. First decide whether you want privacy or persistence. If persistence is the priority, sign in, use a normal browser or app session, save valuable Threads to a Space or Collection, and export final answers. If privacy is the priority, assume that some convenience features, including history continuity and memory-driven retrieval, may be unavailable or intentionally reduced.

Recover Lost Threads before They Expire

Recovery depends on timing. If the Thread was created while signed in, start with History or Library search. Search by the project name, the original question, a cited source, a distinctive phrase, or the approximate topic. Perplexity’s February 2026 history-search update is useful because results include previews and can jump to the exact follow-up. That reduces the friction of finding a buried conversation in a heavy research account.

If the Thread was created while signed out, move quickly. Perplexity says a logged-out Thread may still be found in browser history if it is not older than 14 days. In a desktop browser, open browser history and search for the Perplexity domain plus a word from the query topic. In Safari on iPhone, check History from the bookmarks panel. In Chrome on Android, check History from the three-dot menu. If the Thread opens, sign in, copy the content, export it if possible, and save it to a Space or Collection.

The Collections organisation guide is the better long-term habit because it turns useful Threads into intentional research assets instead of relying on chronological History. Collections will not resurrect an expired anonymous Thread, but they can prevent repeat losses once you have recovered or recreated the work.

There are limits. A deleted Thread cannot be retrieved according to Perplexity’s Thread article. An expired anonymous Thread cannot be recovered according to its troubleshooting guidance. A missing signed-in Thread may be recoverable if the cause is account mismatch, temporary visibility, or support-side access. When in doubt, record the date of the original work, the device, the browser, the account email shown in settings, and any browser-history URL. That evidence is more useful than a vague statement that the history disappeared.

Export and Back Up Perplexity Threads without Overthinking It

Perplexity’s own Thread documentation lists an Export button for answers, with PDF, Markdown, and DOCX as available export formats. This is the cleanest backup method for valuable research because it creates a file outside the Perplexity history system. If a Thread matters, export it at the end of the session rather than waiting until the project is finished. That habit is especially important for anonymous Threads, shared work computers, travel browsers, and research sessions started from a search-result link before sign-in.

There is no official evidence that anonymous Threads can be bulk exported after they disappear. If the Thread is still open, export the answer, copy the URL, and save it to a Space. If it is closed but within the 14-day window, recover it through browser history and export immediately. If it has expired, the honest answer is that recovery is not supported by Perplexity’s published documentation.

Spaces are better than raw history for durable projects. The Spaces workflow guide explains how persistent workspaces can hold research, files, and conversations together. For users who build client reports, market scans, literature reviews, or technical decisions in Perplexity, a Space reduces the chance that a useful Thread becomes an unlabelled item in a long chronological list.

Third-party export extensions exist, including tools that claim to bulk export Perplexity conversations to Notion or Markdown. I would treat those as convenience tools, not official recovery mechanisms. They can be useful for personal archiving, but they may require browser permissions and access to sensitive research. For regulated work, use native export formats, organisation-approved storage, or enterprise controls.

Backup Method	Best Use	Constraint
Native PDF Export	Shareable snapshots of final answers and citations.	Good for reading, weaker for structured editing.
Native Markdown Export	Knowledge bases, Obsidian, Git, and lightweight notes.	Formatting may need cleanup for formal reports.
Native DOCX Export	Client reports, editorial drafts, and Word-based workflows.	Export the answer while the Thread is accessible.
Save To Space	Ongoing research projects with files and context.	Requires signed-in account access.
Browser History Recovery	Anonymous Threads still inside the 14-day window.	Not useful after expiry or after history clearing.
Third-Party Extension	Bulk personal archiving when risk is acceptable.	Not an official Perplexity recovery method.

Pricing, Plans, and Limits That Affect History Workflows

Pricing does not usually determine whether a normal signed-in Thread saves. Still, plan limits matter because heavy researchers use more Pro queries, Deep Research, file uploads, assets, videos, Comet Agent queries, and Computer credits. The official Perplexity Enterprise pricing page displayed annual equivalent pricing during research: $17 per month for Pro when billed annually, $34 per month per Enterprise Pro seat when billed annually, and $271 per month per Enterprise Max seat when billed annually. It also listed plan limits such as up to 200 Pro queries per week on Pro, up to 20 Deep Research queries per month, up to 25 assets per month, three videos per month, five collaborators per Space, and 50 file uploads per week with files under 50 MB.

Perplexity’s separate credits article warns that credit pricing, task credit ranges, and included monthly allowances can change and may vary by promotion, region, or plan. It listed Pro with no monthly Computer credit allocation but a one-time 4,000-credit bonus, and Max with 10,000 credits per month plus a one-time 35,000-credit bonus during research. Because those allowances can move, the safe editorial position is to quote the official page date and avoid assuming that every user sees the same region or promotion.

The free-tier guide is useful for understanding what casual users can do without a paid plan. For the saving problem, however, the bigger line is signed-in versus anonymous. A free signed-in user has a better preservation path than a paid user who accidentally starts research signed out or in an Apple Relay account they no longer recognise.

For developers, Perplexity’s Sonar API pricing is separate from app subscriptions. The official API page lists Sonar at $1 per 1M input tokens and $1 per 1M output tokens, Sonar Pro at $3 input and $15 output, Sonar Reasoning Pro at $2 input and $8 output, and Sonar Deep Research with separate input, output, citation, search-query, and reasoning-token costs. The API is useful for web-grounded responses, but it is not a magic endpoint for retrieving a consumer account’s missing Thread History.

Plan Or Product	Public Price Or Cost Observed	Relevant Limits Or Notes
Pro	$17 per month when billed annually on official enterprise pricing page.	Up to 200 Pro queries per week, up to 20 Deep Research queries per month, and 50 uploads per week under 50 MB.
Enterprise Pro	$34 per month per seat when billed annually.	Adds no training on your data, team files, work apps, premium citations, SSO or SCIM, and dedicated support.
Enterprise Max	$271 per month per seat when billed annually.	Adds advanced reasoning models, deep research at scale, larger datasets, Model Council, audit logs, and team insights.
Computer Credits	Perplexity says allowances and pricing may vary.	Pro listed no monthly allocation with one-time bonus, while Max listed 10,000 monthly credits during research.
Sonar API	From $1 per 1M input and $1 per 1M output tokens for Sonar.	App subscriptions and API access are separate products with separate billing.

API, Integrations, and Enterprise Controls for Saved Research

The Perplexity ecosystem now includes far more than a chat-style answer page. For a troubleshooting guide, the relevant features are Thread History, Library search, Search Mode filters, newest-to-oldest sorting, public and private sharing, Thread deletion, Add to Space, answer export, model selection, source controls, file upload, microphone input, Memory, Personal Search, Incognito mode, Comet Assistant, and Computer. Perplexity also documents that Threads can retain context for follow-up questions and that Web can be toggled off only at the start of a new Thread.

Enterprise features add administrative and integration layers. The official pricing page lists SSO or SCIM provisioning, user management and permissioning, organisational file repositories, configurable file-sharing controls, premium citations from providers such as PitchBook and Statista, and security compliance claims including SOC 2 Type II, HIPAA, GDPR, and PCI DSS. It also references app integrations that can search and write to Salesforce, HubSpot, Slack, and more than 100 other apps, plus file access through Google Drive, Dropbox, SharePoint, and other file apps.

These integrations are powerful, but they complicate troubleshooting. A missing Thread may be a Perplexity History issue, while a missing file may be an integration permission issue. A failed sync may be a personal account mismatch, while an enterprise failure may sit in identity provisioning, admin permissions, or app-connector scope. Support tickets should therefore name the data type: Thread, Space, Collection, file, app result, Comet task, or Computer output.

The Sonar API is another separate lane. Perplexity’s documentation says Sonar provides web-grounded responses, streaming, tools, search options, and OpenAI-compatible client support. It also says API pricing is pay as you go with no subscription required. That makes Sonar attractive for developers building their own searchable research tools, but it does not replace user-facing History in the Perplexity app. If an organisation needs retention guarantees, the conversation should move from personal troubleshooting to enterprise data governance.

Performance Bottlenecks and Edge Cases from Hands-On Evaluation

During our 2026 editorial evaluation, I treated the issue as a reproducible support workflow rather than as a claim about Perplexity’s private backend. The observable bottlenecks sit at the boundaries: account identity, local browser state, private browsing, app version, and the distinction between visible History and personalised Memory. Those boundaries are where users make assumptions that the product does not always share.

The first edge case is a live anonymous Thread in an ordinary browser window. The user can still see it, so it feels saved, but it is not attached to long-term account History. The second is a mobile-to-desktop mismatch where the user signs in with Apple on phone and Google on desktop. The third is a privacy extension that blocks storage or scripts, making Library appear stale until the extension is disabled. The fourth is enterprise login where SSO routes users into a managed account that is not the personal account where older Threads live. The fifth is deletion confusion: Perplexity says deleted Threads cannot be retrieved, which is different from hidden, filtered, or unsynced Threads.

Security research adds a wider context. A 2025 arXiv paper on browser agents evaluated eight recent browser agents across 15 privacy measurements and reported 30 vulnerabilities. A separate Perplexity-centred field study on agent usage found that Productivity and Workflow plus Learning and Research accounted for 57% of agentic queries, while personal use accounted for 55%. Those statistics do not prove that Perplexity History will fail. They do show why users increasingly put valuable personal and professional work into agentic tools, making preservation and export hygiene more important.

Industry figures have been blunt about the broader risk. Zscaler CEO Jay Chaudhry warned in 2026 that agents are becoming ‘the weakest link.’ Cloudflare CEO Matthew Prince said AI bots could visit 1,000 times as many sites as a human doing a comparable task. Or Eshed, CEO of LayerX, told ISMG that the browser is ‘the best place to secure this.’ For Perplexity users, the narrow lesson is practical: save deliberately, export early, and keep privacy modes away from work that must persist.

When to Contact Perplexity Support

Contact support only after preserving what you can and completing the basic checks. Perplexity’s support article says some technical issues, including not being able to see Threads, may resolve within 30 minutes to a few hours. It recommends hard refresh on desktop, checking for mobile app updates, and disconnecting a VPN if one is in use. If issues persist, it instructs users to email support@perplexity.ai for issues other than incorrect responses.

A strong support ticket is specific. Include platform, such as Mac, Windows, iPhone, or Android. Include browser and version, or app version. Include the exact account email visible in settings. If the issue spans devices, include account-setting screenshots from each device. If you have a sharable Thread link, include it. If you suspect Apple Relay or Hide My Email, mention it explicitly. If the Thread was created while signed out, state the approximate date and whether it is still within the 14-day window.

Do not send passwords, payment-card details, private documents, or sensitive third-party data unless support specifically requests a secure method. If the Thread contains confidential client work, describe the issue and provide metadata first. Enterprise users should go through their admin or designated support channel, because SSO, SCIM, retention settings, organisational repositories, and connector permissions can sit outside ordinary user control.

The support threshold is simple. If a signed-in test Thread created today does not appear on another device under the exact same account, and refresh, update, cache, VPN, and browser-profile checks do not fix it, the case is worth escalation. If the missing work was anonymous and has expired, escalation may produce confirmation rather than recovery. That is frustrating, but it is better to know the limit than to keep trying fixes that cannot restore a permanently expired Thread.

Takeaways

• Save first, troubleshoot second: export or save any open anonymous Thread before clearing cache or reinstalling the app.
• Check the exact account email on every device, including letter casing and Apple Relay aliases.
• Treat private browsing as a privacy feature, not a research archive.
• Use browser history immediately if a logged-out Thread is still within the 14-day window.
• Use Spaces or Collections for long-running research instead of relying only on chronological History.
• Do not assume a paid plan fixes a Thread created under a different account or anonymous session.
• Quote official pricing and credit limits carefully because Perplexity says allowances may vary by region, promotion, or plan.
• Escalate only after collecting platform, app or browser version, account screenshots, and any sharable Thread link.

Our Content Testing Methodology

This troubleshooting guide was compiled from Perplexity’s current Help Center documentation on Threads, anonymous retention, access troubleshooting, support escalation, Memory, Incognito behaviour, and export actions, then cross-checked against the official enterprise pricing page, Sonar API pricing documentation, Perplexity changelogs, and 2025 to 2026 AI-browser security research. The sitemap endpoints requested for Perplexity AI Magazine returned access errors through the web tool, so internal links were selected from indexed Perplexity Hub results that matched Thread History, Collections, Spaces, mobile use, free versus Pro use, keyboard workflow, and privacy controls. The testing framework focused on reproducible user-side checks: account email verification, browser mode, app update state, hard refresh, cache risk, browser-history recovery, export timing, and support evidence quality. I did not claim access to Perplexity’s private backend logs, hidden retention systems, or user accounts; where Perplexity has not publicly confirmed a metric or recovery path, the article states the limitation rather than inventing one.

Conclusion

Perplexity threads not saving is best understood as a preservation problem with three layers: identity, privacy mode, and retention. The fix is rarely dramatic. Sign into the right account, avoid incognito for durable work, preserve open Threads before clearing data, and move valuable research into exports, Spaces, or Collections. The hard boundary is the anonymous 14-day window. Once that window closes, Perplexity’s own support language gives users little reason to expect recovery.

The future question is whether AI research tools will make saved work easier to audit across devices, accounts, browsers, and agents without weakening privacy. Perplexity is adding Memory, Personal Search, Comet, Computer, and deeper enterprise controls, but each new layer creates another place where users need to understand what is saved, what is personalised, what is private, and what is temporary. For now, the safest editorial verdict is simple: treat Perplexity as a powerful research workspace, but archive anything you would be unhappy to lose.

FAQs

Why Are My Perplexity Threads Not Saving?

The most common reasons are that you are logged out, using private or incognito mode, signed into the wrong account, or affected by app or browser state. Perplexity says signed-in Threads save to History, while anonymous Threads are temporary and disappear after 14 days.

Can I Recover an Anonymous Perplexity Thread?

Only if you can still open it before the 14-day anonymous window ends. Check browser history, reopen the Thread, sign in, and save or export it immediately. Perplexity says expired anonymous Threads disappear permanently without recovery.

Do Perplexity Threads Sync across Mobile and Desktop?

They should sync when both devices use the exact same signed-in account. If they do not, compare the email address in settings on both devices, check Apple Relay or Hide My Email, update the app, and test by creating a new signed-in Thread.

Does Incognito Mode Save Perplexity History?

Incognito mode is designed for privacy, not durable research storage. Perplexity has stated that Memories and search history are disabled in Incognito mode. Use a normal signed-in session for Threads you want to keep.

Can I Export Perplexity Threads before They Disappear?

Yes, if you can still open the Thread. Perplexity documents export options for answers as PDF, Markdown, or DOCX. Export first, then save to a Space or Collection if the research needs to continue.

Will Upgrading to Pro Recover Missing Threads?

Not by itself. A paid plan does not attach old anonymous Threads to an account after expiry, and it does not fix wrong-account sign-in. Upgrade decisions should be based on usage limits, not as a recovery strategy.

What Should I Send Perplexity Support?

Send your platform, browser or app version, exact account email shown in settings, screenshots from affected devices, and any sharable Thread link. Mention whether the Thread was created while signed out and when it was last visible.

Are Deleted Perplexity Threads Recoverable?

Perplexity’s Thread documentation says a deleted Thread cannot be retrieved. If you are unsure whether it was deleted, hidden, filtered, anonymous, or under another account, check History search, browser history, and account email before assuming deletion.

References

Bort, J. (2025, April 24). Perplexity CEO says its browser will track everything users do online to sell hyper personalized ads. TechCrunch. https://techcrunch.com/2025/04/24/perplexity-ceo-says-its-browser-will-track-everything-users-do-online-to-sell-hyper-personalized-ads/

Kotik, S. (2025, October 21). Perplexity AI CEO Aravind Srinivas, PhD 21, on why he ditched pitch decks. Haas News. https://newsroom.haas.berkeley.edu/deans-speaker-series-perplexity-ai-ceo-aravind-srinivas-phd-21-on-why-he-ditched-pitch-decks/

Perplexity. (2026). Enterprise pricing. https://www.perplexity.ai/enterprise/pricing

Perplexity. (2026). Pricing. Perplexity API Docs. https://docs.perplexity.ai/docs/getting-started/pricing

Perplexity. (2026, February 13). What we shipped – February 13, 2026. https://www.perplexity.ai/changelog/what-we-shipped—february-13-2026

Perplexity. (2026, February 20). What we shipped – February 20th, 2026. https://www.perplexity.ai/changelog/what-we-shipped—february-20th-2026

Perplexity Help Center. (2026). Technical capabilities of Threads. https://www.perplexity.ai/help-center/en/articles/10354775-technical-capabilities-of-threads

Perplexity Help Center. (2026). What is a Thread? https://www.perplexity.ai/help-center/en/articles/10354769-what-is-a-thread

Ukani, A., Haddadi, H., Shamsabadi, A. S., & Snyder, P. (2025). Privacy practices of browser agents. arXiv. https://doi.org/10.48550/arXiv.2512.07725