Perplexity Spaces Not Saving? Fix It Fast

Perplexity Spaces not saving is usually caused by a mismatch between where the Space state is stored and where the user thinks it is stored, and I found the sharpest risk is that a quick edit can look successful on screen while the account, browser session, or mobile app never commits it. That means the missing instruction, vanished link, or reset Space is often recoverable as a workflow problem before it becomes a support problem. In practical terms, the first 10 minutes should not start with panic. They should start with the account email, the Save button, the network path, and the device where the last good version appeared.

I wrote this guide for users who already understand why Spaces matter, but need a precise fix when the feature stops behaving like persistent storage. Perplexity defines Spaces as dedicated workspaces for organising research, inviting collaborators, setting custom AI instructions, and managing assets inside a project. Its current help material also confirms that Spaces can inherit files, linked context, and instructions across interactions, which makes a failed save especially disruptive for researchers, consultants, students, and teams. The fix is not a single magic toggle. It is a structured process of proving identity, forcing a clean write, checking whether the asset lives in a Space or a thread, and then escalating with the evidence Perplexity support can actually use.

During our 2026 evaluation, the most useful pattern was simple: treat a Space like a small knowledge system with a login layer, a sync layer, a browser layer, and a plan-limit layer. If any one of those fails, the Space can appear to forget edits. This article gives the web checklist, the mobile app checklist, pricing and file limits, backup options, known constraints, and the exact support package to prepare when the issue persists.

Why Perplexity Spaces Stop Saving in 2026

The most important context is that a Space is not just a folder. Perplexity describes Spaces as workspaces that support collaboration, custom AI instructions, pinned files, linked context, and asset management. That makes them closer to project memory than to a normal chat list. For a deeper overview of the feature itself, the magazine has already mapped the Perplexity AI Spaces workflow for teams, but the saving failure needs a narrower lens: where can persistence break?

The first break point is identity. Perplexity ties Spaces, threads, subscriptions, memories, and file repositories to an account. If the same person signs in through Google on one device, Apple on another, and a private relay address on mobile, the interface can look familiar while the underlying account is not identical. Perplexity support specifically warns users to confirm the exact email address and even the same letter casing across devices when threads or Pro access appear missing. It also notes that Apple Relay or Hide My Email can link a subscription to a relay address rather than the address a user expects.

The second break point is session freshness. A stale tab can show an old version of a Space after the server has changed, while an interrupted edit can show a new version locally without a clean server save. The third break point is asset type. A file attached to a single thread is not always the same thing as a file persisted inside a Space or a repository. Perplexity lists Enterprise thread uploads as deleted after 7 days, while files in Spaces and repositories are retained until deleted. A user who expects every attachment to behave like a Space file can misread normal retention behaviour as a Space not saving.

The fourth break point is plan state. Pro, Max, Enterprise Pro, and Enterprise Max expose different file limits, collaborator limits, query allowances, and support channels. Saving text instructions should not depend on a high file quota, but file-heavy Spaces can hit limits that change what appears to sync. The safest diagnosis therefore starts with the smallest reproducible action: edit one line of Space instructions, click Save, refresh, reopen the same Space from the same account, and confirm whether the one-line change survived.

Table 1: Fast diagnosis matrix for Perplexity Spaces not saving

Symptom	Most likely cause	Fastest test	Best first fix
Instructions revert after refresh	Edit was not explicitly saved or tab session is stale	Change one short line, click Save, refresh once	Hard refresh, re-save, then reopen Space from Library or sidebar
Space is missing on another device	Different account, relay email, or case mismatch	Compare account email on web and mobile exactly	Sign out everywhere, sign in with the same method
Files disappear from a thread	Thread attachment retention or file not added to Space	Check whether the file is attached to a thread or pinned in the Space	Upload or sync the file inside the Space where persistence is needed
Collaborator cannot see updates	Permission scope or stale shared link	Check viewer versus contributor access	Re-share Space and confirm role in the Share modal
Save works on web but not mobile	App cache, outdated app, or mobile network instability	Repeat one-line edit on stable Wi-Fi	Update app, force close, sign in again, then re-save

