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.

​
Notifications

Anthropic notifies customers with active deployments for models with upcoming retirements. We notify customers of upcoming retirements as follows:

  1. At model launch, we designate a “Guaranteed Available Until” date (at least one year out).
  2. We provide at least 6 months† 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 https://console.anthropic.com/settings/usage
  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.

​
Model Status

All publicly released models are listed below with their status:

API Model NameGuaranteed Available UntilCurrent StateDeprecatedRetired
claude-1.0N/ARetiredSeptember 4, 2024November 6, 2024
claude-1.1N/ARetiredSeptember 4, 2024November 6, 2024
claude-1.2N/ARetiredSeptember 4, 2024November 6, 2024
claude-1.3N/ARetiredSeptember 4, 2024November 6, 2024
claude-instant-1.0N/ARetiredSeptember 4, 2024November 6, 2024
claude-instant-1.1N/ARetiredSeptember 4, 2024November 6, 2024
claude-instant-1.2N/ARetiredSeptember 4, 2024November 6, 2024
claude-2.0N/ALegacyN/AN/A
claude-2.1N/ALegacyN/AN/A
claude-3-haiku-20240307March 2025ActiveN/AN/A
claude-3-sonnet-20240229March 2025ActiveN/AN/A
claude-3-opus-20240229March 2025ActiveN/AN/A
claude-3-5-sonnet-20240620June 2025ActiveN/AN/A

​
Deprecation History

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

​
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.

Retirement DateDeprecated ModelRecommended Replacement
November 6, 2024claude-1.0claude-3-5-haiku-20241022
November 6, 2024claude-1.1claude-3-5-haiku-20241022
November 6, 2024claude-1.2claude-3-5-haiku-20241022
November 6, 2024claude-1.3claude-3-5-haiku-20241022
November 6, 2024claude-instant-1.0claude-3-5-haiku-20241022
November 6, 2024claude-instant-1.1claude-3-5-haiku-20241022
November 6, 2024claude-instant-1.2claude-3-5-haiku-20241022

​
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.

† The Claude 1 family of models have a 60-day notice period due to their limited usage compared to our newer models.

Was this page helpful?

GlossarySystem status