Gemini TTS and Live preview models can shut down from November 17. Here are the 5 IDs.
Don't wait: your Gemini TTS preview can fail November 17. Google's deprecation page lists November 17, 2026 as the earliest shutdown date for five audio preview models: Model ID Move to gemini-3.1-flash-tts-preview gemini-3.8-flash-tts or gemini-3.8-flash-lite-tts gemini-2.5-flash-preview-tts same gemini-2.5-pro-preview-tts same gemini-3.1-flash-live-preview gemini-3.8-live…
Google has announced that five Gemini TTS preview models will be shut down starting November 17, 2026. These models include gemini-3.1-flash-tts-preview, gemini-3.8-flash-tts or gemini-3.8-flash-lite-tts, gemini-2.5-flash-preview-tts, gemini-2.5-pro-preview-tts, and gemini-3.1-flash-live-preview, gemini-3.8-live, and gemini-2.5-flash-native-audio-preview-12-2025.
The earliest shutdown date of November 17 provides a clear deadline for developers to transition their code. However, this fixed date means that the calls can stop at any time after that, without further notice. Preview models tend to have shorter notice periods than stable ones due to their development process.
Voice features are often added rapidly and may not be the core of an application. As a result, migration from preview models to stable ones can be overlooked until issues arise. Developers can use a command like "grep -rnE preview-tts|native-audio-preview|flash-live-preview" to search for references to these models in their code. They should also check environment variables and data storage for any model names.
For TTS calls, developers should move to gemini-3.8-flash-tts (or gemini-3.8-flash-lite-tts for a more cost-effective option), and for Live calls, they should switch to gemini-3.8-live. It's essential to test the new model's output, as voices, pacing, and pronunciation may differ from the preview model. A simple audio check may not catch a voice that users won't recognize.
Run a real Live session from end to end to ensure that settings carry over unchanged. Keep the next migration off error logs and consider using Versyka to track shutdown dates across different providers and centralize model IDs for a streamlined migration process.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.