You can record a Zoom meeting on a Mac without a bot by capturing the audio at the operating-system level instead of asking Zoom for it: your microphone plus your Mac's system audio output, recorded locally. Nothing joins the call, Zoom is never involved, and it works whether you are the host or a guest. Here's how, and where the limits are.
Why can't you just use Zoom's own recording?
You often can't, because Zoom's recording is a permission, not a feature you own. Zoom's documentation is explicit that the host is the only person who can start a computer recording by default; to let anyone else do it, the host has to grant recording privileges during the meeting or make you an alternative host. If you're the guest on a client call, that's a conversation you may not want to have mid-meeting.
Two more constraints matter. First, Zoom always announces it: participants get a consent prompt and a visible recording indicator, which is by design and, for many meetings, entirely appropriate — but it is not something you can opt out of. Second, storage is tiered. Zoom's pricing page shows the free Basic plan limited to local recording, with cloud recording appearing on Pro and Business at 10 GB per licence (as of September 2026).
So Zoom's own recorder answers a narrower question than the one most people are asking. It records the meeting you control, announced, into the tier you pay for. Recording your own side of a call you merely attend is a different problem, and Zoom is the wrong layer to solve it at.
Why doesn't macOS screen recording capture the other side?
Because Apple's built-in screen recording captures your microphone and nothing else. Both the Command-Shift-5 toolbar and QuickTime Player offer exactly one audio choice, and Apple's support documentation says so plainly:
To record your voice or other audio with the screen recording, choose a microphone.
There is no system-audio option in that sentence because there is no system-audio option in the feature. This still holds in macOS 26. The result is the classic half-recording: you are perfectly audible, everyone else is silent, and you don't find out until you play it back.
The traditional workaround is a virtual audio driver — BlackHole is the maintained open-source one — which creates a fake audio device, has you route your Mac's output through it, and lets QuickTime read that back as an input. It works. It also means installing a driver, changing your default output device before every call, and remembering to change it back, all while your actual speakers behave strangely. It is a studio technique wearing a note-taking hat.
How does botless Zoom recording actually work?
A purpose-built recorder skips both dead ends by taking the audio where macOS already has it. From your Mac's point of view a Zoom call is two streams: the microphone (you) and the system audio output (everyone else). Capture both locally and you have the whole conversation without touching Zoom.
Since macOS 14.2, the clean way to get that second stream is Core Audio process taps — CATapDescription and AudioHardwareCreateProcessTap — a first-class API for capturing system or per-process audio with no driver and no screen-capture machinery. A tap can exclude your own app's output, so the recorder doesn't record itself. We wrote up the full engineering picture, including the ScreenCaptureKit era that preceded it, in how botless meeting recorders work on macOS.
The practical consequence is that Zoom is not a participant in the arrangement. It cannot show a banner, cannot deny permission, and cannot block the recorder, because nothing has connected to the meeting. The same recorder works identically on Google Meet, Teams, Webex, or a phone call on speaker — the audio path is the same one every time.
Step by step: recording a Zoom call with no bot
- Install a botless recorder that captures system audio on-device. Speechmark works this way; so do several others (Granola and BB Recorder among them, as of September 2026).
- Grant two macOS permissions, once. Microphone, and system-audio recording — the latter lives in System Settings → Privacy & Security → Screen & System Audio Recording. macOS asks you directly; nothing is asked of Zoom.
- Join the Zoom call normally, with audio playing through your Mac. Headphones are fine — the tap reads the output stream, not the room.
- Start recording from the menu bar and take the meeting. No participant list entry appears, because there is no participant to add.
- Stop when the call ends. With an on-device tool, transcription and diarization run locally afterwards and the transcript lands as a file on your disk.
The only genuine prerequisite is the macOS version: process-tap-based apps need macOS 14.2 or later.
What this does not solve: consent
Botless capture removes a technical announcement, not a legal or professional obligation. Zoom's prompt was doing two jobs — one of them was telling people something true.
Recording-consent law varies by jurisdiction: some US states and many countries require every party to agree, others only one, and none of that changes because the recorder is invisible. Nor does it override your employer's policy or your 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 a bot is disruptive, blocked by IT, or awkward in front of a client — not a way to record people who would say no.
Where Zoom's own recording is the better choice
Zoom's recorder genuinely wins in several cases, and it's worth naming them:
- You need video. Process taps capture audio only. Zoom's recording gives you gallery view, shared screens, and slides.
- You want everyone notified automatically. If your compliance posture depends on a visible, logged consent prompt, Zoom's built-in indicator does that for you and an OS-level recorder does not.
- The recording belongs to the organisation, not you. Cloud recordings land in an account admins can govern, retain, and audit — the right answer for regulated teams.
- You're not on a Mac. Everything here is macOS-specific.
Use the OS-level path when you're a participant capturing your own notes, when bots are blocked or unwelcome, or when the audio genuinely must not leave your machine.
The bottom line
Zoom's recorder asks Zoom for permission. Apple's screen recorder only hears you. A botless recorder sidesteps both by reading the audio macOS already has — microphone plus system output — which is why it works as a guest, needs no host approval, and never appears in the participant list.
Whether that also makes it private is a separate question, and it depends on what happens after capture: transcription and storage that stay offline are what make a local recording actually local. Speechmark does the whole chain on-device — capture, transcription, diarization, summaries — and is a one-time purchase ($79, currently $49 for founding users) rather than a subscription. If you're leaving a bot-based tool specifically, bot-free Otter alternatives covers that migration.