Voice replication blocked in IL, TX, EEA, UK, CH, IN: plan voiceovers

Digital Applied reports Gemini voice replication is unavailable in Illinois, Texas, the EEA, UK, Switzerland and India. A market plan using ready-made voices.

4 min readSume
All posts

Digital Applied reports that Gemini's voice replication is unavailable in Illinois, Texas, the European Economic Area, the United Kingdom, Switzerland and India. If you run ads in those markets, plan the voiceover so it does not depend on a cloned voice. Use a ready-made voice instead, record a human voice, or both, and keep the records. This is not legal advice.

The Gemini API changelog confirms Gemini TTS went GA on 2026-09-22 with voice replication among its features; the list of blocked places comes from the tracker, so check Google's own terms.

What changes market by market?

Make a table with one row per market and one column for the voice you will use. Cloning is the cell that needs a check.

Planning grid. Blocked list per Digital Applied, read 2026-10-02; the plan column is ours.
MarketGemini voice replication (reported)Plan
Illinois, TexasUnavailableReady-made or human voice
EEA, UK, SwitzerlandUnavailableReady-made or human voice
IndiaUnavailableReady-made or human voice
ElsewhereNot listed as blockedCheck terms; still get consent for any real person

What does Sume offer here?

Sume's TTS 1.0 picks a voice by avatar_id, avatar_handle or voice.id, and the TTS Router lists Sonic models. There is no voice cloning in the Sume API; cloning exists only in the app. That makes the API route a ready-made-voice route for every market.

What should I record?

Keep the voice id, the script, the market, the date and the job id for each file. If a platform or regulator asks how a voice was made, you can answer from the record.

Sources

Related posts

More in Use cases

All Use cases posts

Written by Sume