Claude Sonnet 5 launched June 30 with introductory pricing: $2 per million input tokens and $10 per million output tokens through August 31, 2026. After that, it moves to standard pricing: $3 per million input tokens and $15 per million output tokens.

If you moved from Sonnet 4.6 to Sonnet 5 expecting “cost neutrality,” you got it — barely, and temporarily. After August 31, the math changes in two places at once, and most teams are only watching one of them.


The two-variable problem

Variable 1: The rate increase

The rate change is clean and well-publicized: +50% on both input and output tokens.

PeriodInput (per 1M)Output (per 1M)
Sonnet 5 intro (now–Aug 31)$2.00$10.00
Sonnet 5 standard (Sept 1+)$3.00$15.00

Variable 2: The tokenizer inflation

Claude Sonnet 5 uses a new tokenizer. Anthropic’s own Sonnet 5 migration notes state the same input text produces “approximately 30% more tokens” on Sonnet 5 than on Sonnet 4.6, and the launch announcement puts the range at “roughly 1.0–1.35×, depending on content type.” Anthropic does not publish a per-language or per-format breakdown.

Independent testing gives a more granular (but less official) picture. Developer Simon Willison measured token counts on single documents translated into each language/format:

Content typeMeasured multiplier vs. Sonnet 4.6 (Willison, single-document test)
English prose1.42×
Spanish1.33×
Python code1.27×
Simplified Chinese1.01× (effectively unchanged)

These are one independent tester’s single-document measurements, not an Anthropic-published average — French and JavaScript were not separately tested, so they’re omitted here rather than assumed to match Spanish and Python. Willison’s English figure (1.42×) runs slightly above Anthropic’s own stated ceiling of 1.35×, a reminder that your own workload could land anywhere in — or outside — that band. Measure your own before budgeting.

This tokenizer effect is already in your current Sonnet 5 bills. Depending on your content mix, you may already be paying roughly 27–42% more tokens than you were on 4.6 for non-Chinese content (per Willison’s tests); Anthropic’s own published average is closer to 30%. The September rate increase stacks on top of that.


What your September bill actually looks like

Let’s work through the math for an English-heavy workload. (This example uses a rounded 1.40× tokenizer multiplier — Willison’s tests measured 1.42× for English prose; see the table above. Your actual multiplier may differ.)

Baseline: Sonnet 4.6 at standard pricing ($3/$15)

Assume 100M input tokens and 10M output tokens per month:

  • Input: $300
  • Output: $150
  • Total: $450/month

Today: Sonnet 5 at intro pricing ($2/$10, with 1.40× tokenizer)

The same workload produces 140M input and 14M output tokens:

  • Input: $280
  • Output: $140
  • Total: $420/month — slightly cheaper. That’s the “cost neutral” framing Anthropic used at launch: “The introductory pricing is set so that the transition to Sonnet 5 is roughly cost-neutral.”

September 1+: Sonnet 5 at standard pricing ($3/$15, with 1.40× tokenizer)

Same workload, same 140M/14M token counts, new rate:

  • Input: $420
  • Output: $210
  • Total: $630/month

The rate card says +50% vs. intro. Your bill says +50% ($420 → $630). But compare it to what you were paying on Sonnet 4.6: $450. You are now paying $180 more per month — a 40% increase over the Sonnet 4.6 baseline you started from.

If your token counts are pure English prose at 1.40×: effective cost is $3 × 1.40 = $4.20 per million effective tokens on input vs. the $3.00 you paid on Sonnet 4.6. That is a 40% effective price increase for the same text, even though the rate card has not changed from Sonnet 4.6.


Why teams are underestimating this

The introductory pricing masked the tokenizer inflation completely. During the intro period, the lower rates compensated for the higher token counts and landed you at approximately the same effective cost as 4.6.

That compensation disappears September 1. The rate goes up 50%. The token count stays inflated by roughly 27–42% (or ~30% on Anthropic’s own average). There is no new discount to offset either.

Most teams tracked the August 31 date but set a mental model of “50% increase on what I’m paying now.” That is accurate. What they missed is that “what I’m paying now” is already running roughly 27–42% more tokens than 4.6 did (per the measurements above), or ~30% on Anthropic’s own published average. If you migrated to Sonnet 5 and compared your Sonnet 4.6 bills to your current Sonnet 5 bills, and found they were similar — that gap will re-open in September.


What to do in the next 52 days

Step 1: Measure your actual token inflation (do this first)

The 1.27–1.42× figures above are one independent tester’s single-document measurements, not Anthropic-published averages (Anthropic’s own average is ~30%, range 1.0–1.35×). Your workload may be different from all of these. Get the real number.

Run your ten most common prompt templates through both models with usage logging enabled. Compare input_tokens and output_tokens in the response:

import anthropic

client = anthropic.Anthropic()

prompt = "Your actual production prompt here"

s46 = client.messages.create(
    model="claude-sonnet-4-6",
    max_tokens=1024,
    messages=[{"role": "user", "content": prompt}]
)

s5 = client.messages.create(
    model="claude-sonnet-5",
    max_tokens=1024,
    messages=[{"role": "user", "content": prompt}]
)

print(f"Input inflation: {s5.usage.input_tokens / s46.usage.input_tokens:.2f}x")
print(f"Output inflation: {s5.usage.output_tokens / s46.usage.output_tokens:.2f}x")

Do not use the published averages for budget planning. Measure your actual workload.

Step 2: Project your September bill

Take your last 30 days of Sonnet 5 billing data and apply the rate multiplier to the same token counts:

September projected input cost = (current input tokens) × ($3 / $2)
September projected output cost = (current output tokens) × ($15 / $10)

That projection uses your actual tokenizer-inflated token counts, so it is the real number. Compare it against your current budget.

Step 3: Identify your high-token-count workflows

Not all traffic costs the same. Your longest prompts — retrieval-augmented generation, document processing, multi-turn agent loops — bear the most absolute cost. List your top five traffic sources by token volume. Those are where optimization effort returns the most money.

For long-context workflows, the tokenizer change also affects context window utilization. A 200K-token document on Sonnet 4.6 could produce up to roughly 270K tokens on Sonnet 5 — near the top of Anthropic’s stated 1.0–1.35× range — changing whether it fits in a single pass.

Step 4: Set budget alerts now, not September 1

Set an alert at 80% of your projected September budget starting September 1. If you wait until you see the first bill, you have already committed the spend.

AWS Bedrock users: CloudWatch alarms on the InputTokenCount and OutputTokenCount metrics, broken out by model ID.
Direct API users on Claude Enterprise: Anthropic’s admin console supports spend-threshold alerts at 75% and 90% of your org-level spend limit — set your limit to your projected September number. (This is an Enterprise-plan feature; non-Enterprise accounts should track spend manually via the usage and cost API.)

Step 5: Decide whether to optimize, route, or re-evaluate

Three responses to the cost increase:

Optimize in place: Prompt compression, output length caps, caching repeated context. Prompt caching cuts cached input cost to 10% of the standard input rate, so for most teams this meaningfully reduces the tokenizer inflation’s impact on English-heavy workloads — exact savings depend on your specific prompts and cache hit rate, so measure rather than assume a fixed percentage. See our Sonnet 5 effort levels and token overhead guide for specific controls.

Route by task: Use Sonnet 5 for complex agentic work and route simpler classification, extraction, or summarization tasks to Haiku 4.5 ($1/$5 per million). A 60/40 Sonnet/Haiku split can cut the overall bill without necessarily costing quality on simple tasks.

Re-evaluate alternatives: Grok 4.5 launched at $2/$6 per million and is, per xAI’s own docs, “built for coding, agentic tasks, and knowledge work.” Meta’s Muse Spark 1.1 API is priced at $1.25/$4.25 per million tokens (Meta’s blog post doesn’t list pricing directly; the figure is confirmed by Tech Times and gHacks reporting on Meta’s public preview announcement). Both are substantially cheaper at list price than Sonnet 5 standard pricing. If your workload is primarily coding or agentic tool use, benchmark them before September. Switching during the intro period gives you time to validate quality before the cliff.


The quick version

ActionTimeline
Measure your real token inflation on actual promptsThis week
Project September bill against current token volumesThis week
Identify top 5 workflows by token spendNext 2 weeks
Set budget alerts in your billing dashboardBefore August 1
Test routing alternatives if projections exceed budgetJuly–August
Finalize model selection before August 31August 24

August 31, 2026 is a Monday. Billing cycles vary. Leave a week of buffer before the date itself.


Summary

The rate card change is 50%. But because Sonnet 5’s tokenizer is already inflating your token counts — roughly 30% on Anthropic’s own published average, and as much as 27–42% depending on content type per independent testing — above what Sonnet 4.6 produced for the same workload, your effective cost increase versus what you were paying on 4.6 at standard rates is in that same range for non-Chinese content — not zero, despite the “cost neutral” framing at launch.

The introductory pricing made both facts invisible at the same time. From September 1, both are visible at once.

Measure your inflation now. Project your bill now. Plan now — 52 days is enough time to route, optimize, or switch; it is not enough time to absorb a surprise.


ChatForest covers AI infrastructure decisions for builders. This analysis is based on Anthropic’s Claude Sonnet 5 launch announcement, the platform pricing page, and the What’s new in Sonnet 5 documentation. We do not receive compensation from Anthropic or any model provider. See also: Claude Sonnet 5 Migration Guide, Sonnet 5 Effort Levels and Token Overhead.