Who owns a Google Meet recording

Short answer: a Google Meet recording is normally saved as a file in the meeting organizer's Google Drive, in a folder called Meet Recordings. In Drive terms, that makes the organizer the file's owner, even if someone else pressed the record button. Two limits apply. First, Google's documentation describes exceptions where the file ends up with the person who started the recording instead. Second, owning the file in Drive is a storage and access arrangement. It does not settle copyright, consent, or any other legal question about the recorded speech.

A note on sources: no specific evidence, such as current help-center text, edition tables, or dates, was supplied for this article. What follows reflects Google's generally documented behavior and general principles. Recording features, edition eligibility, and admin controls change over time and vary by organization, so check the details against Google's current Meet help pages or with your Workspace administrator.

What "ownership" means for a Meet recording

The question usually covers three different things:

• File ownership: whose Google Drive holds the recording and counts it against their storage. This is normally the organizer.
• Access: who can open, download, or share the file. The owner controls this through ordinary Drive sharing settings, and Workspace admin policies may restrict it further.
• Legal rights: who holds copyright in the content and whether recording was lawful. Drive placement does not determine either, and the answer depends on context such as employment agreements and applicable law.

Where the file goes and who is notified

• Storage: the recording is processed after it stops and is then placed in the organizer's Meet Recordings folder in My Drive.
• Notification: Google states that both the organizer and the person who started the recording receive an email with a link to it.
• Calendar: when the meeting was scheduled through Google Calendar, the recording link is typically attached to the event. Invitees in the organizer's organization may then get access automatically, depending on settings.
• Exceptions: Google's documentation describes cases where the file is saved to the Drive of the person who started the recording instead. These include some meetings whose organizer is outside the recorder's organization. The exact conditions were not available in the supplied material, so confirm them in Google's current documentation.

Who can record in the first place

Recording is tied to Google Workspace editions and administrator settings. It is generally not available on free personal accounts. Even on an eligible edition, an admin can disable it or limit it to certain users, and the organizer may control whether other participants can start a recording. If the record option is missing, the likely causes are your account type, your organization's policy, or the meeting's host controls. A webcam or microphone problem is not one of the usual causes.

Changing or sharing ownership

Because the recording is an ordinary Drive file, the owner can share it like any other file. Within the same Workspace organization, Drive generally lets a file's owner transfer ownership to another user, subject to admin policy. Transfers across organizations or to personal accounts are commonly restricted. Downloading a copy gives the downloader a separate file they control, so a shared recording can spread beyond the original owner's control.

Ownership is not consent or copyright

Meet shows participants a notice when recording starts, but that notice does not make every recording lawful. In the US, consent rules for recording conversations differ by state, and some states require all parties to agree. Workplace recordings may also fall under employer policies or contracts that assign rights to the organization rather than to the individual organizer. For a specific legal concern, consult a qualified professional. Google's Drive behavior is not a legal answer.

What the recording captures from your webcam microphone

Whoever owns the file, its audio comes from the meeting itself, not from your device. Each participant's speech reaches the recording through the microphone selected in Meet's audio settings. That might be a webcam's built-in mic, a headset, or a USB microphone. The audio is also processed by Meet before it is recorded. Features such as noise cancellation are likely to affect it. In practice:

• Choose the input deliberately. Meet uses whichever microphone is selected, which may be the webcam mic, a laptop mic, or a headset. Check this before recording starts, because the recording keeps whatever was transmitted.
• Don't expect a raw local track. The recording is a mix of what the meeting carried, so it is not a substitute for a clean local recording from your own microphone.
• Noise reduction applies before recording. Background suppression can remove noise, but it can also slightly alter the voice. Whether this applies to the recorded file in every configuration is not confirmed by the supplied evidence.
• If you need your own high-quality copy of your speech, record locally with your own software, with appropriate consent. You will own that file outright, separately from the Meet recording.

Gaps in this answer

The supplied material did not confirm the following: which Workspace editions currently include recording; the precise rules for cross-organization meetings; how long recordings take to process; any retention or storage limits; and whether specific audio processing settings are applied to the recorded file. Check these points in Google's current documentation or with your administrator before relying on them.