Lovable AI model retirement dates: Gemini 3.6 Flash on November 19, 2026, Gemini 3.7 Flash on January 28, 2027, and what your app gets after

Find the 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 it shows the replacement for requests Lovable redirected, so look before the date. You can also ask Lovable in the project chat which models the app's AI features use. In a clone of the repository Lovable syncs to GitHub, search the code for the model ids. Lovable's changelog writes them as provider/model, such as google/gemini-3.6-flash; its deprecated models page gives display names only.

grep -rn --exclude-dir=node_modules -e "gemini-3.6-flash" -e "gemini-3.7-flash" -e "gemini-2.5" -e "gpt-4o-mini-tts" -e "gpt-4o-transcribe" -e "gpt-4o-mini-transcribe" .

Replaced or failing: what happens on the date

At 00:00 UTC on the retirement date Lovable stops sending requests to the model. For a replaced model, Lovable sends the request to the replacement and your app keeps working without a code change, at that model's price and with its answers. Lovable says the replacement is the nearest current model, not always the newest, and suggests you pick the model yourself. For a rejected model, such as the speech models above, requests fail with an error that names the model and its retirement date, and the feature stops until you switch.

Switch to a current model

Ask in the project chat, with Lovable's own prompt below, or name the model you want. Lovable updates the backend code that calls the model. Test the AI features in the preview, then publish: until you publish, only the preview uses the new model.

Replace any deprecated AI models in this app with current ones.

Why a model is deprecated on Lovable before the provider retires it

Lovable can deprecate or retire a model on its own, even when the provider still offers it, for example when an agreement with a provider ends or when it stops supporting an older generation. A deprecated model keeps working in the apps that use it until its retirement date, and Lovable no longer picks it for a new AI feature unless no current model covers that job. Lovable emails the project owners whose apps call the model as soon as it has a retirement date.

Checklist

Before November 19, 2026

1. 01Open More, AI, AI activity and write down every model the app's requests used.
2. 02Compare each with the table above. Mark every model with a date before your next release, and every model whose requests fail.
3. 03Ask Lovable to replace the deprecated models, or name the model you want for each feature.
4. 04Test each AI feature in the preview: its output, its errors and the credits it uses per request.
5. 05Publish, then check AI activity again: requests from the published app should show the new model.

Related

Related guides

• LovableLovable Post-Launch ChecklistChecklist
• LovableLovable Test and Live environments retired on October 5, 2026: Test databases are deleted November 4, and drafts use your live dataGuide
• LovableWhat does Lovable's security scan check, and what can it not see?Guide

Sources

Official docs behind this checklist

• Lovable, Replace deprecated AI models in your app
• Lovable, AI features for your app
• Lovable, Changelog

FAQ

FAQ for builders before launch