Skip to main content
A deprecated model still works in the apps that use it. The label means the model is on its way out: Lovable stops serving it on its retirement date, so a deprecation is a deadline to plan around, not an outage. This page lists every deprecated model with its retirement date and what happens to your app’s requests after that date. For the models you can build on today, see AI features for your app.

​
Why a model is deprecated

Model providers retire their models over time. Lovable can also deprecate or retire a model on its own, even when its provider still offers it. That happens when an agreement with a provider ends, or when Lovable stops supporting an older generation. When a provider or Lovable plans to stop serving a model, the model gets a Deprecated badge in the Available models list in Connectors → AI. Lovable lists it on this page instead of with the current models for its job. A deprecated model keeps working in the apps that already use it until its retirement date. Lovable does not choose a deprecated model for a new AI feature, unless no current model covers that job. A deprecated model without a retirement date keeps working until Lovable or the provider sets one.

​
How Lovable informs you of a deprecation

Lovable warns you in two places:
  • In the project chat. If you ask for a deprecated model without saying you know it is deprecated, Lovable tells you, names the retirement date when one is set, and offers a current model for the same job. If you ask again after that, Lovable uses the model you asked for.
  • By email. Lovable emails the owner of every project whose app calls the model, as soon as that model has a retirement date. The provider usually sets the date, so the warning can be short.
Lovable does not change the model in your app’s code on its own, and it keeps your app’s current models when you ask for unrelated changes. Your app calls the deprecated model until you ask Lovable to switch it.

​
What happens on the retirement date

On the retirement date, at 00:00 UTC, Lovable stops sending requests to the model. What happens to your app’s requests depends on the model:
  • Replaced: Lovable sends requests for the retired model to its replacement model. Your app keeps working without a code change. The replacement can cost a different amount per request and can respond differently, so switch your app to a current model before the date.
  • Rejected: Requests for the retired model fail with an error that names the model and its retirement date. Switch your app to a current model before the date to keep the feature working.
A replacement keeps your app running, but it is not a model you chose. Lovable routes retired requests to the nearest current model, which is not always the newest one for the job. Pick the model yourself from Choosing a model, and prefer a newer generation over an older one.

​
Models and retirement dates

Each model below is deprecated. A date in the past means the model is already retired, and the last column describes what your app’s requests get today. Go by the dates below rather than the provider’s own schedule. Lovable can retire a model before its provider does, so the provider’s date can be later.

​
Deprecated OpenAI models

​
Deprecated Google models

​
Switch to a current model

To switch a deprecated model:
1

Check which models your app uses

Open More → AI in the project. The AI activity list shows the model each AI request used. After a retirement date, this list shows the replacement model for requests that Lovable redirected, so check it before that date. You can also ask Lovable in the project chat which models the app’s AI features use.
2

Ask Lovable to switch

Let Lovable pick a current model for the same job, or name the model yourself.
Lovable updates the backend code that calls the model. A different model can change what your AI features cost per request.
3

Publish the change

Publish your changes so your published app uses the new model. Until you publish, only the preview uses it.