Google Meet transcription: getting a usable record of the call

The transcript from Tuesday's call is sitting in Drive. It runs to nine thousand words. Somewhere inside it is the decision about the launch date, the person who agreed to talk to the vendor, and the thing that was dropped without anyone writing it down. Nobody has opened the file, and by Friday nobody will, because reading nine thousand words is a bigger job than asking in chat what was decided.

That is the actual problem with meeting transcription, and it is not a problem of accuracy. The recognition quality on a clear call is good enough. What fails is the step after the transcript exists. This article covers what the built in Google Meet feature does and does not do, how to check whether an account has it, and what has to happen to the text afterwards for the record to be worth having.

What the built in transcription covers

Google Meet has a Transcripts feature that produces an automated text record of what was said. Three limits are worth knowing before planning around it.

It is not available on every plan. According to Google's own support documentation, Transcripts are included in Business Standard, Business Plus, Enterprise Starter, Enterprise Standard, Enterprise Plus, Teaching and Learning Upgrade, Education Plus, and Workspace Individual. A personal Google account on the free tier is not on that list, and neither is Business Starter. For a team on the entry level business plan, transcription is a paid upgrade rather than a setting to switch on.

It runs on a limited set of devices. The documentation states that Transcripts can only be used on a computer, a laptop, or an Android device. Someone joining from an iPhone cannot start a transcript, which matters when the person who usually runs the meeting is on a phone.

It supports eight languages: English, French, German, Italian, Japanese, Korean, Portuguese and Spanish. A call conducted in a language outside that list will not produce a transcript from the built in feature, whatever the audio quality.

One further condition is easy to miss. Transcripts can only be recorded when there is enough space in both the organisation's Google Drive and the meeting host's Drive. A host near their storage limit is a host whose meetings quietly do not get transcribed, and the failure is not obvious at the time.

Turning it on, and where the file ends up

In a meeting, the control sits under Meeting tools at the bottom right, then Transcribe and Start transcription. A confirmation dialog follows, and once transcription is running an indicator appears at the top right for everyone in the call. Whether a participant can start it depends on host management. With host management off, anyone from the host's domain can start a transcript. With it on, only the host and co-hosts can.

Transcription can also be set to begin automatically. When creating the meeting, the option sits under Video call options, then Meeting records, then Transcribe the meeting. Google notes that these automatic features do not start until the host or a co-host joins on the web, which is a common reason a scheduled transcript turns out to be missing.

The output lands in the meeting organiser's Google Drive, in a folder named Google Meet, with a sub folder created for each meeting. Google has also stated that from July 2026 the existing Meet Recordings folder is renamed Legacy Meet Recordings and moved inside the new Google Meet folder, with older transcripts remaining available. Anyone with scripts, shortcuts or shared folder links pointing at the old path should expect to revisit them.

After the meeting ends, an email containing a link to the transcript goes to the host, any co-hosts, and the person who turned transcription on. The transcript is also attached to the meeting's Google Calendar event, where all invitees within the host's organisation can open it. There is one exception worth noting: if the host's organisation has more than 200 invitees on the event, the transcript is available only to the host, co-hosts, and whoever started it. Longer meetings also take longer to process, so the email does not arrive immediately.

What the feature deliberately leaves out

Several gaps are by design, and planning around them is easier than being surprised by them.

Only spoken words are captured. Google's documentation is explicit that chat messages are not in the transcript, and that capturing chat requires recording the meeting instead. On calls where links, numbers and corrections get typed rather than said, a large share of the substance is outside the transcript.

Transcription cannot be paused. It can be stopped and a new one started in the same meeting, and each start produces a separate file. A ninety minute call with two breaks therefore produces three files rather than one document, and somebody has to know that when looking for a particular exchange later.

Transcription stops automatically when all participants leave. That is helpful in the normal case and unhelpful in the case where the last two people stay on the call to settle something, since that part of the conversation is the part most likely to contain the decision.

There is also nothing in the transcript that tells a reader which lines mattered. The file is a sequence of speaker labels and sentences in the order they were spoken, with the digressions, the corrections and the repeated points at the same weight as the conclusion. Automatic note taking and summaries are a separate feature rather than something the transcript itself provides, so a team that turns Transcripts on and expects a short summary to appear will be disappointed by what lands in Drive.

Captions and transcripts are also different things. Captions appear live on screen for accessibility and translation, and the translated captions feature is listed by Google as available on a different set of editions from Transcripts. Turning on captions during a call does not produce a file afterwards.

Built in transcription against the alternatives

Approach	What it gives	What it costs
Built in Transcripts	Text file in the organiser's Drive, no extra vendor, no extra consent to manage, attached to the calendar event	Requires an eligible edition, eight languages, no chat, computer or Android only
Record the meeting	Video and audio including chat, useful when tone or a demo matters	Large files, slower to search, storage consumption, and reviewing it takes as long as the meeting did
Third party notetaker joining the call	Summaries, action item extraction, search across past meetings, integrations	A separate vendor holding meeting audio, a bot visible in the participant list, and its own consent and approval questions

