You can choose a preferred model in Perplexity’s web prompt box, but that is not proof of a permanent account-wide default. Current official instructions document the composer selector; they do not establish that a Settings → Account → Default Model option exists for every user or synchronizes across every device.
Reviewed October 13, 2026. This guide explains selection and a repeatable persistence check, without promising an undocumented permanent setting.
Understand what “default” can mean
A default might mean automatic routing, a remembered choice in the current interface, or an explicit saved preference. These are different behaviors. Before troubleshooting, write down which one you want: the same model for the next request, every new thread, a particular project, or every device.
Perplexity’s current preferred-model help article describes the web composer and its Custom selection. When no model is selected, Best lets the service choose. The guide does not document universal cross-device persistence.
Select your preference for the next request
- Sign in to the account you intend to use and open the Search composer.
- Open its lower-right model dropdown and choose Custom.
- Select an available model, checking any reasoning or speed settings offered.
- Confirm the visible selection before submitting a harmless test question.
If your interface also offers an explicit saved preference, follow its displayed instructions and save confirmation. Do not assume a setting exists because an older article names it. If you cannot find it, the composer route still lets you inspect the choice before an important request.
For help locating the web controls, see how to switch models. This article’s main purpose is to establish what happens after that choice.
Check what survives a new request or device change
Use one small test per step and record the visible selector before sending. There is no need to delete cookies, reset the app or recreate your account.
Scroll the table horizontally on a narrow screen; keyboard users can focus the table region.
| Test | Record | What it establishes |
|---|---|---|
| Second new request | The model or automatic option shown. | Whether a new request retains the choice in this interface. |
| Refresh the page | The selection after reopening the composer. | Whether a refresh changes it. |
| Open a different thread | The displayed selection before the next prompt. | Whether behavior differs by thread. |
| Check another device | Account, app version, mode and selection. | Behavior on that device—not a promise for all devices. |
If the selection changes at a particular step, that is the useful result of the test. Check it at that boundary in your routine. A preference remembered in one browser session is still useful, but should not be described as an account-wide guarantee.
When the choice is unavailable or does not stick
Check the active login, subscription, selected task surface and any organization restrictions. Consult the current subscription guide rather than assuming that every model mentioned in an old tutorial is part of your plan.
If the same account behaves differently in the app and on the web, record both versions and the exact step that changes the choice. Give support this minimal reproduction. Do not include private source documents or full work conversations when a sanitized test demonstrates the issue.
Do not infer the selected model from the assistant’s prose or from its answer to “What model are you?” Use the product controls and any response metadata it exposes. If the interface does not show enough information, mark the result unverified.
Keep source preferences and project settings separate
Choosing a model does not specify which documents or websites should support the answer. Inspect source controls independently. For a repeated research task, save your evaluation checklist and permitted sources, then confirm the model before each important run.
A workspace-specific question belongs to the separate Space and Project model-settings guide. Do not assume a Search preference locks every model used in a Computer task or overrides another collaborator’s account.
The safest practical default is an observable one: a choice you can see, test and recheck. If you cannot confirm persistence, selecting the model before submitting is more reliable than relying on an undocumented setting.
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: