Google Meet changes where recordings and notes are stored in Drive

Google Meet is changing how recordings, transcripts, and AI-generated meeting notes are organized in Google Drive. Instead of leaving meeting files together in the host’s Drive, Google will create a “Google Meet” folder and a separate subfolder for each meeting.

The change is useful for people searching for a recap, but it can break assumptions embedded in scripts, archiving jobs, and internal instructions. Google specifically tells administrators to audit automations that rely on folder names or IDs.

What changes in Google Drive

New recordings, transcripts, and “Take notes for me” documents will be stored in the meeting organizer’s “Google Meet” folder. Each meeting gets its own subfolder. Artifacts from separate instances of a recurring meeting share the same meeting folder.

Attendees who already have access to an artifact will receive a shortcut in their own “Google Meet” folder. A shortcut improves discovery; it does not replace the file’s sharing controls. Google’s Meet documentation says access to notes is still determined by the sharing settings selected by the host or co-host.

• One top-level “Google Meet” folder in the organizer’s My Drive.
• One subfolder per meeting, including a shared folder for recurring instances.
• Shortcuts for attendees who have access to the source files.
• Calendar and email links continue to provide access where applicable.

Existing Meet Recordings folders will move

Google will rename the existing “Meet Recordings” folder to “Legacy Meet Recordings” and move it inside the new “Google Meet” folder. The company says old recording and meeting-note links will continue to work.

Users may briefly see both “Meet Recordings” and “Google Meet” while the transition is taking place. Avoid treating that temporary duplication as evidence that files were copied. Confirm the destination and file owner before deleting or reorganizing anything.

Rollout dates and availability

The new organization applies to all Google Workspace customers. Rapid Release domains began receiving it on July 22, 2026, with a one-to-three-day rollout. Scheduled Release domains begin on July 30, also with a one-to-three-day rollout.

That leaves little preparation time for Rapid Release organizations. The first priority is not changing every process; it is identifying integrations that assume a fixed location and monitoring them through the rollout.

Admin checklist before rollout

Search Apps Script projects, Drive API integrations, no-code automations, backup tools, and records-management jobs for the old folder name. Also inspect workflows that watch one folder for newly created recordings or move every new file into a shared archive.

Do not replace one hard-coded folder path with another without testing. The meeting-level subfolders introduce another layer, and recurring meetings group files differently from unrelated calls. Use a test meeting to observe the actual file owner, parent folder, permissions, shortcut behavior, and timestamps before updating production logic.

• Inventory scripts and automations that reference “Meet Recordings.”
• Run one recorded meeting and one meeting using transcripts or AI notes.
• Test a recurring event separately from a one-time meeting.
• Verify whether archiving follows source files or attendee shortcuts.
• Confirm retention, Vault, and data-loss-prevention policies still cover the source artifacts.
• Update help-desk instructions and screenshots after the rollout reaches the domain.
• Monitor failed jobs and duplicate copies for at least one week.

Check sharing, consent, and storage at the same time

The folder change does not remove the need to review who receives meeting artifacts. “Take notes for me” can share notes with all invited guests, internal invitees, or only hosts and co-hosts, depending on the meeting settings. An attachment visible on a Calendar event does not by itself grant access to the underlying document.

Organizations can also require explicit participant consent before recording, transcription, or AI note-taking begins. Use this rollout as a prompt to verify those settings, available Drive capacity, and the owner responsible for artifacts when a meeting organizer leaves the company.

What end users should know

Tell users to look in My Drive → Google Meet before reporting a missing recording or recap. For recurring meetings, they should open the meeting’s folder rather than expect a new top-level folder after every call.

Users should not move source files merely to make them easier for colleagues to find. Share the source appropriately and let Drive shortcuts provide convenient access. If a recording appears missing during rollout, check the Calendar event, notification email, new folder, and legacy folder before opening a support ticket.