Recording a Google Meet: editions, permissions and the missing button

The most common answer to how to record a Google Meet is that you can’t, and it has nothing to do with the buttons. Recording is an edition feature. If you’re on a free personal Google account, or on the entry Workspace tier, the option isn’t hidden somewhere in a menu, it isn’t there at all. That single fact accounts for most of the confusion, so it’s worth settling before the click path.

Which accounts can record

Recording is available on a subset of paid Google Workspace editions. Business Standard and above generally include it, along with the Enterprise tiers and several Education and Nonprofit editions. Business Starter does not, and neither does a free @gmail.com account.

Google’s support page on recording a video meeting carries the current edition list, and the lineup shifts often enough that it’s worth checking against the Workspace pricing page rather than trusting a blog post, this one included. If you’re on the wrong edition, no setting fixes it and the answer is an upgrade or a different tool.

Assuming you’re on an edition that supports it, two further gates apply. Your Workspace administrator has to have recording enabled for your organisational unit, and you have to be the meeting host, a co-host, or someone in the same organisation as the host. External guests can’t record, which surprises people running calls with clients.

How to record a Google Meet: the click path

In the meeting, open Activities (the icon at the bottom right), choose Recording, then Start recording, and confirm. Everyone in the call is notified that recording has started, including anyone who joins later. Stop it from the same panel, and it also stops on its own when everybody leaves.

Recording captures the active speaker and anything being presented. It doesn’t capture other windows, the chat panel in most configurations, or breakout rooms unless someone records inside them separately.

Where the file goes

The recording lands in the Google Drive of the meeting organiser, in a folder called Meet Recordings, and a link is emailed to both the organiser and the person who started the recording.

The organiser detail matters more than it sounds. If your colleague set up the meeting and you pressed record, the file belongs to their Drive, not yours, and it counts against their storage quota. When a recurring meeting was created by someone who has since left, recordings can end up in a suspended account, which is a slow problem to unpick.

Processing takes a while for long meetings, so the file often isn’t there the moment you stop. If it hasn’t appeared after a couple of hours for a long session, that’s still within normal.

Sharing follows ordinary Drive permissions, which means a recording is not automatically visible to attendees. Someone has to share it deliberately, and external sharing may be restricted by your admin’s Drive policy independent of the Meet settings.

Transcripts, which are usually what you wanted

Meet can produce a transcript separately from a recording, saved as a Google Doc in the organiser’s Drive, and on supported editions there are also meeting notes features that summarise. Google documents transcript behaviour and edition availability on its transcript support page.

For most working meetings the transcript is the more useful artefact. A 48-minute video answers “what did we agree” badly and slowly. A searchable document answers it immediately, takes almost no storage, and doesn’t need anyone to sit through it. If you only turn on one of the two, make it the transcript.

Speaker attribution depends on people joining under their own accounts. Conference-room hardware with several people around one microphone produces a transcript attributed to the room, which is close to useless for follow-ups.

Before you record anything

Consent rules depend on where the participants are, not where your company is registered. Meet’s on-screen notification tells people recording has begun, which is helpful and isn’t a substitute for consent everywhere, and it says nothing about what you’re then allowed to do with the file. Our notes on two-party consent states and recording calls set out where everyone in the call has to agree, and whether recording a video meeting is legal covers the general shape of it.

Say why you’re recording at the top of the call. It costs five seconds and it prevents the more awkward conversation later.

Host management, and who can actually press the button

Meet’s permissions changed when host management arrived, and a lot of older guidance predates it.

The organiser is host by default and can promote others to co-host, which grants recording rights along with the moderation controls. Co-hosts are worth setting up in advance for anything important, because a meeting where only one person can record is a meeting that goes unrecorded whenever that person’s connection drops.

Host management can also be switched off entirely, in which case everyone in the organisation gets host-level controls. Convenient for small teams, and worth thinking about for larger calls, since it means any internal participant can end the meeting for everyone.

A detail that catches people: if the organiser never joins, the meeting may have no host at all, and recording won’t be available to anyone in it. For a recurring call run by someone who rarely attends, transfer the calendar ownership rather than working around it every week.

Recording quality and the things that spoil it

Three practical points, none of which are in the documentation.

Recording captures the active speaker view, so a call where people talk over each other produces a recording that jumps around and is harder to follow than the live meeting was. Pinning a presenter before you start gives a steadier result for anything you intend people to watch later.

Shared screens are captured at the resolution they’re sent, not the resolution of your display. Someone presenting a dense spreadsheet from a large monitor often produces a recording where the text is unreadable, and you won’t notice until afterwards.

And a recording started two minutes late is missing the part where the meeting agreed what it was doing, which is usually the part worth keeping. If recording matters, start it before the small talk finishes rather than when the first agenda item begins.

When a recording is the wrong answer

Recording solves storage. It rarely solves the actual problem, which is that decisions made in the meeting need to exist somewhere findable afterwards.

Most meeting recordings are never watched again. They do reliably create a file that occupies someone’s Drive quota, sits inside your organisation’s retention and legal-hold scope, and needs deleting eventually. If what you wanted was the three decisions and who owns them, an hour of video is an expensive container for four sentences.

Craqly works the other way round. It runs as a desktop app, follows the call without joining as a bot in the participant list, and separates decisions and action items from the discussion while the meeting is happening, so what you keep is a page rather than a video. It behaves the same across Google Meet, Zoom and Teams, which matters when your customers are on one platform and your team is on another, and it doesn’t depend on your Workspace edition. The free Starter plan is 20 credits a month, one credit being a minute of live session, with credits resetting monthly. Paid plans start at $19 a month billed yearly, or $38 month to month, checked on 6 September 2026.

For turning that into something people read, see writing meeting minutes people actually read, and the agenda templates if the meeting itself is the thing that needs fixing.

If the recording option isn’t in your Activities panel, check your Workspace edition first. That’s the answer roughly nine times in ten, and no amount of looking through settings will change it.