Switching The Underlying Model In Pro

Perplexity Pro lets you choose which model writes the final answer from the retrieved passages — Sonar, Claude, GPT, Gemini, sometimes Grok. The retrieval step is the same; the writer changes. The same passages can produce noticeably different answers depending on the writer's training, length defaults, and refusal calibration.

When the model choice matters

1. 1Long-form synthesis: Claude tends to write longer, more structured answers; GPT often more direct
2. 2Sensitive topics: refusal patterns vary; some questions one model declines, another answers fine
3. 3Code-heavy answers: GPT and Claude both strong, but format different blocks differently
4. 4Reasoning-heavy questions: reasoning-tier models work the passages harder
5. 5Tone for an audience: pick the model whose default voice fits your reader

What the model does NOT change

If retrieval pulled the wrong sources, no model can save the answer. If a key paper is paywalled and never made it into context, switching from GPT to Claude doesn't recover it. The model picker is a writing-quality lever, not a retrieval lever.

Apply: build a default + escalation map

• Default model for daily queries: pick one and learn its quirks
• Long-form synthesis: assigned model
• Code-heavy: assigned model
• Disagreement check: a different model than the default
• Sensitive refusal: a third model with different calibration

The big idea: the model picker changes the writer, not the retrieval. Use it to fix tone and refusals, not to fix bad sources.