Transcribe Google Meet on whatever account you have
Whisperer never talks to Google. It hears the Meet tab the way your speakers do and writes the transcript locally — which means the account you are signed in with makes no difference, personal or corporate.
No extension · no Workspace add-on · no Google permissions
The answers below are an example. Your own base connects in the app.
…
…
Let's start with Q3 — how did conversion move?
Conversion is up 14% — let me pull up the funnel.
And the cost per lead?
Cost per lead is €12.40 — 9% under plan. Most of the gain came from organic.
Not a video — this is Whisperer itself, and the panel really answers. The microphone starts only when you press it.
Independence
Why the plan you are on stops mattering
Anything that transcribes a Meet call from inside Google is subject to what Google gives that account. Whisperer is outside: it captures the sound your computer is already producing, so a personal account, a school account and an enterprise tenant all behave identically.
The same independence explains why there is no extension to install and no scope to grant on your Google account.
- Inside Google Depends on the account What you get is determined by the plan, the domain policy and the administrator, and it can change without you.
- Outside Depends on your computer Two permissions on your own machine, and the result is the same on every account you sign into.
Setup
The browser is not part of the setup
Chrome, Safari, Firefox, the Meet desktop app — none of it matters, because capture happens below the browser. What matters is that the sound is coming out of this computer.
On macOS, grant the Screen Recording permission: that is the documented route to another application's audio, not a request to watch your screen. On Windows, no extra permission is needed — just check that the browser is playing through the default output device, since loopback captures only that one.
Limits
The same two, stated plainly
-
First
One recording at a time, not an archive migration
A finished recording can be uploaded: the Meetings section takes one file up to 25 MB — mp3, m4a, wav, ogg, flac, aac, plus mp4 and webm, from which the audio track is used. What is missing is bulk upload of a whole archive; and it spends the same minutes a live call does.
-
Second
Two speaker labels
You and everyone else. On a Meet call with several external guests, their lines are attributed to a single other-side label rather than to individuals.
Questions
Questions about Meet transcripts
Does this work on a free personal Google account?
Yes, identically. Whisperer does not use any Google feature, so nothing about your account type changes the result.
Do I need to install anything in the browser?
No. There is no extension. The desktop application captures audio at the system level, which is also why it keeps working when you switch browsers.
Will Meet show that transcription is on?
No, because Meet's own transcription is not being used and nothing has joined the call. Whether to tell the other participants is your decision.
Can I export the transcript?
Yes — as plain text or Markdown from the session page, and the session as a whole exports to SRT, VTT and JSON as well.
Only my own voice is in the transcript. Why?
System audio is not reaching Whisperer. On macOS that means the Screen Recording permission is missing; on Windows, the browser is probably playing through a device that is not the default output.
One Meet link is enough to check
Open a meeting on your own, play any recorded speech into it, and confirm the other-side label appears. That settles the permissions question for every service at once.