Official documentation checked October 14, 2026.
Before deleting a Perplexity Space or Project, preserve the material you need and confirm what the current deletion dialog will remove. Do not assume that sharing a link creates a backup, or that deleting the container proves every related session and server copy has been erased.
Perplexity’s current documentation uses Projects for these workspaces. The public guide does not establish a universal project-deletion path or recovery guarantee across the current layouts. This guide therefore explains the checks to complete before confirming removal, without inventing a button location.
Identify the Project and the Intended Change
Open the intended account and Project. Record its title, URL and owner. Decide whether you need to delete the workspace, remove one session, remove a file, or change sharing. Those are different operations.
The current Projects guide describes personal and Enterprise layouts with different settings. If an older tutorial’s Space card does not match your screen, stop following its click sequence rather than substituting an account-deletion control.
Preserve an Independent Copy of Essential Material
Open important sessions and save the answers, original prompts and source references you need. Perplexity documents answer export to PDF, Markdown or DOCX in its Session guide. An exported answer is not necessarily a complete Project backup.
Save required files and instructions separately using the controls available for those items. Inspect the saved copies and keep them in an appropriately restricted location. A URL, a browser tab or another member’s access to the same Project is not an independent content copy.
For broader account data, the documented Export my data option can provide an account export. Verify its actual contents before relying on it; do not assume it is a one-click Project restore package.
Check Collaborators, Files and Connected Work
Coordinate with the owner and collaborators before removing shared work. Check active tasks, important outputs and linked services. Deleting a Project should not be used as an undocumented way to cancel every task or revoke every external credential.
Files brought into a Project from connectors can be one-time copies. A change to the external original does not necessarily change the Project copy. Keep source-system cleanup and Project cleanup as separate, verified tasks.
Read the Actual Deletion Confirmation
If the current Project interface offers deletion, check that the action names the intended Project, then read the confirmation’s scope and warnings. Proceed only when you own or are authorized to remove that work and have preserved what is needed.
The current public Projects guide does not specify which associated items survive a Project deletion. Do not fill that gap with an assumption that all sessions are deleted—or that all survive. If the dialog does not make the effect clear, cancel and ask the owner or Help → Contact Support before acting.
Do not test a production Project’s recovery behavior by deleting it. There is no verified universal undo window on which to base that decision.
Verify the Result at the Correct Scope
After an intentional removal, refresh the Project list and check the exact URL and account. If your objective includes removing specific conversations, inspect those conversations separately in History. Do not treat a missing sidebar entry as proof of complete data erasure.
Saved exports and copies outside Perplexity remain separate. A product deletion action is not a guarantee that collaborators’ downloaded files or legally retained records disappear.
If the Project Is Already Missing
First check the account and workspace, access changes and any surviving sessions. Use Perplexity’s missing-session guidance to distinguish account confusion from actual session deletion.
Give official support the Project URL, approximate time and the action taken, without sharing private contents publicly. Support can investigate the case, but recovery must not be promised. Do not delete more content or publish a private link to an external archive while trying to recover it.
Glad it helped. Take a short break with a game:
Sorry about that. Search for the exact error message, or look for a tool that checks your device: