How to troubleshoot a Google Meet recording that does not work

When Google Meet recording doesn't work, the cause is usually your account or permissions rather than your webcam or microphone. Meet's built-in recording is only available on certain paid Google plans. Even on those plans, the meeting host or an organization administrator can stop you from recording. If the Record option is missing or greyed out, look at your account, your role in the meeting and your admin's settings first. Your camera and microphone only matter when the recording exists but has no video or no sound.

Which plans include recording, and what the menus are called, change over time. No current plan list or version details were available for this guide, so check the details below against Google's current Meet Help Center.

The short answer, by symptom

• No Record option at all: your account type probably doesn't include Meet recording, you're on a device that can't start recordings, or an administrator has turned recording off.
• Record option visible but greyed out or blocked: you're probably not allowed to record this meeting, for example because you're not the host or co-host, or the host has restricted recording.
• Recording seemed to start but no file appeared: the file may still be processing, may have been saved to someone else's Google Drive, or may have failed because Drive storage was full.
• Recording exists but has no picture or no sound: the problem is on the input side. The camera or microphone wasn't sending anything into the meeting while the recording ran.

Are you using Meet's own recording or a separate screen recorder?

This guide is about the recording feature built into Google Meet, which saves to Google Drive. If you're using a separate screen-recording app or browser extension, Meet's account and permission rules don't apply. Instead, check that app's settings and your operating system's permissions. For example, macOS requires apps to be granted screen-recording access in System Settings before they can capture the screen.

Checks that narrow down the cause

Work through these checks in order. Each one rules out a single layer, so a result tells you about that layer only.

1. Account and plan

Look at which Google account is signed in to the meeting. You can see it from the profile picture in the corner of the Meet window. Personal Google accounts on the free tier generally can't record in Meet. Recording is tied to eligible Google Workspace editions and some paid individual plans. If you have several accounts, make sure you joined with the one that has the paid plan. This check tells you whether recording is available to you at all. It doesn't tell you whether you're allowed to record this particular meeting.

2. Device and app

Google has described starting a recording as something you do from Meet on a computer. If you're in the mobile app and can't find Record, rejoin from a computer browser and look again. If it appears there, the device was the cause, not your account.

3. Your role in the meeting

Who can record depends on whether you're the organizer or a co-host, and whether you belong to the same organization as the organizer. It also depends on how the host has set the meeting's host controls. If Record is visible but unavailable, or you see a message saying you aren't allowed to record, ask the host to start the recording, make you a co-host or change the recording setting. If a colleague in the host's organization can record the same meeting and you can't, the cause is your role, not your plan.

4. Organization policy

On a work or school account, a Google Workspace administrator can turn recording off for everyone or for some groups. If you're the host, on an eligible plan, on a computer, and Record still isn't there, your admin's policy is the most likely remaining cause. Only an administrator can confirm or change it.

5. Where the file went

Meet recordings are processed after the recording stops, and this can take a while for longer meetings. The finished file is usually saved to the meeting organizer's Google Drive, in a folder for Meet recordings, and a link is sent by email. That means the file may be in the organizer's Drive rather than yours if someone else organized the meeting. Before you decide the recording failed, check the organizer's Drive, the email notifications and the calendar event. Also check whether the Drive that stores the recording is full. A full Drive can stop the recording from being saved.

6. Missing video or audio inside the recording

The recording captures what was sent into the meeting. If your camera or microphone wasn't working in the call, it won't appear in the recording either. Check video and audio separately, because they fail independently. For each one, work out which of these three things went wrong:

• Detection: the operating system doesn't see the camera or microphone. Check the cable or connection and any physical privacy shutter or mute switch.
• Permission: the browser or operating system has blocked Meet from using the device. In the browser, check the site permissions for Meet. On macOS and Windows, also check the system privacy settings for camera and microphone.
• Selection: Meet has access but is using the wrong device, such as a built-in microphone instead of your headset. Check the device choices in Meet's audio and video settings.

To test, use Meet's preview screen before joining, or your own video tile during a call. Watch for the picture and for the microphone activity indicator. A good result shows the device works in Meet right now. It doesn't show that an earlier recording captured it. Also, cutting out your own audio or video doesn't stop the recording itself, so a recording with one silent participant usually points to that participant's devices.

What to change, and how to tell it worked

Finding | Change to make | How to confirm

Wrong account signed in | Rejoin the meeting with the account that has an eligible plan | The Record option appears in the meeting's activities or options menu

Joined from phone or tablet | Rejoin from a computer browser | Record becomes available on the computer

Not the host, or host has restricted recording | Ask the host to record, make you a co-host or change the recording setting | You can start recording and other participants see a recording notice

Admin policy blocks recording | Ask your Workspace administrator to review the Meet recording setting for your account or group | Record appears after the policy change takes effect, which may not be immediate

No file found | Wait for processing, then check the organizer's Drive, email and calendar event; free up Drive space if it's full | The file opens and plays from Drive

Recording has no video or audio | Fix detection, permission or selection for the affected device, then make a short test recording | The test file plays with picture and sound

Start with the changes you can easily undo: switching accounts, rejoining from a computer, choosing a different device, or allowing a permission you'd blocked. After each change, test the same thing that failed. If Record was missing, look for it again. If a file had no sound, make a short test recording and play it back from Drive. None of these steps call for driver, firmware or system resets, and nothing in this guide supports those for a recording problem.

When to escalate

Stop troubleshooting on your own and contact the right person in these cases:

• You've confirmed an eligible account, a computer, and host or co-host rights, and Record is still unavailable. On a work or school account, contact your Workspace administrator. On a personal paid plan, contact Google support.
• Recordings start but no file ever appears, even after a long wait and with free Drive space. Contact Google support or your administrator.