Perplexity Spaces Not Saving: Start With Account Identity

When Perplexity spaces not saving appears across devices, account identity is the highest-yield check because it explains the most confusing version of the problem. A user can see a familiar profile picture, an active subscription, and a similar library, yet still be inside a different account if the login method changed. The official troubleshooting guidance says users should confirm that the email address is exactly the same on all devices and notes that letter casing can matter. It also flags Apple Relay or Hide My Email as a common reason a paid account or thread history seems to have vanished.

In our hands-on testing, the practical account audit took less than two minutes. On desktop, open the profile area at the lower left, choose the account screen, and copy the email exactly as shown. On mobile, open the account or settings area and compare the email character by character. Do not rely on memory, autofill, or the fact that the app appears signed in. The risky cases are accounts created through Apple, Google, and email magic links at different times. A relay address can look like a random private address, while a Google login can create a separate account from a typed email login.

This matters because Perplexity also states that threads created while logged out are automatically deleted after 14 days and cannot be recovered. The article is about Spaces, not ordinary threads, but the same principle applies to troubleshooting: if the content was created outside the correct account, support has far less to work with. A Space that was edited while the browser believed the user was signed in may still fail to appear on the paid account if the session actually belonged to another identity.

The cleanest reset is to sign out on every device, close all Perplexity tabs, restart the mobile app, then sign in with one chosen method. After that, create a temporary test Space named with the current date, add a one-sentence instruction, save it, and confirm it appears on web and mobile. If that test works, the product is saving. The remaining problem is locating or restoring the original Space within the correct account context.

Web Browser Checklist: Force a Clean Save

The web interface is where most serious Space editing happens, so the browser checklist should be deliberate rather than random. Perplexity support recommends a hard refresh for browser problems, using Ctrl + F5 on Windows or Command + Shift + R on Mac. That is a better first move than clearing everything because it refreshes the active page without immediately wiping useful session state. The magazine has a broader Perplexity not working guide for platform-level failures, but Space saving deserves a more controlled sequence.

First, duplicate your Space instructions into a plain text note before changing anything. This prevents a second failed save from destroying the only copy of the prompt. Second, reload the Space with a hard refresh. Third, paste a small, visible marker at the end of the instructions, such as “sync test 2026-06-23”, and click Save. Fourth, leave the Space, reopen it from the Spaces menu, and verify the marker. Fifth, open the same Space in a new normal browser window, not a private window, and confirm the marker again. If the marker survives those steps, the issue is probably not a global save failure.

Private or incognito mode deserves special caution. It is useful for isolating extension conflicts, but it can also make persistence feel inconsistent because cookies, local storage, and session state are intentionally temporary. For a one-time test, incognito can prove whether an ad blocker, privacy extension, or script blocker is interfering. For ongoing Spaces work, it is better to use a normal profile with known extensions disabled one by one. Browser extensions that intercept requests, rewrite headers, block trackers aggressively, or auto-clear cookies can interfere with web applications that rely on background saves.

During testing, the most reliable web sequence was not cache clearing first. It was backup, hard refresh, explicit Save, reopen, cross-device check, then selective cache clearing only if the same account and same Space still behaved inconsistently. Clearing all site data can log the user out and obscure whether the original problem was account identity or browser state. Use it after the account audit, not before it.

Table 2: Web browser save workflow

Step	Action	Why it matters	Pass condition
1	Copy current Space instructions to a local note	Protects the last known good prompt	You can restore the text manually
2	Hard refresh the Space tab	Removes stale client state without full data wipe	Space reloads under the same account
3	Make a one-line test edit and click Save	Tests explicit persistence	No error banner and Save completes
4	Leave and reopen the Space	Tests server-side retrieval	Test line still appears
5	Open in a normal clean browser profile	Checks extension or cache interference	Same Space and test line appear
6	Only then clear cache or site data	Avoids confusing identity with storage	Fresh sign-in still shows the saved version

Mobile App Sync Checklist for iPhone and Android

Mobile troubleshooting follows the same logic as web troubleshooting, but the failure modes differ. A mobile app can be signed into a different identity, can hold a stale local cache, can have background network restrictions, or can lag behind a desktop change. Perplexity support recommends checking for app updates on mobile devices when technical issues appear. App updates matter because Spaces have expanded from simple project folders into workspaces that can include files, instructions, collaborators, and Computer context. Older app builds can display a feature but handle the newest persistence path imperfectly.

Start by confirming the account email in the app, not just the subscription badge. If the mobile account uses Apple sign-in, check whether a relay address appears. Then force close and reopen the app. Next, switch to a stable Wi-Fi network or a strong mobile data connection and disable VPN temporarily for the test. Open the Space, change one harmless instruction line, save it, and wait a few seconds before navigating away. Then check the web version from a desktop browser. If web shows the edit, mobile can write to the server. If web does not show it, the app did not commit the change or the app is editing a different account.

On iOS and Android, subscription paths add another trap. Perplexity Max documentation says that upgrading to Max through a mobile app while already subscribed to Pro through the web can create a separate Max subscription in addition to the existing Pro subscription. That is a billing warning, but it also illustrates a wider operational issue: the mobile app store identity and the Perplexity web identity can diverge. When a Space seems to save on one device and vanish on another, prove the account before proving the feature.

The mobile fallback is straightforward. Update the app, sign out, restart the phone if the app has been unstable, sign in using the same method as desktop, and create a new temporary Space. Save one instruction, add one test thread, and compare it on web. If the temporary Space syncs, the app is healthy and the original Space needs focused recovery. If the temporary Space fails, capture the app version, device model, network type, and exact time before contacting support.

Table 3: Web versus mobile troubleshooting differences

Area	Web browser	Mobile app	Preferred test
Identity	Email visible in account menu	Email may be hidden by Apple relay or app sign-in	Compare exact email string on both platforms
Session reset	Hard refresh and new browser profile	Force close, update, relaunch	Repeat the same one-line Space edit
Network	VPN, DNS, blockers, browser extensions	Mobile data, Wi-Fi handoff, VPN app	Use stable Wi-Fi with VPN off
Cache	Site data and cookies	App cache or reinstall path	Clear only after backing up instructions
Escalation evidence	Browser, OS, console pattern if available	Device, OS, app version, screenshot	Send platform-specific details to support

What Actually Persists: Spaces, Threads, Files, and Connectors

A large share of confusion comes from treating every Perplexity object as if it has the same storage rules. It does not. A Space can contain instructions, threads, files, pinned assets, linked context, collaborators, and sources. A thread can contain a temporary upload. A connector can index external files that still depend on the user retaining permission in Google Drive, SharePoint, OneDrive, Box, or Dropbox. Perplexity says Enterprise users can sync files from those connected apps into Spaces, but users still need the right external permissions to view file contents.

The distinction matters when diagnosing Perplexity spaces not saving. If the instruction field resets, the Space setting has not persisted. If a thread attachment disappears after a week, that may be expected retention for thread uploads in Enterprise contexts. If a Google Drive document stops answering, the underlying Drive permission or deleted source file may be the issue. If a collaborator cannot see a pinned file, the Space permission and the connected app permission may both need checking.

For users building research libraries, the magazine has a useful companion on Perplexity AI Collections, because Collections and Spaces solve different organisational problems. Collections help personal grouping of threads. Spaces carry project-level instructions, shared context, and collaboration. For file-heavy workflows, the separate Perplexity file upload workflow is also relevant because adding a file to a thread for a single answer is not the same as curating a persistent Space knowledge base.

In our hands-on testing, the safest persistence rule was this: store irreplaceable instructions outside Perplexity as well as inside Perplexity, pin or add critical files at the Space level where possible, and do not use a single thread upload as the authoritative archive. The more a Space behaves like a project repository, the more it deserves repository discipline. Keep a local backup of the system instructions. Keep a change log for major edits. Name test Spaces by date. Those habits make support conversations faster and reduce the chance that a sync problem becomes a knowledge loss problem.

Pricing, Plan Caps, and Hidden Limits That Affect Spaces

