Is It Legal to Record a Zoom Meeting? Consent Rules by State (2026)

Recording a Zoom meeting is legal when the consent rules of every participant's state are satisfied, and the person doing the recording is responsible for satisfying them, not Zoom. In most states your own consent is enough because you are a participant. In roughly a dozen jurisdictions, everyone on the call must consent or at least be clearly informed first. The platform's recording banner helps, but it does not settle the question by itself, and the answer changes again when the recorder is an AI notetaker instead of a person.

The Short Answer, State by State

A Zoom meeting is a wire or electronic communication under state wiretap statutes, so it follows the same consent rules as a phone call in almost every state. Under the federal Wiretap Act, 18 U.S.C. § 2511(2)(d), a party to a communication may record it unless the recording is made for a criminal or tortious purpose. Most states mirror that one-party rule: if you are in the meeting, your own consent is enough, and nothing requires you to announce the recording.

The exceptions are where people get into trouble. Seven states require affirmative all-party consent across the board: California, Florida, Illinois, Maryland, New Hampshire, Pennsylvania, and Washington. Several more get there in their own ways. Two are call-specific: Nevada requires all-party consent for anything transmitted over a network (a judicial construction from Lane v. Allstate that runs against the statute's literal text) while staying one-party in person, and Connecticut imposes civil all-party liability for recorded calls even though its criminal law is one-party. Three apply their stricter rule on every medium: Massachusetts bans any secret recording, Montana requires that all parties know, and Delaware's two conflicting statutes are safest read as all-party across the board.

Oregon is often described as putting video meetings under a one-party rule, but its statute is narrower than that. ORS 165.540(6)(a) exempts from the general notice requirement in ORS 165.540(1)(c) only communications that are part of enumerated proceedings, and the video-conferencing clause functions as an alternative to using an unconcealed recording device rather than as a separate one-party rule. The enumerated categories are public or semipublic meetings, regularly scheduled classes, and private meetings or conferences. The private-meeting category, the one that covers an ordinary private Oregon video call, applies only "if all others involved knew or reasonably should have known that the recording was being made," which is an all-participants-knowledge requirement rather than one-party consent. Genuine one-party treatment appears only in ORS 165.540(6)(b), which covers a participant who records a video conference intending to capture alleged unlawful activity and who is coordinating with law enforcement, an attorney, or an enforcement or regulatory entity, or who reasonably believes the recording may be used as evidence in a judicial or administrative proceeding. Outside that narrow lane, treat an Oregon video meeting as requiring everyone on it to know about the recording.

When participants sit in different states, there is no national rule for whose law governs, and the leading case points strict. In Kearney v. Salomon Smith Barney, the California Supreme Court held that California's all-party statute applies to a call that takes place partly in California, even though the recording happened in Georgia, where one-party consent made it lawful. The safe rule for any interstate meeting is to follow the strictest state on the call. Our recording consent checker computes exactly this: pick your state, the other party's state, and the medium, and it shows which rule controls and what satisfies it.

What Zoom Actually Does When Recording Starts

Zoom's own documentation is unusually specific about its notice mechanics, and they matter legally. Zoom states that it "will always notify meeting participants that a meeting is being recorded," in two forms: participants on the desktop or mobile app see an on-screen recording consent disclaimer, and participants who joined by phone "hear an audio prompt when they first join the meeting if it is already being recorded or at the time the recording is started."

How locked-down that notice is depends on the account. On Basic, Pro, Business, and trial accounts with fewer than 100 licenses, the on-screen disclaimer "can't be disabled or customized." Enterprise, Education, and Business accounts with 100 or more licenses can disable it for their own internal users, but "the recording consent disclaimer is required for all guest participants." Phone participants always hear a voice prompt regardless of account type. Admins can even require dial-in participants to press 1 to consent, though Zoom's documentation is candid about the limit of that feature: "Even if users do not press 1 after the second voice prompt has been provided, the meeting will still be recorded."

Zoom's terms of service then hand the legal question back to the person recording: "You are responsible for compliance with all Laws governing the monitoring or recording of conversations as the Host," with the participant's remedy framed the same way courts frame implied consent: "If you do not consent to being recorded, you can choose to leave the recorded session."

Google Meet and Microsoft Teams

Both competitors notify participants, but with a weaker default than most people assume. Google Meet participants "get a notification when the recording starts or stops." An administrator can require every participant to give explicit consent, choosing Start, Join, Continue, or Leave, before recording, transcription, or Gemini notes run, but Google's documentation says that setting "is off by default." Google's Workspace service terms carry the consent duty: customers agree "not to, and not to allow its End Users to, record telephone conversations without consent if such consent is required by applicable laws."

Microsoft Teams is similar: in the global admin policy, "recording and transcription are on by default," while the explicit-consent feature, which asks each participant a Yes/No consent question before they can unmute or turn on their camera, is off by default. When it is on, a participant who answers No gets a view-only experience, and each participant's consent choice is logged to the attendance report and audit logs. Teams' Copilot has no separate notice of its own; it rides the recording and transcription banner.

The practical upshot: a Zoom recording started by the host comes with real, hard-to-suppress notice. A Meet or Teams recording may come with only a start notification unless an admin has turned the consent flow on. And none of the platforms takes legal responsibility for consent: Zoom's and Google's terms put it expressly on the host or customer, and Microsoft's product terms make the customer "solely responsible for displaying and/or obtaining appropriate consents."

Does the Platform Notice Count as Consent?

In most all-party states, yes, if the notice actually reaches people and they keep participating. The doctrine is implied consent: someone who hears a clear announcement that the meeting is being recorded, has a real chance to object or leave, and keeps talking has consented in most all-party jurisdictions. Washington writes a mechanism directly into its statute, but a narrow one: consent "is considered obtained" when one party has announced to all other parties, in any reasonably effective manner, that the conversation is about to be recorded, with the proviso "That if the conversation is to be recorded that said announcement shall also be recorded." A visual platform banner shown before recording begins is neither an announcement made by a party nor captured in the recording, so relying on RCW 9.73.030(3) means a party has to announce the recording audibly once recording is underway, so that the announcement lands in the file itself.

The two caveats are real. First, the notice has to be perceived: a banner a dial-in participant never sees, a late joiner who missed the announcement, or a bot name buried in a large attendee list is exactly where the consent argument fails, and Massachusetts treats a recording as unlawfully "secret" whenever a participant is genuinely unaware of it. Second, Pennsylvania reads its "prior consent" requirement strictly; our Pennsylvania AI meeting recording guide treats a notification banner alone as insufficient there, and no court has settled whether continued participation after seeing a bot's name in the attendee list counts as consent under Pennsylvania law. When the stakes matter, announce it out loud and get an audible yes.

AI Notetakers Are a Different Question

An Otter.ai, Fireflies, or similar bot changes the analysis in two ways. The first is consent mechanics. Otter's Notetaker joins as a visible named guest, "[Your Name]'s Notetaker (Otter.ai)," and cannot join anonymously, but visibility is not consent, and Otter's own help documentation simply recommends "always obtaining consent and following your local laws regarding recording." Its terms of service state that the customer "is solely responsible for providing any notices to, and obtaining consent from, individuals in connection with any recordings." Meanwhile the default, once a calendar is connected, is that the bot "will automatically join all calendar events with a valid Zoom, Google Meet, or Microsoft Teams meeting URL." That configuration is the one our state guides flag as highest-risk under consent law, because a bot that records a meeting its owner never attends leaves no consenting party in the room at all.

The second is the vendor itself. On August 13, 2026, the judge in In re Otter.AI Privacy Litigation let the core claims proceed past dismissal, on three distinct theories: the California Invasion of Privacy Act claim survived on the holding that Otter is plausibly a third-party eavesdropper, not just the host's recording tool, because it allegedly retains conversations and uses them to train its own models; the federal Wiretap Act claim survived because that same alleged training use could be a tortious purpose that defeats the statute's party exception; and the Illinois BIPA claims survived on allegations that Otter collects voiceprints without the written consent Illinois requires. That is a ruling on the pleadings, not a finding of liability, but it means the safest current practice for AI notetakers is affirmative all-party consent plus auto-join disabled, in every state. Our full coverage: the Otter.ai lawsuit, explained and AI meeting recording laws by state.

Work Meetings: Legal Is Not the Same as Allowed

In a one-party state, an employee can generally record a meeting they attend without breaking recording law. That does not make it consequence-free: employer policies can prohibit recording, and violating the policy can be a firing offense even where the recording itself was lawful. The reverse also holds: an employer recording meetings still owes the same consent duties to every participant, including outside guests. Recording law and employment policy are separate questions; clear both before pressing record.

Penalties If You Get It Wrong

Unlawful recording is a crime in every all-party state, and the grades vary enormously: Pennsylvania treats it as a felony punishable by up to seven years, Florida up to five, California as a wobbler, Washington as a gross misdemeanor. Civil exposure is often the larger number: California allows $5,000 per violation with no proof of harm, and Illinois adds separate biometric-privacy damages of $1,000 to $5,000 per violation when a tool derives voiceprints. Several states also make unlawful recordings inadmissible in their own courts. The state-by-state details are in each state's guide in the AI meeting recording cluster.

Related guides

• US Recording Consent Checker
• AI Meeting Recording Laws by State
• The Otter.ai Lawsuit, Explained
• California AI Meeting Recording Laws
• Pennsylvania AI Meeting Recording Laws
• One-Party Consent States

This is general legal information, not legal advice. Platform behaviors reflect vendor documentation reviewed on August 20, 2026 and can change with product updates; state rules reflect our state guides as of the same date. Consult a lawyer licensed in the relevant state about any specific recording.