Sonnet 5 matches Opus 4.8 performance at lower list prices, but new tokenizer inflates actual costs by ~30% for English text; adaptive thinking enabled by default changes inference behavior.
July 7, 2026
Summary
If you're running Sonnet 4.6 in production, switching to Sonnet 5 requires tokenizer recalculation and explicit thinking configuration—apparent price parity masks real cost increase. The 1M context window and 128k output tokens unchanged from prior versions.
Why it matters
If you're running Sonnet 4.6 in production, switching to Sonnet 5 requires tokenizer recalculation and explicit thinking configuration—apparent price parity masks real cost increase. The 1M context window and 128k output tokens unchanged from prior versions.
Implementation verdict
Sonnet 5 replaces Sonnet 4.6 as the mid-tier option, but the tokenizer change means token budgets and cost projections break. Requires testing with your actual workloads using the new token counter before migration. Skip unless you need the performance bump—otherwise stay on 4.6 through August discount period to reset baselines.
Sources
Dev Signal
Get briefs like this in your inbox — free, every weekday.
100+ sources compressed into one 4-minute read. Ranked, cited, implementation-ready.