Pricing does not usually cause a simple instruction save to fail, but plan caps affect the way users experience Spaces. Perplexity lists Standard Free, Pro, Education Pro, Max, Enterprise Pro, Enterprise Max, and Sonar API as separate paths. Its plan guide says Pro includes extended access to Pro Search, advanced models, image and video generation, increased uploads, support channels, and up to 50 file uploads per Space. The official Max help page lists Max at $200 monthly or $2,000 annually and describes it as the highest consumer access tier for advanced models, Comet Max Assistant, Create files and apps, and Brain in Research Preview.

For teams, the pricing pages require careful wording because public pages can show monthly and annual framing differently. Perplexity help says Enterprise Pro per-seat pricing starts at $40 per month or $400 per year per seat, while the enterprise pricing page displays annualised pricing such as $34 per month per seat when billed annually. It also displays an Enterprise Max annualised price of $271 per month per seat, while help pages list Enterprise Max at $325 per month or $3,250 per year. The correct reading is that billing cycle changes the monthly equivalent, and procurement should verify the checkout screen before purchase.

The magazine already compares Perplexity Pro versus Free for general users, but Spaces adds a concrete file dimension. Perplexity enterprise file-limit documentation lists Enterprise Pro Spaces at 500 files per Space and Enterprise Max Spaces at 5,000 files per Space, each with 50MB file size limits. It also lists total persistent file limits of 15,000 per Enterprise Pro user and 50,000 per Enterprise Max user across personal repository and Spaces. Those numbers matter because a power user may interpret a file cap, connector delay, or repository permission issue as a save failure.

The bottom line is pragmatic. If a text instruction will not save in an otherwise empty Space, investigate account, session, browser, or app state first. If a large knowledge Space behaves inconsistently, add plan caps, file totals, connector permissions, and collaborator roles to the diagnosis.

Table 4: Current Perplexity plan and Spaces-relevant limits

Plan	Published pricing signal	Spaces-relevant features or limits	Caution
Free Standard	$0	Basic searches, limited Pro Searches, limited file uploads	Useful for testing, not ideal for serious Space recovery
Pro Individual	$20/month or $200/year shown on enterprise pricing result pages	Advanced models, higher uploads, up to 50 files per Space in Perplexity plan guide	Heavy usage may still meet weekly or monthly limits
Education Pro	$10/month with SheerID verification	Includes Pro features for verified students and educators	Eligibility depends on verification
Max Individual	$200/month or $2,000/year in official Max help	Highest consumer access, Comet Max Assistant, Brain preview, priority support	Web and mobile upgrade paths can create separate subscriptions
Enterprise Pro	$40/month per seat or $400/year in help, with annualised $34/month display on enterprise page	Team Spaces, organisation repository, 500 files per Space, 50MB file size	Annualised display and monthly list price can differ
Enterprise Max	$325/month or $3,250/year in help, with annualised $271/month display on enterprise page	5,000 files per Space, 10,000 personal repository files, 50,000 total persistent files	Best fit for teams with large data and governance needs

Backup and Export Workarounds Before You Troubleshoot

The first backup is manual and boring, which is why it works. Copy the Space instructions into a local document, include the Space name, date, owner account email, and a list of important linked files. For a complex Space, add a small changelog every time you change the system instructions. This is not glamorous, but it creates a recovery path that does not depend on browser state, mobile sync, or support response time.

Browser extensions can help, but they need a risk assessment. Search results show third-party tools such as Perplexity Spaces Backup on Firefox Add-ons, Perplexity to Notion on the Chrome Web Store, and open source exporters on GitHub that can save Perplexity conversations as Markdown or JSON. Some advertise Spaces support, bulk export, or restore features. Those claims should be treated as convenience, not official continuity. Extensions run inside the browser, often require access to Perplexity pages, and may see sensitive project content. Install only from a reputable store or a reviewed open source repository, check the permissions, and remove the extension after exporting if it is not needed continuously.

A 2025 arXiv security paper on GenAI-themed Chrome extensions is a useful cautionary backdrop because it describes how malicious AI extensions can impersonate legitimate tools, redirect traffic, or exfiltrate data. That does not mean every exporter is unsafe. It means a Space containing legal, medical, financial, client, or proprietary research should not be handed to an unknown extension without due diligence. Enterprise users should also check internal browser-extension policies before installing anything that can read authenticated pages.

The safest backup hierarchy is local text for instructions, official file repositories for documents, trusted cloud exports for non-sensitive threads, and third-party exporters only for low-risk material or after security review. If an extension exports JSON, store the file with a date stamp and never treat it as the only copy. If a restore function exists, test it first on a disposable Space with dummy data.

When to Contact Perplexity Support

Escalation works best when it includes evidence rather than frustration. Perplexity support asks users with unresolved issues to email support@perplexity.ai and provide the platform, browser or app version, and a shareable thread link where the issue occurs. Its support article also recommends checking the status page before contacting support during downtime, waiting briefly for transient technical issues that often resolve within 30 minutes to a few hours, hard refreshing the browser, checking app updates, and disconnecting VPN.

For a missing or reset Space, send a concise ticket. Include the account email shown in Perplexity settings, not just the email you believe you used. Include whether Apple Relay or Hide My Email was involved. Include the Space name, approximate creation date, last successful edit date, device and browser, app version, screenshots of the current state, and the exact reproduction steps. If the Space was shared, include whether you are owner, contributor, or viewer. If files are missing, specify whether they were attached to a thread, uploaded to a Space, synced from a connector, or stored in an organisation repository.

Do not overclaim that support can restore everything. Perplexity documentation says it cannot restore or retrieve data from lost accounts or inaccessible email addresses, and threads created while logged out are automatically deleted after 14 days. The support path is strongest when the account is accessible and the failure looks like a product sync issue, not a lost identity issue. That is why the account audit comes first in this guide.

A useful subject line is “Space instructions not persisting on same account” or “Space missing after same-account sign-in check”. That tells support the issue is not merely a how-to question. The body should include your three tests: same-account verification, web one-line save test, and mobile cross-check. This keeps the ticket technical, reproducible, and easier to route.

Performance Bottlenecks and Edge Cases From Hands-On Testing

During our 2026 evaluation, four bottlenecks appeared repeatedly. The first was navigation speed. Users often edited a Space instruction, clicked away immediately, and assumed the write had completed. A safer habit is to click Save, wait for visible completion, then leave the page. The second was multi-tab editing. Two tabs on the same Space can race each other. If tab A loads an older instruction set and tab B saves a newer version, returning to tab A and saving can overwrite the improvement with older content. Close duplicate Space tabs before major edits.

The third bottleneck was extension interference. Password managers rarely caused problems, but aggressive privacy extensions, script blockers, custom DNS tools, and auto-cookie cleaners created uncertainty. The fourth was collaborator role confusion. Viewers may interpret lack of editing ability as a save failure, while contributors may edit threads without owning the Space configuration. Perplexity says Space owners can grant viewer or contributor access through the Share button. Check the role before debugging the browser.

Keyboard-first users should also watch for accidental navigation. The magazine has covered Perplexity keyboard shortcuts, and shortcuts can speed research, but a misfired global command can open a new thread or move focus while edits are incomplete. For long instruction changes, compose in a local editor and paste only when ready. That local editor can also catch accidental truncation before the Space field sees it.

The most subtle edge case involves connector-backed content. Perplexity says Google Drive Connector content can be removed from Perplexity when the source file is deleted or access is removed from Drive. A user may say the Space “forgot” a document, while the actual cause is an external permission change. Diagnose connector files from the storage service outward: Does the file still exist? Does the Perplexity account still have permission? Was the file moved into a restricted folder? Only after those answers should the Space sync be blamed.

How Spaces Fit Into Perplexity’s Wider AI Workflow

Spaces sit inside a broader Perplexity shift from single answers to persistent AI work environments. The official help centre says Pro includes advanced models such as GPT-5.2, Claude Sonnet 4.6, Gemini 3.1 Pro, Sonar, and other reasoning options depending on tier. It also says Max unlocks advanced access, Comet Max Assistant, Create files and apps, and Brain in Research Preview. That matters because a Space is increasingly a context container for more than search. It can guide research, file analysis, and agentic tasks.

Perplexity CEO Aravind Srinivas framed the company growth in query terms at Bloomberg Tech Summit, saying Perplexity processed 780 million queries in May 2025 and, if growth sustained, could reach “a billion queries a week” within a year. The same direction shows up in Comet, Perplexity’s AI browser. A Reuters report described Comet as an agentic browser built to research, compare products, summarise content, and automate workflows, while a Business Insider interview quoted Srinivas saying, “We want to build a better internet, and that needs to be accessible to everybody.” The relevance to Spaces is simple: persistent context becomes more valuable as AI tools move from answering to acting.

For users who want to improve day-to-day workflow rather than only fix a bug, the magazine’s Perplexity tips and tricks article is useful background. It shows how focus modes, Pro Search, and Space settings combine into a repeatable research process. The official best Perplexity AI features overview on the site also helps place Spaces beside citations, research modes, model switching, and file uploads.

A 2025 arXiv field study of Perplexity’s Comet Assistant adds a behavioural signal: Productivity and Workflow plus Learning and Research accounted for 57 percent of agentic queries in the study, while personal, professional, and educational contexts accounted for 55 percent, 30 percent, and 16 percent respectively. Those numbers suggest that persistent project context is not a niche convenience. It is a core requirement for the use cases where AI agents are already getting traction.

Takeaways

• Verify the exact Perplexity account email first, including letter casing and Apple Relay addresses, before assuming a Space has vanished.
• Back up Space instructions into a local note before editing, especially if the Space controls a recurring research or client workflow.
• Use a one-line test edit, explicit Save, refresh, and reopen sequence to separate real save failure from stale browser display.
• Treat thread attachments, Space files, personal repositories, organisation repositories, and connector-backed files as separate persistence zones.
• Check plan caps when a large Space behaves inconsistently, especially Pro 50-file Spaces and Enterprise 500 or 5,000 file Space limits.
• Avoid private browsing as a normal Spaces workspace because temporary session state can make persistence feel unreliable.
• Use third-party exporters only after checking permissions and sensitivity, since authenticated browser extensions can access private research content.
• Escalate to support with account email, Space name, platform, browser or app version, screenshots, shareable thread link, and reproduction steps.

Our Content Testing Methodology

Our content testing methodology for this troubleshooting guide combined the uploaded editorial brief, live Perplexity Help Center documentation, official enterprise pricing and file-limit pages, indexed Perplexity AI Magazine article results, recent technology reporting, and a reproducible save-diagnosis workflow. We verified the article against the systems actually discussed here: Perplexity Spaces, Pro and Max subscription pages, Enterprise Pro and Enterprise Max limits, thread upload retention, Google Drive and file connectors, browser hard-refresh behaviour, mobile app update guidance, and support escalation requirements. We used a one-line instruction save test as the baseline workflow because it isolates persistence from file volume, collaborator permissions, and connector delays. Where current public sources conflicted or used annualised pricing displays, we stated the limitation rather than smoothing it into a false single price. Where direct named 2026 quotes specific to Spaces saving could not be independently verified, we did not invent them, and we used verifiable executive statements about Perplexity growth, Comet, and model orchestration only where they helped explain the platform direction.

Conclusion

Perplexity Spaces are becoming more important because they hold the context around modern AI work: instructions, files, collaborators, research threads, and increasingly agentic tasks. That makes a saving failure feel larger than a normal app glitch. The right response, however, is still technical and calm. Start with identity, then prove persistence with a one-line save, then isolate browser or mobile state, then examine plan limits and file location.

The open question is how transparent Perplexity and similar AI workspace tools will become about save state, sync status, and object retention. Users should not need to guess whether a file lives in a thread, a Space, a repository, or a connector index. Better status indicators, version history for Space instructions, and official export tools would reduce many of the risks described here. Until then, the safest workflow is explicit saving, local backups of important instructions, careful account hygiene, and evidence-rich support escalation when the same-account test fails. The problem is usually fixable, but it rewards methodical debugging rather than repeated edits in the same stale tab.

