To switch a model in Perplexity on the web, use the model control in the prompt box before submitting your request. The current documented route is the dropdown at the bottom right, then Custom and an available model. This guide covers that action; it does not assume the choice becomes a permanent default on every device.
Reviewed October 13, 2026. Web instructions follow Perplexity’s help article last modified September 24, 2026. Mobile layouts and account access can differ.
Check the task surface before choosing a model
Search, Deep Research and Computer are not interchangeable labels for the same workflow. Perplexity’s model-access documentation distinguishes them: Search offers eligible manual choices, while Deep Research selects models automatically. Check that you are following Search instructions in Search.
Also check that you are signed in to the intended account. A paid subscription on another login does not explain the options shown in this one. If you are in an organization, ask whether its administrator limits model availability.
Switch models in the web Search composer
- Open a new Search request while signed in.
- Open the dropdown at the lower-right of the prompt input.
- Choose Custom and select an available model. Review any reasoning or speed options shown.
- Check the displayed selection before submitting the question.
- Review the answer and its sources. Record the actual model information shown by the interface when comparing results.
Perplexity documents Best as automatic selection when no model is chosen. It is not a promise that a particular named model will handle every request. See the official model-switching instructions.
For a fair comparison, create separate test requests with the same prompt, attachments and source settings. A later follow-up has extra conversational context, so a better answer on the second attempt does not by itself prove the second model is better.
What to do on mobile or when a model is missing
The current official instructions cited above describe the web interface. This guide does not assume a fixed iOS or Android button position. Inspect the model or mode control near your app’s composer; if the available controls differ, use the documented web route as a reference and record the app version when asking support.
Scroll the table horizontally on narrow screens; keyboard users can focus its region.
| Symptom | First check | Next step |
|---|---|---|
| Only automatic selection appears | Account, plan and task surface. | Compare the live options with the current access guide. |
| A tutorial’s model is absent | Whether the tutorial names a retired or renamed version. | Choose an available option; do not assume an upgrade restores an old model. |
| Work account differs from personal | Organization restrictions. | Ask the administrator about enabled models. |
| Web and app differ | Login, app version and selected mode. | Report the exact difference without assuming your preference was lost. |
Verify the result, not the assistant’s self-description
Asking “Which model are you?” is not a reliable substitute for the product’s model display. Keep the selected option and any available response metadata with your test notes. If no model detail is exposed, record that limitation rather than guessing.
Do not infer quality from answer length. Check whether the result addresses the question, supports important claims with relevant evidence and follows your constraints. For code, use tests; for a research answer, open the cited documents.
This article explains one-time selection. To investigate whether a preference survives a new request, refresh or another device, use the separate default-model persistence checklist. For choosing between model families, use the model-picker comparison worksheet.
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: