Google released two new text to speech models on September 23, 2026, and they sit far closer together than the names suggest. Gemini 3.8 Flash TTS and Gemini 3.8 Flash-Lite TTS build voices the same way, take direction the same way, and record for the same length. Moving a script from one to the other changes nothing about how you work.<\/p>\n
That leaves two differences that decide anything at all. Flash TTS speaks 130 languages against Flash-Lite’s 101. And Flash-Lite costs less to run.<\/p>\n
So the useful question is not which model is better. It is whether your script needs one of the 29 languages the flagship covers alone, or the extra polish it brings to harder jobs like layered dialogue and regional accents. If it does not, the cheaper model gives you the same result.<\/p>\n
| <\/th>\n | Gemini 3.8 Flash TTS<\/th>\n | Gemini 3.8 Flash-Lite TTS<\/th>\n<\/tr>\n<\/thead>\n |
|---|---|---|
| Languages<\/th>\n | 130<\/td>\n | 101<\/td>\n<\/tr>\n |
| Overall quality ranking<\/th>\n | 1st<\/td>\n | 2nd<\/td>\n<\/tr>\n |
| Custom voice ranking<\/th>\n | 1st<\/td>\n | Not ranked<\/td>\n<\/tr>\n |
| Overlapping dialogue<\/th>\n | Works best here<\/td>\n | Supported<\/td>\n<\/tr>\n |
| Built for<\/th>\n | Rich performance, accents, long narration<\/td>\n | Speed, volume, everyday voiceover<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Those rows are the whole list. Everything else about the two models matches, which is why the next section is the longer one.<\/p>\n What both models do exactly the same<\/span><\/h2>\nEvery voice option.<\/strong> Both reach the 30 ready-made voices, hundreds more in the extended library, custom voices you create by describing them in words, and voice replication that rebuilds a speaker’s voice from a short sample with consent checks. Google’s own capability list marks all of it available on both.<\/p>\n Two-speaker scenes.<\/strong> Both stage a conversation between two voices from a single script, with natural turn taking, so a podcast-style exchange does not have to be recorded twice and stitched together.<\/p>\n Recording length.<\/strong> Both produce the same amount of audio in one run, so neither gives you more room than the other.<\/p>\n The practical things.<\/strong> File formats and bulk processing options match as well.<\/p>\n Language coverage, by 29.<\/strong> Flash TTS reads 130 languages and Flash-Lite reads 101. This is the largest gap between them and the one most likely to rule a model out before anything else does.<\/p>\n Cost.<\/strong> Flash-Lite generates audio for about a third less than the flagship. Both rates rise at the start of 2027, so the gap between them stays the same either side of that date.<\/p>\n Polish on demanding material.<\/strong> Google points Flash TTS at audiobooks, studio narration, complex multi-speaker scenes, heavy character acting, tricky pronunciation and regional accents. Flash-Lite is aimed at bulk work, voice assistants, read-aloud features and everyday single-voice recordings.<\/p>\n Overlapping dialogue.<\/strong> Both handle listener reactions layered inside a speaker’s line. Google notes that genuinely simultaneous or interrupted speech works best on the flagship, which is a stated preference rather than a hard limit.<\/p>\n Google publishes a language by language breakdown, and the gap in it is worth reading before you pick on price. These 29 run on Flash TTS only:<\/p>\n Banjar in Arabic script, Bashkir, Bemba, Burmese, Crimean Tatar, Dyula, Dzongkha, Finnish, Guarani, Igbo, Kabyle, Latgalian, Lithuanian, Luxembourgish, Minangkabau in Latin script, Occitan, Pangasinan, Sindhi, Slovenian, Somali, Southern Sotho, Swahili, Swati, Swedish, Tajik, Thai, Tigrinya, Tosk Albanian and Uyghur.<\/p>\n Several of those are large markets rather than edge cases. Thai, Swedish, Finnish, Lithuanian and Slovenian all sit on the flagship-only side, as do Swahili and Somali.<\/p>\n There is an awkward consequence worth naming. Flash-Lite is the model built for high-volume dubbing and localization, and it is also the model with the shorter language list. If you are localizing a catalog, check your target languages before you build around the cheaper option, because the saving disappears the moment you need a second model to fill the gaps.<\/p>\n Google describes long narration running for hours with the voice holding steady, and the steadiness is real. The length is worth reading carefully, though.<\/p>\n One recording run produces roughly 11 minutes of speech. An audiobook or a feature-length narration is therefore made of pieces on either model rather than one continuous take.<\/p>\n What the models genuinely give you is consistency across those pieces. The voice, its tone, its volume and even the sense of the room stay the same from one segment to the next, which is the part that used to break. Plan in 11-minute chunks and the promise holds.<\/p>\n Choose Flash-Lite TTS<\/strong> for volume in a widely spoken language. Voice assistants, read-aloud features, bulk narration and everyday single-voice work all sit squarely in what it was built for. You keep custom voices and voice replication, so nothing about your voice choices has to change.<\/p>\n Choose Flash TTS<\/strong> when the material is demanding or the language is on the exclusive list. Layered dialogue, heavy character acting, difficult pronunciation, regional accents, and long narration where the voice has to hold are what the higher cost buys you.<\/p>\n Try both<\/strong> if you are unsure, because it is unusually easy here. The same script and the same voice work on either model, so comparing them costs you a setting rather than an afternoon. Record the same 30 seconds on each, listen to them back to back, and let your own material decide.<\/p>\n |