Model deprecations

As we launch safer and more capable models, we regularly retire older models. Applications relying on Anthropic models may need occasional updates to keep working. Impacted customers will always be notified by email and in our documentation.

This page lists all API deprecations, along with recommended replacements.

Overview

Anthropic uses the following terms to describe the lifecycle of our models:

• Active: The model is fully supported and recommended for use.
• Legacy: The model will no longer receive updates and may be deprecated in the future.
• Deprecated: The model is no longer available for new customers but continues to be available for existing users until retirement. We assign a retirement date at this point.
• Retired: The model is no longer available for use. Requests to retired models will fail.

Migrating to replacements

Once a model is deprecated, please migrate all usage to a suitable replacement before the retirement date. Requests to models past the retirement date will fail.

To help measure the performance of replacement models on your tasks, we recommend thorough testing of your applications with the new models well before the retirement date.

For specific instructions on migrating from Claude 3.7 to Claude 4.5 models, see Migrating to Claude 4.5.

Notifications

Anthropic notifies customers with active deployments for models with upcoming retirements. We provide at least 60 days notice before model retirement for publicly released models.

Auditing model usage

To help identify usage of deprecated models, customers can access an audit of their API usage. Follow these steps:

1. Go to the Usage page in Console
2. Click the "Export" button
3. Review the downloaded CSV to see usage broken down by API key and model

This audit will help you locate any instances where your application is still using deprecated models, allowing you to prioritize updates to newer models before the retirement date.

Best practices

1. Regularly check our documentation for updates on model deprecations.
2. Test your applications with newer models well before the retirement date of your current model.
3. Update your code to use the recommended replacement model as soon as possible.
4. Contact our support team if you need assistance with migration or have any questions.

Deprecation downsides and mitigations

We currently deprecate and retire models to ensure capacity for new model releases. We recognize that this comes with downsides:

• Users who value specific models must migrate to new versions
• Researchers lose access to models for ongoing and comparative studies
• Model retirement introduces safety- and model welfare-related risks

At some point, we hope to make past models publicly available again. In the meantime, we've committed to long-term preservation of model weights and other measures to help mitigate these impacts. For more details, see Commitments on Model Deprecation and Preservation.

Model status

All publicly released models are listed below with their status:

Deprecation history

All deprecations are listed below, with the most recent announcements at the top.

2025-12-19: Claude Haiku 3.5 model

On December 19, 2025, we notified developers using Claude Haiku 3.5 model of its upcoming retirement on the Claude API.

2025-10-28: Claude Sonnet 3.7 model

On October 28, 2025, we notified developers using Claude Sonnet 3.7 model of its upcoming retirement on the Claude API.

2025-08-13: Claude Sonnet 3.5 models

On August 13, 2025, we notified developers using Claude Sonnet 3.5 models of their upcoming retirement.

2025-06-30: Claude Opus 3 model

On June 30, 2025, we notified developers using Claude Opus 3 model of its upcoming retirement.

2025-01-21: Claude 2, Claude 2.1, and Claude Sonnet 3 models

On January 21, 2025, we notified developers using Claude 2, Claude 2.1, and Claude Sonnet 3 models of their upcoming retirements.

2024-09-04: Claude 1 and Instant models

On September 4, 2024, we notified developers using Claude 1 and Instant models of their upcoming retirements.