For a week, Claude Opus 5.5 was the only new model in Anthropic's 5.5 family. Then Sonnet 5.5 showed up at a quarter of the price, closing most of the gap on everyday work. Here's how the two actually differ, and which one fits your job.
Anthropic's Claude 5.5 line now has two members. Opus 5.5 arrived on September 22, 2026, as the flagship. Claude Sonnet 5.5 followed on September 28 as the mid-tier workhorse. They share a family name, a set of safety features, and a price range that runs four times apart at the top.
The short answer is that they're built for different jobs. Opus 5.5 is for open-ended problems that need sustained judgment. Sonnet 5.5 is for well-scoped tasks where speed and cost matter more than depth. The long answer is where it gets useful, so let's take the two apart.
Sonnet 5.5 vs Opus 5.5: The Core Difference
The gap between them is narrower than the price gap suggests. On knowledge work, Anthropic reports just two points of separation. On coding, Sonnet 5.5 comes within a couple of points of Opus 5.5 on CursorBench, a benchmark drawn from real Cursor sessions.
Here's the side-by-side.
Measure | Claude Sonnet 5.5 | Claude Opus 5.5 |
|---|---|---|
Input price | $2 / 1M tokens | $4 / 1M tokens |
Output price | $10 / 1M tokens | $20 / 1M tokens |
Cache reads | $0.20 / 1M tokens | $0.20 / 1M tokens |
Terminal-Bench 4.0 | 70.6% | 66.4% |
GDPval-AA | 1844 | 1846 |
AA Intelligence Index | 56 (max) | 58 (max) |
Best for | Scoped tasks, fast iteration | Complex, open-ended work |
Released | September 28, 2026 | September 22, 2026 |
One line jumps out: on Terminal-Bench 4.0, the cheaper model beats the flagship. That's not a typo. Sonnet 5.5 reports 70.6% against Opus 5.5's 66.4%. Anthropic notes the Opus figure reflects a high-effort run, so the two aren't measured at identical settings. Still, a mid-tier model outscoring the top tier on any agentic coding test is the story of this comparison.
Benchmarks Compared: Where Each Claude 5.5 Model Wins
Read the benchmark table the right way and a pattern appears. Sonnet 5.5 wins on the fast, scoped tests. Opus 5.5 wins on the ones that reward patience.
On Terminal-Bench 4.0, which measures command-line tasks, Sonnet 5.5 leads. On CursorBench 4.0, Opus 5.5 edges ahead at 57.8% to Sonnet 5.5's 55.5%. On GDPval-AA and Artificial Analysis's Intelligence Index, Opus 5.5 stays just in front. The margins are small, mostly two to three points.
The bigger difference is cost per task. Artificial Analysis tracks Opus 5.5 at roughly $0.55 per task at the default setting, the lowest it measures. Sonnet 5.5 halves the token price, and Anthropic says it saves up to 30% per task versus Sonnet 5. So on the same job, the two can land close in total spend even with different rate cards, because Opus 5.5 tends to finish in fewer steps while Sonnet 5.5 runs at a lower rate.
There's one number that cuts against Sonnet 5.5. Artificial Analysis notes it uses the highest output tokens per task it has recorded. On hard problems, it thinks longer. If your work is long and complex, the token savings you were counting on may shrink.
Sonnet 5.5 benchmarks
- Terminal-Bench 4.0: 70.6%, ahead of Opus 5.5's 66.4%
- FrontierCode 1.1: 46.2% at max effort
- CursorBench 4.0: 55.5%
- GDPval-AA: 1844
Opus 5.5 benchmarks
- Terminal-Bench 4.0: 66.4% at high effort
- FrontierCode 1.1: 54.4%
- CursorBench 4.0: 57.8%
- GDPval-AA: 1846
The honest read: Opus 5.5 wins more benchmarks, but not by much. For most searches for the best Claude model, the deciding factor won't be a two-point spread. It'll be what you're asking the model to do.
Opus 5.5 Pricing vs Sonnet 5.5 Pricing
The cost gap is real and it's large. Opus 5.5 costs twice Sonnet 5.5 on both input and output tokens: $4 versus $2 for input, $20 versus $10 for output. Both share the same $0.20 cache-read rate, which is where agentic and coding workloads spend most of their money.
Run a coding assistant across a big repository and the output rate is what you feel. Doubling it from $10 to $20 changes a monthly invoice in a way you notice. That alone pushes a lot of routine work toward Sonnet 5.5.
But price per token isn't price per task. Anthropic says Opus 5.5 uses fewer tokens for the same work, which is where its "40% less than Opus 5" claim comes from. The same logic applies when you compare it to Sonnet 5.5: the cheaper model wins on rate, the flagship can win on steps. For a quick bug fix, Sonnet 5.5 is clearly cheaper. For a long investigation that needs the model to hold a thread for hours, Opus 5.5 may not cost much more, and it's more likely to get there without help.
Speed, Effort Levels, and the Migration Cost
Both models use effort levels that trade cost against quality. Sonnet 5.5 arrives with five: low, medium, high, xhigh, and max. Claude Code and the Claude apps default to Medium; the Claude Platform defaults to High. Opus 5.5 runs adaptive thinking always on, with Medium as its default depth.
For Sonnet 5.5, Anthropic says it generates output more than 30% faster than Sonnet 5, making it the fastest Sonnet to date. Partner reports pile on: Box said results came 2.4 times faster, Zendesk processed tickets 20% faster, and Slack saw about 14% fewer output tokens with no prompt changes. Speed is where the mid-tier model separates from the flagship, and for teams doing fast iteration on smaller tasks, that's the point.
Migration is worth a line. Moving code from Sonnet 5 to Sonnet 5.5 isn't drop-in: adaptive thinking now runs by default, the disabled-thinking setting returns an error, and developers who turned thinking off must switch to a new between_tools setting. Forced tool choice is rejected in favor of automatic tool choice. None of that breaks anything outright, but both Opus 5.5 and Sonnet 5.5 changed API behavior, so anyone upgrading from the older generation should read the migration guide before flipping the switch.
Which Claude Model Should You Pick?
The choice comes down to what you hand the model, not which one scores higher.
Reach for Claude Sonnet 5.5 when the task is scoped and repeatable: fixing a bug you can describe in a sentence, drafting slides, cleaning a spreadsheet, running reviews at volume. You get near-flagship results, faster output, and half the token price. CodeRabbit's team moved simple and moderate code reviews onto it on day one, which says a lot about where it fits.
Reach for Claude Opus 5.5 when the work is open-ended and needs sustained judgment: a system design audit, a long debugging hunt, a document where the model has to weigh tradeoffs across many pages. Anthropic says it stays clearly stronger here, and the independent scores put it just ahead. You pay more per token, but the model is more likely to finish without you stepping in.
If you mostly write code, Sonnet 5.5 is hard to argue against. If your work is genuinely hard and irregular, Opus 5.5 earns its price. Most people will want both, and switching between them based on the job is the point of having a family.
Both are live now. Pick either from the model selector in Claude Code or the Claude apps, or call them by their API IDs, claude-sonnet-5-5 and claude-opus-5-5, on every major cloud. And a third option is on the way: Anthropic says Haiku 5.5, the cheap high-volume tier, lands in the coming weeks. If cost is your main concern, that's worth waiting a little longer for.






