Google launches Gemini 3.5 Transcribe, an LLM-based speech-to-text model

Gemini 3.5 Transcribe is not a bolt-on acoustic decoder wrapped in a new name - it is built on a Gemini LLM rather than a purpose-built acoustic recognizer, and it lives inside the same Gemini API surface developers already use for text and multimodal tasks. That distinction matters because an LLM does not just map sound to characters, it reasons over what a speaker meant. Google's own materials describe the model as stripping filler words, correcting slips of the tongue, and formatting text automatically rather than transcribing every syllable it hears^[2].

The practical effect shows up most clearly in how the model handles self-corrected speech: because it models intent rather than pure acoustics, an abandoned false start can be collapsed into the speaker's corrected meaning instead of preserving both halves verbatim. Launch demos showed this concretely: the model correctly self-corrected a spoken email address mid-utterance, and parsed phone numbers into the right regional format - a 10-digit US number versus an 8-digit Singapore number - based on context rather than a fixed template. That same language-first design is also why Gemini 3.5 Transcribe supports vocabulary biasing for up to 1,000 custom terms - names, jargon, brand words a purely acoustic model would otherwise mangle - by treating recognition as something it can bias linguistically, not just a signal-processing problem^[1]. It is a real departure from Chirp 3's acoustic-modeling lineage, and it is why the headline error rates of 4.0% streaming and 2.6% batch come with an asterisk: they measure recovered meaning as much as raw phoneme accuracy^[1].

That same intent-first design is Gemini 3.5 Transcribe's biggest point of friction. The model ships with two output modes: Verbatim, the default, which preserves fillers, repetitions, and false starts exactly as spoken, and Smart, which removes disfluencies and applies structured formatting - but is explicitly incompatible with word-level timestamps or speaker diarization^[1]. Choosing Smart mode trades raw fidelity for readability, and that trade is not free.

Developers testing the model flagged the risk directly. One Hacker News commenter, Crystalin, warned that Smart mode's cleanup can 'simplify' a sentence into something that changes its meaning, giving the example of a self-corrected line like 'I hesitated to check it, I should have verified' being collapsed down to just 'I should have verified' - dropping the hesitation that was arguably the point^[3]. Another commenter, film42, went further, saying the model still 'suffers from the same hallucination problems as Chirp' and that their team reverted to Whisper for timestamp accuracy, pairing it with Gemini Flash only for correction^[3]. Reddit users evaluating the same tradeoff independently described Smart mode as one that strips signal in cases where hesitation or a self-correction was itself the meaningful part of what was said - the same concern surfacing twice, in separate communities, unprompted by Google's own materials.

Google backs the launch with an unusually direct set of head-to-head numbers. On the FLEURS multilingual benchmark, Gemini 3.5 Transcribe posted 5.50% WER in streaming mode and 5.04% in batch mode^[1], against 7.32% for Google's own outgoing Chirp 3, 8.97% for OpenAI's GPT Live Transcribe, 9.70% for ElevenLabs Scribe v2 Realtime, and 15.77% for Deepgram Nova-3^[3]. On price, Google positions the batch endpoint at roughly $0.005 per minute blended and the live endpoint at about $0.009 per minute blended^[4].

Developers are not taking the comparison at face value. One Hacker News commenter, Void_, ran the math against ElevenLabs Scribe's roughly $0.22-per-hour rate versus Gemini's roughly $0.12-per-hour figure and called it 'a good deal if the accuracy is comparable' - but another commenter, dbbk, flatly disagreed, calling Gemini 3.5 Transcribe 'still more expensive and worse performing than ElevenLabs Scribe'^[3]. The split continued on Reddit, where one user testing a hard Finnish-language dataset said the model beat Whisper and OpenAI's transcription model, while another said a head-to-head comparison against AssemblyAI left them concluding 'assembly wins,' with no further detail on the task given. Even a sympathetic independent voice hedged on the headline number: on X, @JulianGoldieSEO highlighted the 2.6% batch WER figure - roughly 97-98 words correct out of every 100 - then added that accuracy is only half the story, without specifying what the other half is. The pattern across all three threads is consistent: aggregate benchmark averages do not predict how the model performs on any one team's specific language, accent, or audio conditions, and buyers are finding real variance dataset by dataset.

Unlike a typical model-card release, Gemini 3.5 Transcribe launched already wired into consumer products. It now powers Rambler, the dictation feature on Pixel's Gboard, and the Gemini app on macOS, with Chrome web-page dictation, Search Live, Gemini Live, Docs, Keep, and Gmail all listed as coming soon^[5][6]. The model is also live in public preview through Google AI Studio, Google Antigravity, and the enterprise-facing Gemini Enterprise Agent Platform, putting the same transcription engine in front of consumers, developers, and enterprise buyers at once^[7].

That breadth is the point: Gemini 3.5 Transcribe is explicitly built to retire Chirp 3, the acoustic transcription model Google shipped through Vertex AI roughly eighteen months earlier^[8], folding speech recognition into the same Gemini API developers use for everything else rather than maintaining a separate product line. The release name itself became its own small subplot online - community threads on r/singularity leaned into running jokes about how hard Google's version-numbering scheme has become to track, treating the naming cadence as one more sign of how fast the Gemini line is iterating.