The official Gemini API changelog released Voice remixing on November 4. Starting from a prebuilt voice, an Extended Voice Library voice or a Voice Design persona, developers describe changes such as accent, pitch, pacing or age in natural language, and POST /v1beta/voices returns a new standalone voice_ ID usable with Gemini 3.8 Flash TTS and Flash-Lite TTS. It is also available interactively in Google AI Studio.

Key Takeaways

  • ✓New Voice remixing feature: apply relative natural-language edits to an existing voice to create a new standalone voice
  • ✓Uses POST /v1beta/voices (type=prompted, store=true, plus a new prompted.base_voice field) and returns a voice_ ID with a 24kHz WAV preview
  • ✓Base voices can be any of 30 prebuilt voices, an Extended Voice Library voice, or a stored custom voice_ voice in the project
  • ✓The resulting voice_ ID works with gemini-3.8-flash-tts and gemini-3.8-flash-lite-tts and can itself be remixed again
  • ✓The original voice is never modified, and deleting it does not affect voices remixed from it
🧭

Turn your technical choice into a development budget

Compare 40 dev plans & simulate token costs vs $20/mo subscriptions

🔬

In-Depth Technical Analysis

Background and the Industry Pain Point

Teams building voice products often get stuck at "almost right": a prebuilt voice is close, but the accent, pacing or perceived age is off, while designing a new voice from scratch with Voice Design makes it hard to stay consistent with an existing brand voice. Gemini 3.8 TTS already supported prebuilt voices and Voice Design, but had no way to adjust an existing voice.

Architecture Highlights and Mechanism

According to the official Gemini API changelog (November 4) and the Voice remixing guide, the feature reuses the Voice Design endpoint POST /v1beta/voices (type=prompted, store=true) and adds a prompted.base_voice field for the source voice, with prompted.input describing the changes in natural language. The model applies these relative instructions to the base voice's acoustic profile, stores a new voice_ resource in the project and returns a 24kHz WAV preview, without modifying the original. The new ID can be passed as base_voice again to refine it step by step. Thor (@thorwebdev), who works on developer experience at Google DeepMind, also introduced the feature on X.

Benchmarks and Measured Results

This is an API feature update. Google published no benchmarks, latency or audio quality evaluations, and did not describe separate pricing; check the Gemini API pricing page for billing.

Getting Started for Developers

Try it interactively on the Generate speech page in Google AI Studio, or call client.voices.create() in the google-genai SDK with a base_voice such as "Puck" and an edit instruction. Use the returned voice_ ID in speech_config with gemini-3.8-flash-tts or gemini-3.8-flash-lite-tts. It suits audiobook narration, brand voices and multi-character dubbing where you need several variants of one voice.

Action HubReady to adopt this in production?

Benchmark side-by-side against alternatives, or calculate monthly token cost vs subscription break-even.

Up NextGemini API Deprecates Gemini 2.5 Pro and 2.5 Flash: From December 1, Requests Auto-Route to 3.8 Flash and 3.5 Flash-Lite at the New Models' Rates
Read Now→