If you are looking for a default model setting in a Perplexity Space, first check which workspace experience you have. Perplexity now describes Spaces as Projects. A model dropdown documented for the older Space creation screen is not a reliable guide to a current Project or Computer task.
Reviewed October 13, 2026. This guide separates the documented legacy Space setting from the current Projects experience. It does not promise a project-wide model lock.
What changed from Spaces to Projects?
Perplexity’s current Projects page says existing Spaces migrate automatically, carrying their threads, files and history. Projects organize continuing work with shared files, context and connected sources. You do not need to rebuild a workspace simply because the name changed.
The older official Spaces guide did describe choosing a model while creating a Space for eligible paid users. That is historical documentation, not evidence that the same dropdown still appears in every current account.
Keep three questions separate: where the work is organized, which sources a task can use, and which model handles a request. A Project name or instruction does not by itself answer the last question.
Check the model for a current Project task
- Open the existing workspace and confirm that its expected files and conversations are present. Do not delete or recreate it to recover a missing setting.
- Identify the task surface you are using. Search and Computer do not necessarily expose the same model controls.
- Inspect the selector available in that task’s composer. Use an eligible option shown by your account, rather than typing an old model name into the instructions.
- Review the selected sources and permissions independently of the model choice.
- Run a small, non-sensitive test. Record the selected option and inspect any model information the interface provides.
Perplexity distinguishes model availability across Search, Deep Research and Computer in its model-access guide. A selection in one surface should not be treated as a guarantee about every model used by a multi-step workflow.
If your interface still shows the older Space controls
The legacy creation instructions were: open Spaces, create a Space, enter its details and choose an available model if your plan offered that control. Use that route only when it actually matches your screen. The old guide does not justify inventing an edit-menu path for a different interface.
If an existing Space exposes an editable model preference, note the original choice before changing it. Start a new test request afterward and check the visible selection. Do not assume the preference rewrites previous answers, overrides collaborators’ entitlements or governs a separate Computer workflow.
For a shared workspace, ask a collaborator to check their own selector if consistent behavior matters. Describe the intended task and sources in shared instructions, but do not use instructions such as “You are model X” as proof that the selected model changed.
Test whether the preference persists
A visible selection for one request is not proof of an enduring workspace default. Use this small checklist without modifying the project’s real work:
- Start a second new request in the same workspace. Inspect its selector before sending.
- Open a different workspace and compare the selector. Record any difference rather than assuming a global setting.
- Refresh the original workspace and check again.
- If you use a mobile or desktop app, inspect it separately. Do not infer cross-device persistence from the web result.
If the selected option changes, keep checking it before important requests and consult support with the app version, plan and task surface. Avoid including confidential prompt contents in a support screenshot.
Which setting are you trying to control?
On small screens, scroll this table horizontally or focus it and use the arrow keys.
| Your goal | What to inspect | What not to assume |
|---|---|---|
| Reuse project evidence | Files, connected sources and project instructions. | That a preferred model can access every source. |
| Select a model for a request | The selector for the current task surface. | That a historical model roster is still available. |
| Keep a preference | A new-request and refresh test. | That one selection applies to all future tasks and devices. |
| Share a workflow | Each collaborator’s access and the agreed evaluation criteria. | That the owner’s subscription transfers to everyone. |
For the current web Search picker, see how to switch models in Perplexity Pro. For preference persistence outside a project, see how to check your default model preference.
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: