You can record a Google Meet call on a Mac without a bot by capturing audio at the operating-system level — your microphone plus your Mac's system audio output — instead of asking Meet for it. Nothing joins the call, so Meet's host-and-plan gating and Gemini's visible note-taking indicator both become irrelevant, and it works the same whether you're the organizer or a guest.
Why can't you just use Google Meet's own recording?
Often you can't, because Meet's recording is gated twice over: your Workspace admin has to turn it on, and the host needs an eligible plan. Google's support page is specific about who can actually press record: "You're the meeting host. You're from outside the host's organization and promoted to a co-host. You're from the host's organization and Host Management is off." A plain guest from another company isn't on that list. Even when you qualify, a Workspace administrator must turn on recording for your account before anyone can use it — the feature can be invisible to you even on a plan that supports it.
The eligible-plans list is broader than the common assumption that this is a "Business Standard and up" feature for companies. Google's own page names Business Standard and Business Plus, Essentials, several Enterprise tiers, Education Plus — and, separately, individual Google One subscribers with 2 TB or more storage and Workspace Individual subscribers. A solo user with a big-enough Google One plan can record; an employee at a company on Business Starter cannot. Plan name alone doesn't answer the question.
Recording also isn't quiet. Participants get a notification when the recording starts or stops, including people outside your organization, and the recording stops automatically after 8 hours. Recordings land in the organizer's Google Drive, and by default Meet keeps them for three months before admin-configured retention takes over.
Doesn't Google Meet already have an AI notetaker built in?
Yes — Gemini's "Take notes for me," and it's worth understanding before reaching for a third-party tool. Unlike a bot that joins as a separate participant, it runs inside Meet itself, and Google is explicit that it's visible to the room:
Google Meet informs all meeting participants that notes are being taken and the pencil icon appears on all participants' screens.
That's the opposite design choice from an OS-level recorder. An admin can also require explicit consent before "Take notes for me," recording, or transcription can start at all, and notes are saved to the organizer's Drive under the same retention policy as recordings.
This also answers a question worth asking directly: does Meet police outside AI notetakers the way Microsoft Teams now does, holding detected bots in the lobby? We found no such policy for Google Meet as of October 2026. Google's response to the bot-notetaker trend looks different from Microsoft's — build a first-party one with a visible indicator, rather than detect and gate third-party ones at the door.
Why doesn't Mac's own screen recording capture the other side?
Because Command-Shift-5 and QuickTime Player's screen recording take audio from exactly one source: your microphone. There's no system-audio option in the feature, in macOS 26 or any version before it. Record a Meet call this way and the transcript is just you, clear as day, answering questions nobody can hear.
The longstanding fix was a virtual audio driver — BlackHole is the maintained open-source one — that creates a fake output device, has you route your Mac's audio through it, and lets QuickTime read it back as an input. It works, at the cost of changing your output device before every call and remembering to change it back after.
How does botless Google Meet recording actually work?
A purpose-built recorder skips Meet's host gating and the driver workaround by taking audio where macOS already has it. From your Mac's perspective, a Meet call is two streams: your microphone and your Mac's system audio output. Capture both locally and you have the whole conversation without Meet ever knowing a recorder exists.
Since macOS 14.2, the clean way to capture that second stream is Core Audio process taps — CATapDescription and AudioHardwareCreateProcessTap — a driver-free, first-class API for system or per-process audio capture. A tap can exclude the recorder's own output, so it doesn't record itself. The full engineering picture, including the ScreenCaptureKit era that came before it, is in how botless meeting recorders work on macOS.
Because nothing connects to the meeting, Meet has nothing to notify, nothing to gate by plan, and nothing to hold in a lobby. The same recorder works identically on Zoom, Teams, Webex, or a phone call on speaker — the Zoom and Teams versions of this guide cover the platform-specific gating on those calls.
Step by step: recording a Google Meet call with no bot
- Install a botless recorder that captures system audio on-device. Speechmark works this way, as do several others, Granola among them (as of November 2026).
- Grant two macOS permissions, once: Microphone, and system-audio recording — System Settings → Privacy & Security → Screen & System Audio Recording. Meet is never asked.
- Join the Meet call normally, audio playing through your Mac. Headphones work fine — the tap reads the output stream, not the room.
- Start recording from the menu bar. No pencil icon, no recording notification, because nothing has joined as a participant.
- Stop when the call ends. With an on-device tool, transcription and diarization run locally afterward and the transcript lands as a file on your disk.
The one hard prerequisite is macOS 14.2 or later for process-tap-based apps.
What this does not solve: consent
Meet's recording notification and Gemini's pencil icon are both doing a real job — telling people something true. Capturing audio below the platform removes the technical announcement, not the underlying obligation.
Recording-consent law varies by jurisdiction: some US states and many countries require every party to agree, others require only one, and an invisible recorder changes none of it. Nor does it override your employer's recording policy or a client's expectations. The reasonable default is to say you're recording and why, and to stop if someone objects. Botless recording is the right tool when Meet's gating keeps you out of your own notes — not a way to capture people who would say no.
Where Google Meet's own recording is the better choice
- The organization needs the record. Meet recordings and Gemini notes land in the organizer's Drive under retention your admin controls, and can feed into Vault for legal hold — the right answer for regulated teams.
- You want everyone notified automatically. Meet's notification and Gemini's pencil icon are visible by design; an OS-level recorder shows nothing to anyone else.
- You want shared notes across the team. Gemini can share notes with every invited guest, including people outside your organization — a local transcript on your Mac is yours alone unless you send it.
- You need video, screen shares, or slides. Process taps capture audio only.
- You're not on a Mac. Everything here is macOS-specific.
Use the OS-level path when you're a guest Meet won't let record, when your plan or admin settings don't include recording, or when the audio genuinely must not leave your machine.
The bottom line
Google Meet's recorder asks your admin and your plan before it asks you, and its Gemini notetaker announces itself to the whole room on purpose. A botless recorder sidesteps both by reading the audio macOS already has — microphone plus system output — which is why it works as a guest, on any plan, with nothing for Meet to gate or announce.
Whether that also makes it private depends on what happens after capture: transcription and storage that stay offline are what separate a local recording from a local capture that gets uploaded anyway. Speechmark keeps the whole chain on-device — capture, transcription, diarization, summaries — as a one-time purchase ($79, currently $49 for founding users) rather than a subscription.