How to Record Zoom, Teams and Google Meet Meetings (With and Without Host Permission Rules)

Meeting recordings have become part of the basic plumbing of remote work. They feed searchable archives, let absent teammates catch up at double speed, and settle "who agreed to what" debates before they start. Yet the mechanics remain surprisingly confusing: recording permissions differ across Zoom, Microsoft Teams, and Google Meet; the rules differ again between free and paid plans; and hovering over all of it is a legal question most people have never looked up — whether everyone on the call needs to consent.

This guide walks through the built-in recording features of the big three platforms as they work in 2026, the consent laws and etiquette you should actually understand before pressing record, how to record as a participant using OBS or your system's recorder when you have permission but not the host role, and where the booming AI notetaker category fits into all of this.

Built-in recording: how each platform handles it

The platforms' native recording is almost always your best option when it is available. It captures clean audio directly from the call (no speaker-to-microphone quality loss), produces a tidy gallery or speaker view, and on paid plans adds transcripts automatically.

Zoom

Zoom offers two recording modes. Local recording saves MP4 video and M4A audio to the host's computer and is available even on free accounts. Cloud recording, available on paid plans, saves to Zoom's servers with streaming links, automatic transcription, and options to record gallery view, speaker view, and shared screen as separate files.

By default only the host can record. Participants can record locally if the host grants permission through the Participants panel (More, then Allow Record), and hosts can enable recording permission by default in their web settings. When any recording starts, Zoom plays an audible announcement and shows a persistent indicator to everyone — participants on free and paid plans alike will always know.

Microsoft Teams

Teams recording is cloud-only and tied to Microsoft 365: recordings save to OneDrive or SharePoint, inherit your organization's retention policies, and appear in the meeting chat when processing finishes. Who can record is governed by admin policy; typically the organizer and people from the same organization can start a recording, while external guests and anonymous attendees cannot. Transcription can run alongside or independently of recording, and the recording banner is shown to all participants. Teams Premium adds extras such as sensitivity-label-driven restrictions on who can even watch a recording afterward.

Google Meet

Meet's recording lives on the paid side of Google Workspace (Business Standard and up, plus education and enterprise tiers); free personal accounts cannot record natively. The host, co-hosts, and members of the host's organization (when allowed) can start a recording from the Activities panel. Files land in the organizer's Google Drive in a "Meet Recordings" folder and are linked in the calendar event. Meet records the active speaker and shared content rather than a full gallery, and Gemini-powered "take notes for me" features can generate summaries with or without a full recording.

Quick comparison

Feature	Zoom	Microsoft Teams	Google Meet
Free plan recording	Yes, local only	No	No
Cloud recording	Paid plans	Yes (OneDrive/SharePoint)	Paid Workspace tiers
Who can record	Host; participants with permission	Organizer and same-org users, per policy	Host, co-hosts, same-org users
Auto transcription	Cloud recordings on paid plans	Yes, with speaker attribution	Yes, plus Gemini notes
Recording notification	Audible announcement plus banner	Banner to all participants	Banner to all participants

The consent question: laws and etiquette

Before touching any workaround, understand this section. Recording a conversation without proper consent can be a civil or even criminal matter depending on where the participants are located.

In broad strokes, jurisdictions follow one of two models. One-party consent means a conversation may be recorded as long as at least one participant (which can be you, the recorder) consents. Two-party consent — more accurately "all-party consent" — requires everyone on the call to agree. In the United States this varies by state: federal law and the majority of states are one-party, while a significant group of states, including California, require all parties' consent. Much of Europe layers GDPR on top, treating recordings as personal data processing that needs a lawful basis, and countries elsewhere range across the spectrum. Critically, on a multi-state or international call, the safe practice is to satisfy the strictest jurisdiction on the line.

This is not legal advice, and if recordings are business-critical for you (sales calls, interviews, research sessions), spend an hour with your legal team to establish a policy. But the practical etiquette that keeps you safe nearly everywhere is simple:

• Announce at the start that you are recording and why, and give people a moment to object.
• Prefer the platform's built-in recording precisely because it notifies everyone automatically.
• Never share a recording beyond its original audience without checking; a recording consented to for "internal notes" is not consented to for a public YouTube upload.
• Delete recordings you no longer need. Retention is a liability, not just a convenience.

Recording as a participant with OBS or a system recorder

Sometimes you have every right to record — you have asked, everyone agrees — but the mechanics do not cooperate: the plan lacks cloud recording, the host cannot find the permission toggle, or you want your own copy at higher quality. In these cases, recording your own screen with OBS Studio, the macOS Screenshot toolbar, or the Windows Snipping Tool works on any meeting platform, because to your computer the meeting is just another window. To be clear on scope: this is for capturing meetings you are allowed to record; the notification banner other participants rely on will not appear, which is exactly why the consent conversation above has to happen out loud.

