Claude Opus 5 vs Fable 5 vs Sonnet 5: Which Should You Use?

The practical Claude choice is no longer a three-way contest between Fable 5, Opus 4.8, and Mythos 5. For normal app, Claude Code, and API buyers, the current decision is Sonnet 5 versus Opus 5 versus Fable 5. Opus 4.8 matters as a migration baseline, while Mythos 5 remains an access-gated route rather than a self-serve option.

The short answer is to start with Sonnet 5 when responsiveness and volume dominate, move to Opus 5 when difficult work makes failed attempts or extra human review expensive, and reserve Fable 5 for workloads where a matched evaluation proves that its additional capability is worth the higher price and stricter operating boundary. Anthropic's own model guide starts complex agentic coding and enterprise work on Opus 5, but that positioning is a starting hypothesis, not proof that one model wins every workload.

Start with the job, not the model name

Sonnet 5 is the throughput choice. Anthropic positions it as the best combination of speed and intelligence, lists it as fast relative to the other current models, and prices it below Opus 5. It is the sensible baseline for interactive assistants, routine coding, high-volume extraction, and agent loops where latency or token spend compounds across many calls.

Opus 5 is the quality-first daily model. Anthropic positions it for complex agentic coding and enterprise work, while keeping its standard API price at the Opus 4.8 level. It is the stronger starting point when a task is ambiguous, long-running, tool-heavy, or expensive to review, but it should still be compared with Sonnet 5 on the actual work.

Fable 5 is the capability-ceiling route. Anthropic describes it as its most capable widely released model and targets long-running agents, but it costs twice Opus 5 per input and output token. It also carries model-specific retention requirements and stricter safeguards. That makes Fable a specialized escalation, not the automatic premium default.

Anthropic publishes benchmark and safety evaluations for all three models. Those results are useful vendor evidence about intended positioning, but they are not independent comparative testing. Use them to form an evaluation plan, not to declare a universal benchmark winner.

Specs that change the decision

The shared context and output limits remove a common but misleading selection shortcut: choosing the more expensive model does not buy a larger advertised window among these three. The real differences are capability profile, latency orientation, token price, effort behavior, access, and governance.

Per-token price is also not the same as cost per completed job. A slower or more expensive model can be economical if it needs fewer retries, fewer tool calls, or less review. A cheaper model can become costly if a long agent loop repeatedly fails. Measure input tokens, output tokens, elapsed time, retries, tool calls, and human correction together.

Treat Sonnet 5's introductory price as a temporary acquisition window. A production decision should still work at its published standard US$3/US$15 rate, because the US$2/US$10 rate ends after August 31, 2026.

Choose Sonnet 5 for speed and scale

Choose Sonnet 5 when most tasks are repeatable, latency-sensitive, or high-volume. It is the first model to try for customer-facing chat, broad internal assistants, routine coding changes, extraction pipelines, and agents whose economics depend on many inexpensive steps. Its lower standard price leaves more room for retries, caching, or parallel attempts.

Sonnet 5 is also the easiest family baseline for evaluating whether more capability changes the outcome. Run it at the same effort level and with the same tools as Opus 5. If it meets the quality threshold, the faster latency orientation and lower price usually make the selection straightforward.

Do not promote Sonnet solely because Anthropic says its performance approaches older Opus models on some evaluations. That is a vendor claim tied to specific harnesses and effort settings. The buyer-relevant question is whether Sonnet clears the acceptance bar on the exact workload at the standard price that will apply after the promotion.

Choose Opus 5 for difficult everyday work

Choose Opus 5 when the task is difficult enough that judgment, persistence, or self-correction matters more than the lowest token rate. Complex repository work, multi-step research, professional document analysis, and enterprise agents with costly failure modes are better candidates than routine transformations.

Opus 5 sits at a useful middle boundary: it is half Fable 5's standard token price, has a moderate rather than slower latency orientation, and does not carry Fable's model-specific 30-day retention requirement. Anthropic also made it the default model on Claude Max and the strongest model available on Claude Pro, which signals its intended role as the everyday premium choice in the Claude app.

For latency-sensitive premium work, Anthropic offers Opus 5 Fast mode at about 2.5 times the default speed. That route costs twice the base Opus API price and can consume usage credits in Claude Code, so compare it with Sonnet 5 rather than treating speed as a free toggle.

Choose Fable 5 only for measured headroom

Choose Fable 5 when long-horizon autonomy, unusually difficult reasoning, or frontier-level capability is the primary constraint and a representative evaluation shows a material gain over Opus 5. The evaluation should use the same prompt, tools, effort, stopping conditions, and review rubric for both models.

The price boundary is simple: Fable 5's standard US$10 input and US$50 output rates are twice Opus 5's US$5 and US$25 rates. The purchase case therefore needs to come from better task completion, lower correction cost, or access to work Opus cannot reliably finish—not from the prestige of the tier name.

Fable also changes the governance decision. Anthropic designates Fable 5 and Mythos 5 as Covered Models that require 30-day retention and cannot be used under zero data retention. A ZDR organization can enable the required retention for a specific workspace, but that is an explicit privacy and compliance choice, not a model dropdown change.

Stricter safety classifiers can also refuse or reroute some requests. In Claude surfaces, Anthropic may fall back from a flagged Fable request to another model; API users need to handle refusal details or configure an eligible fallback path. For cybersecurity, biology, or other sensitive workflows, confirm which model actually answers and whether the resulting behavior remains acceptable.

Effort changes the model you are buying

Fable 5, Opus 5, and Sonnet 5 all support the low, medium, high, xhigh, and max effort levels. High is the API default. Effort affects thinking, visible output, and tool calls, so it changes both capability and cost; it is a behavioral signal rather than a strict token budget.

Start a family comparison at high effort, then sweep downward or upward only where the workload justifies it. Sonnet at high may beat Opus at low for one task, while Opus at high may avoid retries that make Sonnet more expensive in practice. A model comparison without matched effort is partly an effort comparison.

Fable's adaptive thinking is always on. Opus 5 and Sonnet 5 also use adaptive thinking by default, but Opus 5 cannot disable thinking at xhigh or max. Applications that hard-code older thinking settings need a compatibility check before a model change.

Max effort is not a default buying recommendation. It allows unconstrained token spending for the deepest work. Use it only when a measured quality gain matters more than the added latency and cost, and set output limits with enough room for thinking and tool use.

Claude app, Claude Code, API, and cloud routes

Access depends on both model and surface. Sonnet 5 is the default on Claude Free and Pro and is available on Max, Team, and Enterprise. Opus 5 is the default on Max, is the strongest model on Pro, and is offered across Anthropic's platforms. Fable 5 is available in Claude, Claude Code, and Cowork, but its current subscription route uses usage credits after the introductory included window; plan and organization entitlements still apply.

Claude Code's model selector supports Sonnet 5, Opus 5, Fable 5, and Opus 4.8. Use the /model menu or a model flag to make the choice explicit, then check /status so an evaluation does not accidentally run against a different model or billing route.

A paid Claude app plan does not include direct Claude API access. Console and API usage are billed separately, and Claude Code can use either a supported subscription allocation or API credits depending on authentication and account state. Keep app entitlement, Claude Code usage, and direct API spend as separate budget lines.

For developers, all three current models are available through the Claude API, Claude in Amazon Bedrock, Claude Platform on AWS, Google Cloud, and Microsoft Foundry. Model IDs, feature support, fallback behavior, data processing, and regional availability can differ by route. Anthropic is the processor for its native API, Claude Platform on AWS, and Claude in Microsoft Foundry; cloud-provider terms govern Amazon Bedrock and Google Cloud processing.

Opus 4.8 and Mythos 5 are boundaries, not peer choices

Opus 4.8 remains relevant when an existing integration must be upgraded. Opus 5 keeps the same standard token price and broad limits, but changes default thinking behavior and has migration details that deserve a dedicated compatibility review. This page owns current-family selection; the separate Opus 4.8 migration guide owns the version-change checklist.

Mythos 5 shares Fable 5's specifications and pricing but is not a general buyer option. Anthropic limits it to approved Project Glasswing customers for defensive cybersecurity workflows, with no self-serve signup. Unless an organization already has that access path, compare Sonnet 5, Opus 5, and Fable 5 instead.

Run a workload evaluation before switching

Build a small evaluation set from work that is valuable, difficult, and representative. Include routine tasks that expose needless premium spend, difficult tasks that expose quality differences, and sensitive tasks that can trigger safeguards or governance constraints.

For each candidate, keep prompts, tools, context, effort, and stopping rules fixed. Record successful completion, review corrections, retries, tool calls, token use, elapsed time, refusal or fallback events, and total cost. Price the Sonnet result at both its promotional and standard rates.

Choose the least expensive route that reliably clears the quality, latency, and governance thresholds. Start with Sonnet 5 for throughput work, Opus 5 for difficult daily work, and Fable 5 only where its measured headroom pays for the higher price and operating constraints. Re-run the evaluation when prompts, tools, effort settings, or cloud routes change.