The third row is where most teams end up if the built in transcript is not enough, and it is worth being precise about what is actually being bought. The gap being filled is rarely accuracy. It is the summary step, the extraction of who agreed to do what, and search across many meetings at once. Those are worth paying for if a team genuinely reads them. If the summaries go unread too, the second tool has added a vendor without removing the original problem.

Consent, access and who ends up holding the text

A transcript is a written record of what people said, which changes what a meeting is. Two controls are worth checking before transcription becomes routine.

Google describes an administrator setting that requires all participants to give explicit consent before features such as recording, transcription and automatic note taking are used. That setting is off by default and an administrator can turn it on. Separately, participants joining a meeting where the host has enabled automatic capture see an on screen warning.

Access is worth checking too. The transcript sits in the organiser's Drive and is attached to the calendar event, where any invitee in the host's organisation can open it. For a call that included candid discussion of a customer, a supplier or a colleague, "any invitee in the organisation" is a broader audience than people in the room usually assume.

The practical step is to decide, as a team, which meetings get transcribed at all. Regular working meetings where the point is a shared record are good candidates. One to one conversations, performance discussions and anything involving a third party's confidential information usually are not. Writing that rule down once takes ten minutes and prevents the awkward case where a transcript exists and somebody objects afterwards.

From transcript to something people act on

A transcript is raw material. The value comes out only if three things are pulled from it and put somewhere they will be seen again.

What was decided. Meetings settle things with phrases like "let us go with that for now", which read as ambiguous in a transcript and are unambiguous in the room. Marking the decisions is a job for somebody who was present, and it takes two or three minutes immediately after the call.

Who owns each item. Spoken language drops subjects constantly. When somebody says they will sort the vendor question out before Thursday, the transcript carries a speaker label, but the moment that line is summarised into "sort out the vendor question by Thursday" the owner has disappeared. Owners are the single most frequently lost element and the most expensive to lose.

Where the item now lives. A decision recorded only in a transcript in a Drive folder is invisible during the hours when people are choosing what to work on. Moving the three to six real outcomes onto the board or tracker the team already uses is the step that turns a meeting into work. A project management tool that carries the board, the schedule and the conversation in one place shortens that step, because the record and the work are not in separate systems.

The transcript is then what it should be: the searchable backup for the question "what exactly did they say about this", not the record everyone is expected to read.

Two small habits make that extraction cheap enough to keep doing. The first is to name the person who will do it before the meeting starts, because a task with no owner at the end of a call does not happen. The second is to do it in the last two minutes of the meeting rather than afterwards, while everyone is still present and can correct a wrong reading of what was agreed. Teams that push the step to later find that it competes with the next meeting and loses, which is how the habit dies within a fortnight of a promising start.

What to change first

Check which Workspace edition the account is on, because if it is not on the eligible list no amount of configuration will produce a transcript. If it is, turn transcription on for one recurring meeting only, and add a two minute step at the end of that call where the decisions, owners and dates get written onto the board rather than left in the file. If the board and the meeting record currently live in different systems, Pinateca keeps them together, which is what stops the transcript from being the only place the decision exists.

Q1. Does Google Meet transcription work on a free Google account?

No. Google's support documentation lists Transcripts as available on Business Standard, Business Plus, Enterprise Starter, Enterprise Standard, Enterprise Plus, Teaching and Learning Upgrade, Education Plus and Workspace Individual. A free personal account is not on that list, and neither is Business Starter, so a team on either of those needs a plan upgrade or a separate tool.

Q2. Where is the Google Meet transcript saved after the meeting?

In the meeting organiser's Google Drive, inside a folder called Google Meet, with a sub folder for each meeting. A link is also emailed to the host, co-hosts and whoever started transcription, and the transcript is attached to the meeting's Calendar event. Google has said that from July 2026 the older Meet Recordings folder is renamed Legacy Meet Recordings and moved inside the Google Meet folder.

Q3. Are chat messages included in the transcript?

No. Only spoken words are transcribed. Google's documentation states that capturing chat messages requires recording the meeting rather than transcribing it. On calls where links, figures and corrections are typed instead of spoken, a meaningful part of the content will be missing from the transcript alone.

Q4. Can transcription be started from a phone?

Not from an iPhone or iPad. Transcripts can be used on a computer, a laptop or an Android device, according to the feature documentation. If the person who normally runs a recurring meeting joins from an iPhone, either a co-host on a supported device starts it or the meeting is set to transcribe automatically when created.

Q5. Do participants have to be told that a meeting is being transcribed?

An indicator appears at the top right for everyone once transcription is running, and participants joining a meeting with automatic capture enabled see an on screen warning. Beyond that, an administrator can turn on a setting that requires explicit consent from all participants before transcription, recording or automatic note taking is used, and that setting is off by default. Legal obligations vary by country, so a team recording conversations regularly should confirm the position with the people responsible for compliance in the organisation.