Gemini API preview models marked for retirement on October 22 and 23: Check call IDs and replacement models first

Google's Gemini API deprecation table lists October 22 and 23 as scheduled retirement dates. The affected models are preview models. Unlike generally available (GA) models, preview models can have schedules that change quickly, so it is safer to review your call code once this week.

1. October 22: Omni preview and Veo 3.1 preview

According to the table, gemini-omni-flash-preview was released on June 30 as a preview, and its scheduled retirement date is October 22. The replacement model is gemini-omni-1.1-flash. On the same date, the Veo 3.1 preview models (veo-3.1-generate-preview, veo-3.1-fast-generate-preview, and veo-3.1-lite-generate-preview) are also listed, and the table gives gemini-omni-1.1-flash as their replacement model.

Also note that the date has changed once. The August 27 release notes announced that gemini-omni-flash-preview would be deprecated on September 30. The current table lists October 22 as the earliest retirement date. Do not estimate the schedule based only on the old announcement.

2. October 23: Deep Research preview

deep-research-pro-preview-12-2025 is scheduled for retirement on October 23. The release notes instruct users to change the agent value in the interactions.create request to deep-research-preview-04-2026 as the replacement method. If deeper research is needed, deep-research-max-preview-04-2026 is also an option. Find this string first in the agent call configuration file.

3. November 17 item and review order

In the same table, voice preview models such as gemini-3.1-flash-live-preview and gemini-3.1-flash-tts-preview are listed with November 17. If you use real-time voice features, plan to move to the replacement gemini-3.8-live series during October.

The review process has three steps. First, search for the model IDs above in your code, environment variables, and saved task lists. Second, send several actual requests to the replacement models and compare the response formats and token costs. Third, finish the transition before the date, because calls will fail after the retirement date. The table describes the retirement date as the 'earliest possible date' and states that Google will announce the exact date separately. Therefore, it is better to move first rather than delay based on the date.

Sources: Google Gemini API deprecation table ↗ and release notes ↗, checked on October 19, 2026. The quality and cost of the replacement models were not tested in this article.

Related article: OpenAI legacy model API ending on October 23: Check the model IDs being called first ↗

This English edition was written and translated with AI assistance, with sources provided. For errors or additional information, please request a correction. Editorial policy