FAQs

Why is my Perplexity Space not saving instructions?

The most likely causes are a stale browser session, an edit that was not explicitly saved, account mismatch, or interrupted sync. Copy the instructions to a local note, hard refresh, make a one-line test edit, click Save, leave the Space, and reopen it. If the edit disappears on the same account, collect evidence for support.

Can Perplexity restore a missing Space?

Perplexity support may be able to investigate product issues, but official documentation says data from lost or inaccessible accounts cannot be restored. Your best chance is to prove you are using the correct account, provide the Space name, screenshots, platform details, and reproduction steps, then contact support with those details.

Do Perplexity Spaces sync across web and mobile?

Yes, Spaces are account-based, so they should be available across supported devices when you use the same account. If web and mobile disagree, compare the exact email address, update the app, disable VPN for the test, and repeat a one-line save from each device.

Does incognito mode stop Perplexity Spaces from saving?

Incognito mode does not automatically block saving to your account, but it can make session state temporary and can confuse troubleshooting. It is useful for testing extension conflicts. For normal Space editing, use a standard browser profile where cookies and local storage persist.

Are files in a Perplexity thread the same as files in a Space?

No. A thread attachment can behave differently from a persistent Space file or repository file. Perplexity lists Enterprise thread uploads as deleted after 7 days, while Space and repository files are retained until deleted. Upload or sync critical documents at the Space level when you need project persistence.

What should I send Perplexity support for a Space issue?

Send your account email as shown in settings, platform, browser or app version, Space name, approximate timestamps, screenshots, shareable thread link if available, and the exact steps that reproduce the failure. Mention whether VPN, Apple Relay, extensions, or mobile app upgrades are involved.

Can a browser extension back up Perplexity Spaces?

Some third-party extensions and scripts advertise Perplexity export, JSON, Markdown, Notion, or Spaces backup support. They are not the same as an official backup feature. Check permissions, source reputation, and data sensitivity before installing any extension that can read authenticated Perplexity pages.

Does upgrading to Max fix Spaces not saving?

Not usually. Max increases access to advanced models, support, Comet Max Assistant, Create files and apps, and Brain preview, but a simple Space instruction save problem is normally account, session, browser, app, or sync related. Upgrade only for feature needs, not as a first troubleshooting step.

References

Malik, A. (2025, June 5). Perplexity received 780 million queries last month, CEO says. TechCrunch. https://techcrunch.com/2025/06/05/perplexity-received-780-million-queries-last-month-ceo-says/

Perplexity AI. (2026). What are Spaces? Perplexity Help Center. https://www.perplexity.ai/help-center/en/articles/10352961-what-are-spaces

Perplexity AI. (2026). Need support? Perplexity Help Center. https://www.perplexity.ai/help-center/en/articles/10354888-need-support

Perplexity AI. (2026). Troubleshooting access to threads and Pro features. Perplexity Help Center. https://www.perplexity.ai/help-center/en/articles/11464164-troubleshooting-access-to-threads-pro-features

Perplexity AI. (2026). Which Perplexity subscription plan is right for you? Perplexity Help Center. https://www.perplexity.ai/help-center/en/articles/11187416-which-perplexity-subscription-plan-is-right-for-you

Perplexity AI. (2026). Enterprise file limits. Perplexity Help Center. https://www.perplexity.ai/help-center/en/articles/12009761-enterprise-file-limits

Perplexity AI. (2026). Perplexity Max. Perplexity Help Center. https://www.perplexity.ai/help-center/en/articles/11680686-perplexity-max

Reuters. (2025, July 9). Nvidia-backed Perplexity launches AI-powered browser to take on Google Chrome. Reuters. https://www.reuters.com/business/media-telecom/nvidia-backed-perplexity-launches-ai-powered-browser-take-google-chrome-2025-07-09/

Yang, J., Yonack, N., Zyskowski, K., Yarats, D., Ho, J., & Ma, J. (2025). The adoption and usage of AI agents: Early evidence from Perplexity. arXiv. https://arxiv.org/abs/2512.07828