# Stop Wrestling with ASR: The Complete Guide to Gemini 3.5 Transcribe 🎙️

> Source: <https://dev.to/googleai/stop-wrestling-with-asr-the-complete-guide-to-gemini-35-transcribe-1m6i>
> Published: 2026-08-28 13:34:29+00:00

You’ve probably used Gemini to analyze hours of video, summarize podcasts, or answer questions from recorded meetings (if you didn't you should, it's extremely useful!). But when all you need is a clean, hyper-accurate, and structured transcript from audio, spinning up a huge reasoning model with complicated prompts often feels like using a sledgehammer to crack a nut.

Enter **Gemini 3.5 Transcribe** (`gemini-3.5-transcribe`

).

It's Google's dedicated speech-to-text model built on Gemini's audio understanding core, optimized specifically for fast, accurate, and cost-effective transcription. Whether you want an exact court-reporter transcript with millisecond timestamps, or a reading-optimized summary that removes all your awkward *"ums"* and *"uhs"*, this model handles it natively with zero prompt gymnastics.

🚀

Hands-on first:If you want to jump straight into running the code yourself, open the interactive[! It's ready to run so you can dirrectly experience how the model work.]Gemini Transcribe Colab notebook

Prefer a visual UI with zero coding? You can also test speech recognition directly in[.]Google AI Studio

Here's what you'll find in this guide:

Before looking at the code, let's get the mental model straight. You might wonder: *"Can't I just upload an MP3 to Gemini 3.7 and say 'Transcribe this'?"*

You can, but here is why `gemini-3.5-transcribe`

is different:

| Feature | General Audio Understanding (e.g. Gemini 3.7) | Dedicated Transcribe (`gemini-3.5-transcribe` ) |
|---|---|---|
Primary Job |
Reasoning, Q&A, sentiment analysis, audio chat | High-throughput, precise speech-to-text |
Speaker Diarization |
Prompt-dependent (can hallucinate turns) | Native segment labeling (`spk:0` , `spk:1` ) |
Timestamps |
Approximate timecodes via text prompt | True word-level millisecond offsets in metadata |
Vocabulary Biasing |
System prompt instructions | Native acoustic biasing dictionary (up to 1,000 terms) |
Cost & Latency |
Full multimodal LLM generation overhead | Optimized lightweight speech pipeline |

Pro tip:If you need toask questionsabout what happened in an audio file ("What was the action item for Alice?"), use a multimodal model like Gemini 3.7. If you need thetranscript itself, subtitles, or cleaned dictation notes, use Gemini Transcribe!

The Gemini 3.5 Transcribe model runs on the modern **Google GenAI SDK** (`google-genai`

v2.0+) using the [Interactions API](https://ai.google.dev/gemini-api/docs/interactions-overview).

First, install the SDK:

```
pip install -U "google-genai>=2.0.0"
```

Make sure you have an API key from [Google AI Studio](https://aistudio.google.com/app/apikey), set it as `GEMINI_API_KEY`

, and let's look at how audio gets passed to the model:

``` python
from google import genai

client = genai.Client()

# 1. Upload your audio file via the Files API
audio_file = client.files.upload(file="meeting_recap.mp3")

# 2. Request transcription using the uploaded file's URI
interaction = client.interactions.create(
    model="gemini-3.5-transcribe",
    input=[{"type": "audio", "uri": audio_file.uri}],
)

print(interaction.output_text)
```

Watch the demo video below to see the baseline transcription in action—handling natural speech and bilingual code-switching with ease:

When dealing with audio and video, you never want to inline raw audio bytes as base64 in your API requests—it blows up the payload size by 33%, easily hits network timeouts, and requires re-uploading the same bytes if you want to rerun a query.

The ** Files API** solves this cleanly:

As you saw in the video above, Gemini Transcribe automatically identifies spoken languages out of the box and seamlessly handles **code-switching** (when someone mixes multiple languages in the same sentence—like switching between French and English mid-sentence, which happens to me all the time!).

However, if you know your audio is exclusively in a specific language or regional dialect, you can pass explicit **BCP-47 language codes** in `transcription_config`

to bias recognition:

```
interaction = client.interactions.create(
    model="gemini-3.5-transcribe",
    input=[{"type": "audio", "uri": spanish_audio.uri}],
    generation_config={
        "transcription_config": {
            # Explicit language hint
            "language_codes": ["es-ES"],
        }
    },
)

print(interaction.output_text)
```

Note:Leaving`language_codes=[]`

(or omitting it) enables full automatic detection across[85+ supported languages and locales]. Check out the[Audio Transcription Documentation]for the complete list of language codes.

Every developer has suffered from an ASR model mangling proper names, confusing specialized libraries with everyday dictionary words (turning *"ScaNN"* into *"scan"*, or *"Qdrant"* into *"quadrant"*), or inventing phonetically similar terms (*"Sitsi"* instead of *"CitC"*, *"Thiago"* instead of *"Tiago"*).

With `custom_vocabulary`

, you can pass a list of up to **1,000 domain-specific terms** that the model will bias towards:

```
interaction = client.interactions.create(
    model="gemini-3.5-transcribe",
    input=[{"type": "audio", "uri": team_briefing.uri}],
    generation_config={
        "transcription_config": {
            "custom_vocabulary": [
                "Guillaume Vernade",
                "ScaNN",
                "Qdrant",
                "Cilium",
                "Weaviate",
                "Milvus",
                "Buganizer",
                "Tiago",
                "CitC",
                "CL",
                "spaCy",
            ],
        }
    },
)

print(interaction.output_text)
```

Watch the side-by-side comparison video below to see how the model behaves with and without custom vocabulary biasing:

| Without Custom Vocabulary (Default ASR) | With `custom_vocabulary` (100% Precision) |
|---|---|
"For our vector benchmarks, sync with Guillaume **Vernat* in Paris to compare Scan against Quadrant while Syllium handles the traffic."* |
"For our vector benchmarks, sync with Guillaume **Vernade* in Paris to compare ScaNN against Qdrant while Cilium handles the traffic."* |
"We also need to evaluate Weaviate against Milvus, assign the buganizer ticket to **Thiago, and test the changes in **Sitsi* before submitting the CL."* |
"We also need to evaluate Weaviate against Milvus, assign the Buganizer ticket to **Tiago, and test the changes in **CitC* before submitting the CL."* |
"Finally, run a quick smoke test with **Spacey* to validate the tokenization pipeline before deploying."* |
"Finally, run a quick smoke test with **spaCy* to validate the tokenization pipeline before deploying."* |

Notice how default speech recognition falls back to phonetic dictionary guesses (**Vernat**, **Scan**, **Quadrant**, **Syllium**, **Thiago**, **Sitsi**, **Spacey**). By contrast, supplying `custom_vocabulary`

guarantees that names of team members, niche tools, internal infrastructure, and open-source libraries are transcribed with 100% precision.

Pro tip:Don't just put acronyms in your custom vocabulary. Add proper names of team members, internal service codenames, GitHub repo handles, product brand names, and niche industry terminology.

This is hands down my favorite capability of Gemini 3.5 Transcribe.

By default, speech-to-text models operate in ** verbatim** mode: they write down

When you're transcribing a speech rehearsal, interview, or voice memo, reading raw verbatim text is painful:

```
--- Verbatim output ---
"Uh, hello. Good evening, everyone. Um, I'd like to start by, well, first of all, thank you all for coming. Today is, um, a very special day, or rather, evening? No, afternoon? Right, evening. We are here to celebrate, uh, sorry, let me just find my notes. Ah, here. We are here to honor, no, not honor, but, um, to mark the launch of our new, sorry, my glasses are a bit foggy, the new marketing campaign. No, wait, product campaign? Product, yes. Um, where was I? Ah, yes. It has been a long journey, a very, uh, challenging, well, not challenging in a bad way, but, you know, difficult? No, rewarding. Rewarding is the word. So, um, yes, cheers to, wait, we don't have glasses yet. Thank you."
```

If you switch `mode={"type": "smart"}`

, the model performs intelligent reading optimization:

Here is how you turn it on:

```
interaction_smart = client.interactions.create(
    model="gemini-3.5-transcribe",
    input=[{"type": "audio", "uri": audio_file.uri}],
    generation_config={
        "transcription_config": {
            "mode": {
                "type": "smart",
            },
        }
    },
)

print(interaction_smart.output_text)
```

Look at the cleaned result on that exact same rehearsal audio:

```
--- Smart transcription output ---
Good evening everyone. First of all, thank you all for coming. Today is a very special evening. We are here to mark the launch of our new product campaign.

It has been a long journey, a very rewarding one. So, cheers to that.
```

Watch the side-by-side comparison video below to see how the raw disfluencies are stripped while listening:

*(If the video doesn't load, you can listen to rehearsing.wav directly.)*

Important caveat:Because Smart transcription uses language modeling to clean up disfluencies and structure the output,it might slightly rewrite, omit, or rephrase parts of what was saidto make it sound natural and concise. If you are doing verbatim court reporting, medical transcription, or subtitle syncing where every exact syllable matters, stick with`verbatim`

mode!Also note that Smart mode is

incompatible with word-level timestamps and speaker diarization(which require`{"type": "verbatim"}`

).

Need to know who spoke during a multi-person meeting or podcast? Enable **diarization** with `diarization_mode="speaker"`

:

```
interaction = client.interactions.create(
    model="gemini-3.5-transcribe",
    input=[{"type": "audio", "uri": meeting_audio.uri}],
    generation_config={
        "transcription_config": {
            "mode": {
                "type": "verbatim",
                "diarization_mode": "speaker",
            },
        }
    },
)
```

To extract each speaker turn cleanly, iterate through the step annotations:

``` python
def print_diarized_transcript(interaction):
  words = []
  for step in getattr(interaction, "steps", []) or []:
    for content in getattr(step, "content", []) or []:
      for annotation in getattr(content, "annotations", []) or []:
        if getattr(annotation, "type", None) == "word_info":
          words.append(annotation)

  current_speaker = None
  current_turn = []

  for w in words:
    speaker = getattr(w, "speaker", "spk:0")
    if speaker != current_speaker:
      if current_turn:
        print(f"[{current_speaker}]: {' '.join(current_turn)}")
      current_speaker = speaker
      current_turn = [w.text]
    else:
      current_turn.append(w.text)

  if current_turn:
    print(f"[{current_speaker}]: {' '.join(current_turn)}")

print_diarized_transcript(interaction)
```

Output:

```
[spk:0]: One chocolatine, please.
[spk:1]: Tiago, arrête. It is a pain au chocolat.
[spk:0]: Wait, a guy from the south west told me it's chocolatine.
[spk:1]: Do not listen to them. 90% of France and the entire universe calls it pain au chocolat. Chocolatine is a myth.
[spk:0]: Meu Deus, you French are intense. In Brazil, people fight the exact same way over bolacha versus biscoito.
[spk:1]: Well, here pain au chocolat is the only real word.
[spk:0]: Fine. Two pain au chocolat, please. As long as it has chocolate, tá valendo.
```

Watch the demo video below where two colleagues debate *pain au chocolat* vs. *chocolatine*. **Notice how the waveform line dynamically changes color (Cyan for Tiago, Orange for his colleague) as each speaker takes turns:**

*(Direct audio link: listen to pain_au_chocolat.wav)*

When you need exact synchronization—for example, to jump to specific points in a video, build interactive transcripts, or align text with waveforms—you can request word-level millisecond start and end offsets.

Configure `timestamp_granularities=["word"]`

(and optionally combine it with `diarization_mode="speaker"`

):

```
interaction = client.interactions.create(
    model="gemini-3.5-transcribe",
    input=[{"type": "audio", "uri": audio_file.uri}],
    generation_config={
        "transcription_config": {
            "mode": {
                "type": "verbatim",
                "timestamp_granularities": ["word"],
                "diarization_mode": "speaker",
            },
        }
    },
)
```

Each recognized word comes back with its exact time offsets (and speaker turn) attached in the content annotations:

```
words = []
for step in getattr(interaction, "steps", []) or []:
  for content in getattr(step, "content", []) or []:
    for annotation in getattr(content, "annotations", []) or []:
      if getattr(annotation, "type", None) == "word_info":
        words.append(annotation)

for w in words[:6]:
  spk = getattr(w, "speaker", "spk:0")
  print(f"[{w.start_offset:>7} -> {w.end_offset:>7}] ({spk}) {w.text}")
```

Output:

``` php
[ 0.000s ->  0.400s] (spk:0) One
[ 0.400s ->  1.200s] (spk:0) chocolatine,
[ 1.200s ->  1.800s] (spk:0) please.
[ 3.200s ->  3.700s] (spk:1) Tiago,
[ 3.700s ->  4.200s] (spk:1) arrête.
[ 4.200s ->  4.500s] (spk:1) It
```

Having millisecond-level offsets for every individual word unlocks huge capabilities:

`.srt`

/ `.ass`

)💡

Behind the scenes:That's actually what I did to make the demo videos above! The word timestamps provided the exact millisecond timing to align the subtitle cards, highlight the custom terms ("oatmilk"), and trigger the color switch of the waveform line from Cyan to Orange when the speaker changed.If you want the complete Python function to convert these word annotations into standard

`.srt`

subtitle files, you can find it directly in the[interactive Cookbook Colab notebook].

Here is a quick cheat sheet to pick the right settings for your use case:

| Use Case | Mode | Diarization | Timestamps | Custom Vocab |
|---|---|---|---|---|
Meeting Notes / Voice Memos |
`smart` |
No | No | Optional |
Video Subtitles / Closed Captions |
`verbatim` |
Optional | `["word"]` |
Highly recommended |
Podcast / Multi-speaker Interview |
`verbatim` |
`speaker` |
`["word"]` |
Highly recommended |
Legal / Compliance Audio Logs |
`verbatim` |
`speaker` |
`["word"]` |
Optional |
Search Indexing & Embeddings |
`smart` |
No | No | Optional |

Everything we covered above is for **pre-recorded audio files** (unary mode via the Files API).

Gemini also supports **real-time live streaming transcription** over WebSockets using `gemini-3.5-transcribe-live`

and the Live API. It lets you stream raw 16-bit PCM chunks (100ms each) directly from a microphone and receive instantaneous interim partial hypotheses (`interim_input_transcription`

) and finalized text as speech occurs.

However, streaming real-time WebSockets with asynchronous Python workers (`asyncio`

), handling audio chunking, and managing ephemeral valet tokens for secure client apps is quite a bit more complex and deserves its own dedicated tutorial.

If you want to dive straight into live streaming code right now:

Gemini 3.5 Transcribe gives you the best of both worlds: strict, millisecond-accurate verbatim data when you need timestamps and diarization, and an intelligent, disfluency-stripping smart mode when you want clean text for human eyes.

Have you tried using `smart`

mode on your own voice recordings or meetings? Drop your thoughts and edge cases in the comments below! 🚀