Perplexity Spaces Are Now Projects: Complete Workspace Guide
Perplexity Spaces have evolved into Projects—persistent workspaces that keep research sessions, Computer tasks, files, instructions, connectors and collaborators together. Existing Spaces were migrated automatically, so your previous work should now appear under Projects.
This page keeps the established “Perplexity Spaces” search term while using the current Projects terminology throughout.
What happened to Perplexity Spaces?
Spaces have not disappeared. Perplexity renamed and expanded them as Projects in July 2026, positioning the feature around ongoing work with Search and Computer.
Projects are the evolution of Spaces
A Project is a persistent, shareable hub where people and Perplexity can work from the same sessions, files, instructions and connected sources over time. Instead of recreating context in every conversation, you build a dedicated workspace around one client, campaign, subject or operational goal.
The current version goes beyond organising research threads. Projects can hold Computer tasks and artefacts, use project-scoped connectors and skills, maintain shared files, build ongoing context through Brain and connect work initiated from Slack or Microsoft Teams.
Perplexity Spaces vs Projects
The familiar workspace idea remains, but Projects add a stronger file, memory, Computer and team-collaboration layer.
How to create a Perplexity Project
A clear name, narrow purpose and useful default instructions make a Project much easier to reuse than a general dumping ground.
Open Projects
Choose Projects from the left sidebar, then select + New project. You can also use the plus option next to the Projects heading.
Name the workspace
Add a title of up to 50 characters, an optional description of up to 1,000 characters and an icon or colour for quick recognition.
Add instructions
Use up to 8,000 characters to define the objective, sources, style, output format, quality rules and how Computer should work inside the Project.
Add files and sources
Upload persistent files or folders, import from an available connector and prioritise useful web links or domains in the Project settings.
Choose access
Projects start as Restricted. Invite collaborators only after checking whether they need view or edit permission and which files they can access.
Start the work
Run a Search session or Computer task inside the Project. Pin important Projects so they remain easy to find from the overview and sidebar.
What can a Perplexity Project contain?
A Project combines several parts of Perplexity that would otherwise be scattered across separate conversations, files and settings.
Search sessions
Keep related questions, follow-ups, answers and citations together, allowing collaborators to return to the same research history.
Computer tasks
Run multi-step work inside the Project so created files, task history and outputs build on the same shared context. Computer usage consumes credits.
Persistent files
Upload individual files or folders and import supported connector files. Appropriate Project members can search and work from the shared material.
Instructions and sources
Apply reusable guidance to every query, prioritise selected websites or domains and set a default mode or Computer orchestrator model.
Brain and summaries
Where available, Brain builds evolving Project memory and a Project summary can provide a running status update. The owner controls automatic or manual runs.
Connectors, skills and channels
Scope connectors and reusable skills to the Project, add shared credentials where permitted and bind Slack or Teams channels to the workspace.
Project roles and sharing permissions
Access is role-based, and every new Project starts private. Share the workspace only as widely as the project requires.
Owner
Has full control over the Project, including context, settings, files, members and the available collaboration configuration.
Can edit
Can edit context, files, connectors, skills, people, defaults and channels. Use this role for active contributors, not passive reviewers.
Can view
Can read the Project and the sessions or files shared through it, without receiving the broader editing powers assigned to contributors.
Available access scopes
Perplexity Project file limits
Capacity depends heavily on the subscription. These published figures are useful when planning a knowledge base or collaborative research workspace.
Perplexity Project instruction templates
Paste a template into Project instructions, then replace the bracketed details. Keep rules specific enough to guide work without making every query rigid.
SEO research Project
StrategyWork as an evidence-led SEO research assistant for [site/brand]. Use British English. Prioritise current primary sources and our uploaded data. Separate verified facts from inference. Never invent search volume, rankings, traffic, authority scores or backlink counts. Cite material external claims and identify where Search Console or a specialist SEO platform is required.
Guest-posting and outreach Project
OutreachSupport publisher and outreach research for [campaign]. For each site, record audience, country, main topics, public contribution policy, source URL, evidence date and potential risks. Do not guess contact details or claim placement acceptance without a live source. Keep commercial notes separate from editorial-quality assessment.
Content hub Project
ContentHelp build a content hub about [entity/topic] for [audience]. Maintain one search intent per page, flag possible keyword cannibalisation, use a logical parent/supporting-page structure and recommend contextual internal links. Write in British English and provide claim-to-source notes before drafting publication-ready copy.
Using Perplexity Projects for SEO and guest posting
The best Projects represent durable workflows. Build one around a client or campaign rather than opening a new workspace for every small question.
Client knowledge hub
Store approved briefs, audits, service information, brand guidelines and reference sources so every research session starts with consistent client context.
Topical authority planning
Keep entity research, content maps, source notes and cannibalisation decisions together while separate sessions investigate supporting keywords and questions.
Outreach campaign workspace
Organise publisher research, campaign angles, policies and communication guidance. Keep live status and verified metrics in the appropriate CRM or spreadsheet.
SEO audit follow-through
Place crawl exports, issue notes and implementation guidance in one Project, then use sessions for technical, content and internal-linking workstreams.
Digital PR development
Collect datasets, media examples, subject-matter notes and campaign drafts so researchers and writers work from the same evidence base.
Editorial quality control
Apply consistent source, spelling, tone and fact-checking rules across content reviews while preserving the decisions and examples that shaped the standard.
Perplexity Project vs Session
A Session is one contextual conversation. A Project is the persistent workspace that can contain many Sessions, tasks, files and shared defaults.
Use a Session when…
The task is self-contained and does not need a durable shared environment.
Use a Project when…
Several pieces of work should continue from the same knowledge and rules.
Do not make every Project public
Restricted is the default for a reason. Link sharing can expose sessions and files to unintended readers if it is enabled carelessly.
Do not create one Project for everything
Mixed clients and unrelated topics weaken context, complicate permissions and make Brain or Project summaries less useful.
Do not assume connector access is pooled
Personal connector accounts and memory remain scoped to individuals. Shared files still follow Project and source-system permissions.
Do not leave files unmanaged
Remove outdated guidance, name files clearly and maintain a source owner. Persistent context becomes harmful when obsolete material looks authoritative.
Related Perplexity guides
Understand the main platform, choose a suitable plan and build stronger research workflows around your Projects.
Perplexity Spaces and Projects questions answered
Concise answers to the naming, migration, files, collaboration and privacy questions users ask most often.
Did Perplexity remove Spaces?
No. Perplexity evolved Spaces into Projects in July 2026. The core idea of a reusable workspace remains, with expanded support for Computer tasks, persistent files, Brain, connectors, skills and collaboration.
What happened to my existing Perplexity Spaces?
Perplexity says every existing Space was migrated automatically. Look under Projects in the left sidebar while signed into the same account or Enterprise organisation that owned the original Space.
Are Perplexity Projects private?
New Projects are Restricted by default, meaning only invited people have access. Owners can change the sharing scope, while Enterprise administrators may restrict public links, external invites and organisation-wide publishing.
How many people can join a Perplexity Project?
Perplexity lists up to five contributors for non-Enterprise Projects and up to 9,999 contributors for Enterprise-owned Projects.
What can I put inside a Perplexity Project?
A Project can contain Search sessions, Computer tasks, persistent files and folders, custom instructions, prioritised web sources, connectors, skills, shared credentials, collaborators and—where available—Brain memory and Project summaries.
How many files can a Perplexity Project hold?
Published limits vary by plan. Perplexity lists up to 50 files per Project for Pro, 500 files of up to 50 MB each for Enterprise Pro and 5,000 files of up to 50 MB each for Enterprise Max. Check your account for current consumer limits.
Can collaborators see my personal connectors and memory?
Perplexity says personal memory and connector accounts remain scoped to each individual. Material deliberately added or synchronised into a shared Project can become searchable to Project members, subject to Project and source-system permissions.
Does Brain cost credits inside a Project?
Perplexity states that Brain runs are billed to the Project creator. The owner can control whether Brain runs automatically or manually from the Memory area in Project settings.
Build Projects around work that continues
Choose a narrow purpose, add trusted files, write clear instructions and keep access restricted until collaboration is required. A well-maintained Project becomes reusable context; a cluttered one becomes another folder nobody trusts.
