Quick answer: Google Meet is changing where meeting notes, transcripts, and recordings appear in Google Drive. New artifacts go into a Google Meet folder in the host’s My Drive, with a separate subfolder for each meeting. Existing Meet Recordings folders will be moved inside it and renamed Legacy Meet Recordings. Rapid Release rollout began July 22, 2026; Scheduled Release rollout starts July 30, 2026.
Action for Workspace admins: Check scripts, integrations, retention jobs, and support documentation that expect a folder named “Meet Recordings” or rely on a particular folder ID. Google specifically recommends auditing automations that depend on folder names or IDs.
What changes in Google Drive
| Item | Previous behavior | New behavior |
|---|---|---|
| Top-level location | Artifacts were placed in the host’s My Drive without meeting-based organization | A new Google Meet folder in the host’s My Drive |
| Organization | No folder per meeting | A subfolder is created for each meeting |
| Recurring meetings | Files were not grouped this way | Different instances of a recurring meeting share one folder |
| Attendee access | Files appeared only in the host’s Drive | Attendees who have access see shortcuts to the source files in their own Google Meet folders |
| Existing recordings | Stored in Meet Recordings | That folder moves under Google Meet and becomes Legacy Meet Recordings |
The attendee items are shortcuts to the source files, not newly created copies. Access still depends on the file’s sharing permissions.
Rollout dates and availability
- Rapid Release domains: full rollout over 1–3 days starting July 22, 2026.
- Scheduled Release domains: full rollout over 1–3 days starting July 30, 2026.
- Availability: Google says the organizational change is available to all Google Workspace customers.
- Admin control: Google did not announce a switch for disabling this folder organization.
This storage update does not by itself enable recording, transcription, or AI note-taking for an account. The applicable Meet feature, administrator settings, and account eligibility still determine which artifacts can be created.
Google Workspace admin checklist
1. Inventory folder-dependent automations
Search your Apps Script projects, Drive API integrations, no-code workflows, backup jobs, and records-management procedures for references to:
Meet RecordingsGoogle Meet- saved Drive folder IDs used for Meet artifacts
- rules that assume all recordings sit directly in one folder
2. Test with a real meeting
In a rollout-enabled test account, create a meeting and generate only the artifacts your organization normally uses. After processing completes, confirm:
- the Google Meet folder exists in the host’s My Drive;
- the meeting-specific subfolder contains the expected artifact;
- an attendee with permission can see the shortcut;
- an attendee without permission is not given unintended access; and
- downstream backup, archiving, and discovery workflows still find the source file.
3. Do not “fix” the transition too early
Google warns that users may briefly see both Meet Recordings and Google Meet while migration is underway. Avoid asking users to move or rename folders manually until the automatic transition has finished.
4. Update internal instructions
Replace screenshots and help-desk instructions that tell users to look only in My Drive > Meet Recordings. The new path for current artifacts is:
My Drive > Google Meet > [meeting-specific folder]
Older files should be under:
My Drive > Google Meet > Legacy Meet Recordings
5. Verify links rather than recreating them
Google’s Meet Help documentation says old recording links will continue to work. Test important bookmarks and embedded links before replacing them or making duplicate copies.
What users should do
- Open Google Drive and look for the new Google Meet folder.
- Open the subfolder named for the relevant meeting.
- For older recordings, check Google Meet > Legacy Meet Recordings.
- If you attended but did not host the meeting, look for a shortcut in your Google Meet folder.
- If a shortcut does not open, ask the file owner to review sharing access; the shortcut does not override permissions.
FAQ
Where are new Google Meet recordings saved?
They are saved in the meeting organizer’s Google Drive under the Google Meet folder, inside a subfolder created for that meeting.
What happened to the Meet Recordings folder?
Google will automatically move the existing folder inside the new Google Meet folder and rename it Legacy Meet Recordings. Both folder names may appear briefly during the transition.
Will old Google Meet recording links break?
Google’s updated recording documentation says old recording links will continue to work.
Do attendees receive their own copy of every file?
No. Attendees who already have access receive shortcuts to the source files. A shortcut is not a duplicate and does not change the underlying sharing permissions.
Does every recurring meeting get a new folder?
Google says files from different instances of a recurring meeting will share one folder.
Should admins update Drive API or Apps Script workflows?
Admins should at least audit and test them. Google specifically calls out scripts and automated workflows that rely on folder names or IDs.
Official sources
- Google Workspace Updates announcement (July 22, 2026)
- Google Meet Help: Record a video meeting
- Google Meet Help: Use transcripts
- Google Meet Help: Take notes for me
Last checked: July 23, 2026. Rollouts can take the stated period to reach every account.