Claude 3.5 Sonnet was announced in June 2024 as a major improvement to Anthropic’s mid-tier model line. The original June snapshot is identified as `claude-3-5-sonnet-20240620`, while later 2024 snapshots use different IDs. Combining their capabilities into a single immutable “Claude 3.5” record would mislead developers who need reproducible results.
Historical research cutoff: 25 October 2026. Primary-source historical claims are date-scoped; cloud entitlements, region-specific availability, current pricing and rate limits are not implied.
Release identity at a glance
- Provider
- Anthropic
- Model family
- Claude 3.5 Sonnet
- Public launch
- 2024-06-21
- API ID / checkpoint
- claude-3-5-sonnet-20240620
- API retirement status
- 2025-10-28
The release and why it mattered
Anthropic’s launch announcement emphasized coding, reasoning and visual understanding, with access through its app, API and cloud partners. Its measured benchmark comparisons were vendor-generated and may use tool or prompt configurations that differ from the reader’s needs. The fact that the public article was dated June 21 while the snapshot ends in 20240620 is not a contradiction: announcement date and model stamp are different fields.
Capabilities and genuine use cases
Useful workflows include coding support, long-form editing, document analysis and extraction from complex images. Quality still varies by domain, and claims drawn from a contract need explicit links to the passage that supports them. Tool access also depends on application integration; an LLM does not directly commit code just because a product demo does.
Integration and version identity
Anthropic’s deprecation history lists both the June and October 2024 Sonnet 3.5 snapshots as retired on October 28, 2025. Preserve which one a request used in a legacy usage audit. When moving to a newer Sonnet model, compare structured output behavior, tool-call arguments and refusal cases with equivalent input sets.
Limits and evidence gaps
Consumer subscription availability at release is not evidence for current account limits. Replacements may alter sampling controls, hidden reasoning behavior or unsupported parameter combinations. A migration runbook needs active endpoint and model documentation rather than historical press pricing.
How to choose or migrate
Claude 3.5 Sonnet belongs in the 2024 model archive for its effect on practical developer use. For new work, evaluate a current named model against the application’s acceptance tests and record provider-specific privacy and region policies separately.
Reproducible evaluation checklist
For older Claude services, compare the vendor-operated API lifecycle with the lifecycle published by the actual cloud partner. Exercise long inputs, structured outputs and tool argument validation as separate acceptance tests. Do not assume that matching family names imply identical backend checkpoints.
Collect the exact Messages API version, system instructions and model string from a reproducible request. An active cloud model and a retired direct-API model can coexist under similar product naming.
Sources & Further Reading
- www.anthropic.com — documentation/reference (supplier-provided reference; not independently checked in this pass)
- platform.claude.com — documentation/reference (supplier-provided reference; not independently checked in this pass)
Source documentation establishes vendor-published facts, not independently measured model quality, tenant access, contractual rights or current prices. Use a dated pricing ledger and an account-specific entitlement check for deployment decisions.