---
title: "Google Meet Translation, Both Ways | VoxisLive"
description: "Translate a Google Meet call in both directions on Windows. No bot joins, no Workspace admin approval, nothing installed inside the meeting."
url: https://voxislive.com/use-cases/google-meet-translation
language: "en"
source_html: https://voxislive.com/use-cases/google-meet-translation
site: "Voxis — real-time voice translation"
og_image: https://voxislive.com/assets/og.png
generated_by: voxislive-markdown-pipeline
---

[Home](https://voxislive.com/) · / · [Use cases](https://voxislive.com/use-cases/) · / · Google Meet translation

GOOGLE MEET TRANSLATION

# Translate a Google Meet call in both directions, without anything joining it

Google Meet runs in a browser tab, but the translation does not happen inside that tab. VoxisLive captures audio at the operating-system layer and speaks it back to you, and sends your translated voice into the call through a virtual microphone.

## Meet is a browser tab, and that changes nothing

Most conferencing tools ask you to install a client. Google Meet does not — it runs in a Chrome, Edge or Firefox tab, next to twenty others. For anything that tries to work *inside* the meeting, that is a complication: a tab is a harder place to attach to than a desktop app, and Google decides what may attach at all.

VoxisLive does not work inside the meeting. Capture happens at the **operating-system audio layer**, which is the same place for every program on the machine. The source app does not matter — a tab, a native client, a media player, a game. To VoxisLive, Meet is simply one more thing your computer is currently playing.

The practical consequence: there is nothing Meet-specific to set up on our side. What *is* Meet-specific is where you point its microphone and speaker settings, and that is covered below.

## Two directions, two independent sessions

Meeting mode runs two translation sessions at the same time, and they do not depend on each other:

- **Incoming** — what the other participants say is captured from your system audio and spoken back to you in the language you chose to hear.
- **Outgoing** — what you say into your real microphone is translated into the language the other side should hear, and delivered into the call as speech.

Because the two sessions are independent, one can be busy while the other sits idle — which is what a normal conversation looks like. Each direction trails the speaker by a few seconds. That gap is the span a simultaneous interpreter needs as well; it is a property of interpreting, not a setting you can turn down.

**What this is not:** it is not a transcript feature bolted onto the call, and it is not something the other participants can see, join, or configure. There is no shared interpreter channel — the incoming translation exists only in your headphones.

## The virtual microphone is what makes the outgoing direction possible

Your translated voice has to reach Meet somehow, and Meet only accepts audio from something it recognises as a microphone. That something is a **virtual microphone**: a small free driver — VB-CABLE is the usual one — that appears in Windows as an ordinary recording device. VoxisLive speaks your translated voice into it, and Meet picks it up exactly as if you were talking into a headset.

**Without a virtual microphone, Meeting mode still runs — as listen-only.** You hear the other participants in your language; they hear whatever your real microphone is picking up, untranslated. That is a legitimate way to use it, and for a call where you mostly listen it may be all you need. But the outgoing direction described on this page requires the driver.

One consequence worth stating plainly: if the host turns on Meet's own recording, your translated voice is on that recording the same way any microphone audio would be. Routing speech through a virtual device does not put it outside the meeting.

## Where the device settings live in Google Meet

Meet keeps both device pickers in one place, and you can reach them before or during the call.

1. In the call, open the three-dot menu in the bottom bar and choose **Settings** (on the green-room screen before joining, it is the gear icon in the top right).
2. Open the **Audio** tab. It has two rows: Microphone and Speakers.
3. Set **Microphone** to the virtual cable's recording device. With VB-CABLE installed, that is the entry named *CABLE Output* — Windows exposes it as an input, which is why it appears in this list at all.
4. Leave **Speakers** on your headphones. Do not point it at the virtual cable; the incoming direction goes to your ears, not back into the loop.
5. Watch Meet's own level meter under the microphone row while you speak. It should stay flat while you talk and move a few seconds later, when the translated voice arrives — that delay is the confirmation that Meet is listening to the translation and not to you.

Two browser-specific things to expect: the virtual device only appears in Meet's list after the driver is installed *and* the browser has been restarted, and Chrome asks for microphone permission per site — if you denied it earlier, the picker will look empty regardless of what is installed.

Use headphones. Meet is being translated out of your speakers, and open speakers put that translated audio back into the room where your real microphone is sitting.

## No bot, no Workspace admin approval, nothing installed in the meeting

**Nothing joins the call.** There is no participant to admit, no second tile in the grid, no attendee list entry for someone to ask about. The capture is happening at the operating-system audio layer of your own machine, and the meeting has no way to observe it because the meeting is not involved.

That removes a category of blockers. There is no Meet add-on to install, so no Google Workspace admin has to approve a third-party app for the domain. There is no in-meeting extension asking for access. Host controls over external participants do not apply, because nothing external is asking to enter. If you can join the meeting yourself, you can translate it.

**What this is not:** it is not a compliance statement. We hold no certifications, and an architecture decision does not substitute for one. What we can describe is the mechanism — where the audio is read, and what is and is not connected to your call — and let your own policy people judge it on that.

## The browser extension, and when the desktop app is the right answer

VoxisLive also has a browser extension, and Meet is a browser product, so the obvious question is which of the two you want. The extension captures the audio of the tab you are on and speaks it back to you. That is its whole description, and for listening it is a short path: the thing you want to hear is already in a tab.

|  | Browser extension | Desktop app |
| --- | --- | --- |
| What it captures | the audio of the tab you are on | audio at the operating-system layer, whatever is playing it |
| Where it runs | in the browser, attached to the tab | on the machine, alongside the browser |
| Good for | listening to a Meet call, or any other tab | listening, plus the two-way Meeting mode described here |
| Two-way outgoing direction | not covered | Meeting mode, with a virtual microphone |

So the split is simple. If you only need to understand what is being said, the extension is the shorter route. If you need the other side to hear you in their language, that is the desktop app's Meeting mode — the outgoing leg has to reach Meet as a microphone device, and devices exist at the operating-system level.

## Meeting mode is not covered by the free minutes

**The free tier does not cover Meeting mode.** Free minutes are for one-way listening; starting a two-way meeting session requires a paid plan or a minute pack. Better to find that out before a call than during one — check [pricing](https://voxislive.com/pricing) and start a session once ahead of the day you need it.

## Setting up, in order

1. Install VoxisLive and install a virtual microphone driver such as VB-CABLE. Restart the browser afterwards, or Meet will not list the new device.
2. Open VoxisLive and choose the **Meeting** scenario, then pick your real microphone — the one you actually speak into.
3. Set the two languages: the one you want to hear, and the one the other side should hear.
4. In Google Meet, open Settings › Audio and set Microphone to the virtual cable's recording device, leaving Speakers on your headphones.
5. Start the session in VoxisLive, then join the meeting as you normally would.
6. Say one sentence and watch Meet's level meter. Movement a few seconds after you stop talking means the outgoing leg is wired correctly.

If step six produces nothing, the problem is almost always the device picker rather than the translation: either Meet is still on your real microphone, or the browser was not restarted after the driver went in.

## Where to go next

The general shape of two-way meeting translation — both directions, the language pickers, what participants can and cannot see — is on the [meetings hub](https://voxislive.com/use-cases/meetings), and it applies to Meet unchanged. If a device is missing, or a session starts and stays silent, work through the [troubleshooting](https://voxislive.com/troubleshooting) checklist, which covers the audio-routing cases in the order they usually happen. For the capture path itself, see [how it works](https://voxislive.com/how-it-works) and [features](https://voxislive.com/features).

FAQ

## Common questions

### Do I need to install a Google Meet add-on or get Workspace admin approval?

No. Nothing is installed into Meet and nothing joins the call, so there is no third-party app for a Workspace admin to approve. The capture happens at the operating-system audio layer on your own machine, which is why the conferencing app does not matter.

### Can the other participants hear me in their language?

Yes, with a virtual microphone. Meeting mode runs an outgoing session that translates what you say and speaks it into a virtual microphone device — a free driver such as VB-CABLE — which you then select as your microphone in Meet. Without that driver, Meeting mode runs as listen-only: you hear them translated, they hear your untranslated voice.

### Should I use the browser extension instead, since Meet runs in a tab?

If you only need to understand the call, the extension is the shorter route: it captures the audio of the tab you are on and speaks it back. If you need the other side to hear you in their language, use the desktop app's Meeting mode — the outgoing direction has to reach Meet as a microphone device.

### Is Meeting mode included in the free minutes?

No. The free tier does not cover Meeting mode. Free minutes apply to one-way listening; a two-way meeting session needs a paid plan or a minute pack. See pricing.

### Will anyone see that I am using it?

There is no participant entry, no extra tile and nothing for the host to admit, because nothing joins the meeting. What is visible is ordinary: your microphone device is a virtual one rather than a headset, and your speech reaches the call a few seconds after you say it.

### The virtual microphone does not appear in Meet's device list. Why?

Two common causes. The browser was not restarted after the driver was installed — Meet enumerates devices when the browser starts. Or microphone permission for the site was denied earlier, in which case the picker looks empty no matter what is installed. Fix the permission, restart the browser, then reopen Settings › Audio.


## Structured data (JSON-LD)

```json
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "BreadcrumbList",
      "itemListElement": [
        {
          "@type": "ListItem",
          "position": 1,
          "name": "Home",
          "item": "https://voxislive.com/"
        },
        {
          "@type": "ListItem",
          "position": 2,
          "name": "Use cases",
          "item": "https://voxislive.com/use-cases/"
        },
        {
          "@type": "ListItem",
          "position": 3,
          "name": "Google Meet translation",
          "item": "https://voxislive.com/use-cases/google-meet-translation"
        }
      ]
    },
    {
      "@type": "WebPage",
      "name": "Google Meet Translation, Both Ways | VoxisLive",
      "url": "https://voxislive.com/use-cases/google-meet-translation",
      "description": "Translate a Google Meet call in both directions on Windows. No bot joins, no Workspace admin approval, nothing installed inside the meeting.",
      "inLanguage": "en",
      "isPartOf": {
        "@type": "WebSite",
        "name": "VoxisLive",
        "url": "https://voxislive.com/"
      },
      "publisher": {
        "@type": "Organization",
        "name": "VoxisLive",
        "url": "https://voxislive.com/"
      }
    },
    {
      "@type": "FAQPage",
      "mainEntity": [
        {
          "@type": "Question",
          "name": "Do I need to install a Google Meet add-on or get Workspace admin approval?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "No. Nothing is installed into Meet and nothing joins the call, so there is no third-party app for a Workspace admin to approve. The capture happens at the operating-system audio layer on your own machine, which is why the conferencing app does not matter."
          }
        },
        {
          "@type": "Question",
          "name": "Can the other participants hear me in their language?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Yes, with a virtual microphone. Meeting mode runs an outgoing session that translates what you say and speaks it into a virtual microphone device — a free driver such as VB-CABLE — which you then select as your microphone in Meet. Without that driver, Meeting mode runs as listen-only: you hear them translated, they hear your untranslated voice."
          }
        },
        {
          "@type": "Question",
          "name": "Should I use the browser extension instead, since Meet runs in a tab?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "If you only need to understand the call, the extension is the shorter route: it captures the audio of the tab you are on and speaks it back. If you need the other side to hear you in their language, use the desktop app's Meeting mode — the outgoing direction has to reach Meet as a microphone device."
          }
        },
        {
          "@type": "Question",
          "name": "Is Meeting mode included in the free minutes?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "No. The free tier does not cover Meeting mode. Free minutes apply to one-way listening; a two-way meeting session needs a paid plan or a minute pack. See pricing."
          }
        },
        {
          "@type": "Question",
          "name": "Will anyone see that I am using it?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "There is no participant entry, no extra tile and nothing for the host to admit, because nothing joins the meeting. What is visible is ordinary: your microphone device is a virtual one rather than a headset, and your speech reaches the call a few seconds after you say it."
          }
        },
        {
          "@type": "Question",
          "name": "The virtual microphone does not appear in Meet's device list. Why?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Two common causes. The browser was not restarted after the driver was installed — Meet enumerates devices when the browser starts. Or microphone permission for the site was denied earlier, in which case the picker looks empty no matter what is installed. Fix the permission, restart the browser, then reopen Settings › Audio."
          }
        }
      ]
    }
  ]
}
```