
What happened
Google's Gemini 3.5 Transcribe, launched in August 2026, is a transcription-only model that separates speakers (up to 8), adds per-word timestamps, and auto-normalizes units like "三件" to "3件".
Why it matters
Speaker labels mean meeting notes can show who said what, not just an anonymous block of text, and the model runs in both a recorded-file version and a real-time version.
What to watch
Speaker separation beyond 3 people is labeled an experimental feature, so accuracy on larger meetings may vary. Timestamps also raise cost, so watch whether the added tokens and time are worth it for your use case.
WHO IT HITSTeams building meeting-minutes or subtitling tools can get speaker labels and word timings from a dedicated transcription model instead of prompting a general-purpose model. Companies handling sensitive audio may prefer the Vertex AI path, which supports custom vocabulary and IAM-based access control.
Summaries like this, in your inbox every morning.
Previously, feeding an audio file to a general-purpose Gemini model could produce a transcript, but it could not reliably tell you which participant said which line — a serious problem if the point of the document is accountability. Gemini 3.5 Transcribe is built specifically to close that gap, using voice differences to attach speaker labels and returning a start and end time for every word. It also lets you pre-register up to 1,000 technical terms or proper nouns, which should reduce misrecognitions of product names and people's names, and it automatically formats numbers and units, turning spoken "三件" into "3件".
The rollout differed by platform. On the Gemini API it reached general availability on 2026-08-26, while on Vertex AI it arrived as a preview in August 2026 and reached GA in October 2026. Two output modes are offered: VERBATIM, which transcribes speech exactly as spoken and is the only mode that supports speaker separation and word timestamps, and SMART, which removes hesitations and false starts for a cleaner read but cannot be combined with those features.
For companies weighing adoption, the practical question is workflow rather than raw capability. The most common need — knowing who spoke while also cleaning up the text — cannot be met by a single API call today, so the realistic setup is a two-step pipeline: label the speakers first, then polish the text with a separate text model. Whether that added step is worth it depends on how much accuracy matters in a given meeting, especially since speaker separation for three or more people is still labeled experimental.
Pick your industry and the AI tools you use, and get news related to your work every day.
Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →
Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.
ElevenLabs completed a $300 million employee tender at a $22 billion valuation, and co-founder Mati Staniszews…

On October 15, OpenAI announced the Rosalind Academic Plan, giving approved US university labs free access to…

A Qiita article compared automated red-teaming methods for LLM apps — GCG, PAIR, and TAP — using mock implemen…

Liquid AI released d1-ultra on October 15, 2026, an upgraded open-weights decision model that averaged 76.7 ac…

Circlia started a proof-of-concept for TASTE SIGNAL: visitors to Holland Village Cafe FUKUOKA taste cookies an…

In a webinar hosted by French Mathematical Society president Isabelle Gallagher, Fields Medal winner Hugo Dumi…
