Gemini DEPRECATED MODERATE

gemini-3.1-flash-tts-preview — Deprecated

Deprecated
Shutdown
Status
active
Replacement

Quick fix — copy & paste

Choose your language. The "before" block matches the deprecated call; the "after" block is the drop-in replacement.

Breaks after deprecation
# Gemini: gemini-3.1-flash-tts-preview (active)
model = "gemini-3.1-flash-tts-preview"
Use this instead
# No direct replacement — see Gemini docs.
# Pick a current model from the provider's available list.

This migration was generated automatically from the model rename. If your code does more than swap a model id, double-check request/response shapes against the official Gemini migration guide.

Error messages

Seeing one of these? You're in the right place.

  • model_not_found: gemini-3.1-flash-tts-preview
  • The model `gemini-3.1-flash-tts-preview` has been deprecated
  • The model `gemini-3.1-flash-tts-preview` does not exist or you do not have access to it

Other Gemini deprecations

What this means for your code

gemini-3.1-flash-tts-preview is an audio model used for either speech input or speech output. Audio models have separate pricing for input audio (per minute) and output audio (per minute or per character). Replacements may change voice list, audio format support, or sample rate.

gemini-3.1-flash-tts-preview has been marked deprecated by Gemini. A specific shutdown date has not been published, but deprecated models typically receive 6-12 months of notice before retirement.

Find every call in your codebase

Before you change anything, locate every place the deprecated model id is referenced. Search source files, environment files, feature flags, and config repos. Use these commands from your project root:

Python projects

grep -rn '"gemini-3.1-flash-tts-preview"' --include="*.py" .

JavaScript / TypeScript projects

grep -rn '"gemini-3.1-flash-tts-preview"' --include="*.{js,ts,tsx,jsx}" .

Anywhere (configs, scripts, infra)

grep -rn "gemini-3.1-flash-tts-preview" .

Migration checklist

Steps in order. Skip any that don't apply, but read the whole list — for audio models, the non-obvious steps are usually the ones that break in production.

  1. 1. Update the model id in audio API calls
  2. 2. Verify the new model supports your audio format (mp3, wav, opus, flac)
  3. 3. Map old voice ids to the new model's voice catalog
  4. 4. Test with your longest and shortest audio inputs
  5. 5. Recompute per-minute audio cost — input and output are usually priced separately

Will this migration cost more?

Switching from gemini-3.1-flash-tts-preview to an alternative model could change your costs significantly. Calculate the exact difference for your prompts.

Open the cost calculator →