The OBS setup for meetings

1. Add a Window Capture source pointed at the meeting window (or Display Capture if you will be switching between the call and shared documents).
2. Confirm the audio mixer shows both Desktop Audio (the other participants' voices) and your microphone.
3. Enable separate audio tracks in Settings, Output, Recording — track 2 for your mic, track 3 for desktop audio — so you can balance or clean up either side in editing.
4. Record in Hybrid MP4 format so an unexpected crash mid-meeting does not destroy the file.

Audio routing, the part that trips people up

The classic failure mode: your recording captures everyone else perfectly but your own voice is missing, or you hear yourself twice. The cause is that meeting apps and recorders both grab audio devices, and the routing has to be deliberate.

On Windows, OBS's Desktop Audio captures whatever plays through your default output device, and Mic/Aux captures your microphone directly — usually everything just works, but if you use a headset with its own audio device, verify both sources in OBS point at the right hardware. Modern OBS also offers Application Audio Capture, which grabs audio from just the meeting app and is the cleanest option: notification dings from other apps stay out of the recording.

On macOS, the long-standing quirk is that the system provides no built-in way for apps to capture system audio. OBS on current macOS versions can use the system's audio capture support directly; on older setups, a free virtual audio driver such as BlackHole routes meeting audio into your recorder. Wear headphones in every case — speakers bleeding into your microphone create echo for everyone on the call and a muddy recording for you.

Transcription: often more useful than the video

An honest observation from years of recording meetings: most recordings are never watched, but transcripts get searched constantly. All three platforms now generate transcripts with speaker attribution on their paid tiers, and the quality has become genuinely good, including for accented speech and technical vocabulary. If your plan includes transcription, turn it on by default. If it does not, running a recording through a transcription tool such as Whisper (free, runs locally) or any of the commercial services often delivers most of the value of the recording at a fraction of the storage.

Storing and sharing recordings sensibly

Meeting videos are large, sensitive, and multiply quickly. A few practices prevent the usual mess:

• Let the platform manage storage when possible. Zoom cloud, OneDrive/SharePoint, and Google Drive all apply your organization's access controls and retention rules automatically. A folder of MP4s on a laptop does not.
• Share links, not files. A link can be revoked or expire; an emailed MP4 is forever beyond your control.
• Name recordings so future-you can find them. Date, team, and topic beats "Recording (14).mp4" every time.
• Set a retention habit. Many organizations auto-delete meeting recordings after 30 to 180 days. If yours does not, calendar a quarterly cleanup.

The AI notetaker landscape

The fastest-changing corner of this space is the AI meeting assistant. Tools like Otter.ai, Fireflies, Fathom, and tl;dv join meetings as bots or run alongside your call, producing transcripts, summaries, action items, and searchable archives, while the platforms themselves have built the same capabilities in — Zoom's AI Companion, Teams' Copilot-powered intelligent recap, and Gemini in Meet can all summarize a meeting you never recorded in the traditional sense.

Two cautions temper the enthusiasm. First, a notetaker bot is a recording for consent purposes: it should be announced and consented to like any camera-and-microphone capture, and many organizations now restrict which notetakers may join calls at all, precisely because meeting content flows to a third-party service. Second, summaries are lossy; for decisions with consequences, check the transcript or recording rather than trusting the AI's three bullet points. Used with those caveats, a good notetaker eliminates the main reason people wanted recordings in the first place.

Frequently asked questions

Can I record a Zoom meeting on a free plan?

Yes — free accounts include local recording, saved to the host's computer. Participants need the host to grant recording permission. Cloud recording requires a paid plan.

Will other people know I am recording?

If you use built-in recording, yes, always: all three platforms show a banner and Zoom plays an audio announcement. If you record your screen with OBS or a system recorder, no automatic notification appears, which is why announcing it yourself is both an ethical and, in all-party consent jurisdictions, a legal necessity.

Where do Teams and Meet recordings actually go?

Teams recordings save to the recorder's OneDrive (ad-hoc meetings) or the channel's SharePoint (channel meetings) and are linked in the chat. Meet recordings save to the meeting organizer's Google Drive in a "Meet Recordings" folder and attach to the calendar event.

What is the highest-quality way to record a meeting I host?

Use the platform's cloud recording for the reliable baseline copy, and optionally run OBS alongside for a high-bitrate local version with separate audio tracks. The two do not conflict, and you will be glad for the backup the day one of them fails.

Recording meetings well is mostly about doing three unglamorous things consistently: using the built-in tools where they exist, saying "I'm recording this, is everyone okay with that?" out loud, and keeping the resulting files organized and pruned. Get those habits in place and the technology, on every platform, is more than ready.