The Google Meet Transcript Exists and You Still Cannot Open It
You were in the meeting, the transcript was made, and Drive still shows you a Request access screen. Meet ties the transcript to the Calendar invite, cuts off meetings with more than 200 invitees, and leaves external guests out entirely. Here is each rule, and why the file came out in the wrong language.
A Google Meet transcript is not something Meet hands to everyone in the call. It is a Google Doc that lands in the organiser's Drive and gets attached to the meeting's Calendar event, so your access is decided by that attachment, not by the fact that you sat through the meeting. Three rules settle whether you can open it: whether you were invited from inside the host's organisation, how many people were on that invite, and whether your address is external. A fourth decides what language the file is in.
If the Transcribe control was never there in the first place, that is the other half of this problem: see Google Meet transcription button missing.
Why you cannot open it
- You attended but were not on the Calendar invite. Access follows the invite, not the attendance list.
- You are outside the host's organisation. Google's rule covers invitees inside it and stops there.
- The invite had more than 200 internal names on it. Above that, only three people get the file.
- You were invited through a group address. Group members still need access as individuals.
- You are looking in the wrong place. Since July 2026 the file also appears in Drive.
- You can open it, and it is in the wrong language. That is the host's Meet setting, not a bug.
The transcript is a Google Doc on the Calendar event
After a meeting with transcription on, Google emails a link to three people: "The host, Any co-hosts, The person who turned on Transcripts." The file itself is "saved in the meeting organizer's Google Drive in the 'Google Meet' folder", and it is attached to the meeting's Calendar event, where "All invitees in the host's organization can open the attachment" (Use transcripts with Google Meet, checked September 2026).
Two assumptions break here, and between them they explain most of the confusion.
Attending is not access. If someone forwarded you the Meet link, or you joined from the chat, you were never on the Calendar event, so the attachment is not yours to open.
Seeing the attachment is not access either. Google says this outright about the Gemini notes document, and the same mechanic applies to any Doc attached to an invite: "The ability to see the document attached to the calendar invite does not mean they have access to the document," and "If a group email is added, the members of the group still need to have individual access to the notes doc" (Take notes for me in Google Meet, checked September 2026). That is the screen you are looking at: the paperclip renders, the Doc does not open, Drive offers a Request access button. Requesting works, but it mails the organiser and waits. Asking them to share the Doc is the same action on their side, and usually faster.
More than 200 invitees, and three people get it
This is the rule almost nobody knows about, and it is the one that quietly kills all-hands and department meetings:
"If there are more than 200 invitees in the host's organization, the transcript is only available to the host, co-hosts, and the person who turned on Transcripts."
Read the wording carefully. It counts invitees in the host's organisation, not the people who showed up: a recurring invite with 250 names on it behaves this way even when twelve people join. There is no per-person override, so your only route is one of those three people.
External guests get nothing until the host shares the file
Google's access rule is written for invitees "in the host's organization." If your address is on another domain, the Calendar attachment does not open for you and no email arrives. Two things then have to go right: the organiser shares the Doc with your address, and their Workspace admin permits sharing files outside the organisation. A willing host inside a restrictive domain still cannot get the file to you, which is why "I will send it over" sometimes never arrives.
Gemini meeting notes at least ask the host to decide up front, between "All invited guests, including those outside of my organization", "Invited guests in my organization" and "Hosts and co-hosts only". Transcripts have no such chooser, so external access is always a manual share afterwards.
| You are | Attachment opens | What works | |
|---|---|---|---|
| Host, co-host, or whoever started transcription | Yes | Yes | Nothing needed |
| Invited from inside the host's organisation | No | Yes | Open the event, open the attachment |
| Inside the organisation, not on the invite | No | No | Ask to be added, or ask for the Doc |
| Invited through a group address | No | No | Ask for individual access |
| Any invitee, invite has 200+ internal names | No | No | Ask one of those three |
| External guest on another domain | No | No | Host shares the Drive file |
Check Drive before you chase anyone
Google changed where these files live in July 2026. Meet now uploads notes, transcripts and recordings into a Google Meet folder in My Drive, with a subfolder per meeting, and the old Meet Recordings folder became Legacy Meet Recordings. The part that matters to a participant: "Any meeting attendees with access to the meeting files will see shortcuts to these source files in their 'Google Meet' Drive folders too" (Google Workspace Updates, rollout from 22 July 2026, checked September 2026).
So look in Drive under Google Meet for a subfolder named after the meeting. A shortcut there means you had access all along and were searching your inbox for an email nobody sent you. Nothing there is also an answer.
Why the transcript came out in the wrong language
The meeting was in German, everyone spoke German, and the Doc is in English. The language is not detected from the audio: it follows the host. Google's admin documentation says so plainly: "These artifacts match the language that the host selected in their Meet recording settings. So if the host's Meet language is set to French, and automatic transcription is turned on in a meeting, the transcript will be in French" (Choose automatic meeting artifact settings, checked September 2026). A German meeting organised by a colleague whose Meet interface is English produces an English transcript until that colleague changes their own setting.
Two limits sit on top of that. Meet transcripts exist in eight languages only: "English, French, German, Italian, Japanese, Korean, Portuguese, Spanish", so a meeting in Dutch, Polish or Turkish produces none at all. And captions are a separate feature with a separate setting: each participant picks their own caption language under More options > Settings > Captions, captions are not written to a file, and changing yours has no effect on the transcript.
Meet writes the transcript while the call runs, so the language is settled before anyone joins. There is no re-run and no per-participant override. The fix is the host changing their Meet language setting before the next meeting.
What a participant can actually do
Ask for three specific things rather than "can you send the transcript": that the organiser shares the Doc from Drive with your address, that they check with their admin whether external sharing is allowed, and that they fix their Meet language setting before the next call.
The alternative is to stop depending on the organiser's Workspace. Kalima transcribes the audio your own computer is playing, so nothing joins the call and no extra name appears in the participant list. The transcript is created in your account from the first second, which retires the invite rule, the 200-invitee rule, the external-guest rule and the host-language rule at once.
In the browser, start a session, set the audio source to Desktop audio, add Include microphone if you want your own voice too, and press record. The browser asks what to share: pick the Google Meet tab and tick the share audio option, without which only video is shared and nothing is transcribed. In the desktop app, pick Desktop audio and start; it captures meeting audio natively, with no share dialog each time. Automatic meeting detection currently recognises Microsoft Teams calls only, so for Meet you start the recording yourself.
Language works the other way round here: Kalima detects what is spoken instead of reading a setting. It covers 60 languages, follows a conversation that moves between them inside one session, and marks each part of the transcript with a badge for that segment's language, so the German stays German and the English asides stay English. Live translation can render everything into one language, or run two-way between two.
Free is honest about its size: 2 hours of transcription a week and 45 minutes per live session, enough for stand-ups but not an all-day workshop. Longer sessions sit on the paid plans, listed on pricing. Exports are PDF, SRT, VTT and JSON.
Tell the other participants
A transcript running on your own device is not visible in Meet, so say that you are keeping one. Recording rules differ by country and many require everyone's consent; in Germany, § 201 StGB protects the non-publicly spoken word, and consent from all participants is the safe path. Your employer's policy and the meeting's terms apply too. One sentence at the start of the call is enough, and offering to share the notes afterwards usually turns the announcement into a favour.
Frequently asked questions
Why does Google Meet ask me to request access to a transcript from my own meeting?
Because the transcript is a Google Doc in the organiser's Drive, attached to the Calendar event, and you are not on the sharing list. Attending does not grant access, and neither does seeing the attachment. Click Request access, or ask the organiser to share the Doc.
Can an external guest get a Google Meet transcript?
Only if the host shares the Drive file and their Workspace admin allows sharing outside the organisation. Google's rule covers invitees inside the host's organisation, so external guests get no email and cannot open the attachment.
Why is my Google Meet transcript in English when everyone spoke German?
Because meeting artefacts follow the language the host picked in their own Meet settings, not the language in the room. Only the host can change it, and only for future meetings.
Do captions save a transcript?
No. Captions are live text for whoever turned them on, each participant chooses their own caption language, and nothing is written to a file. The transcript is a separate feature, started under Meeting tools > Transcribe.
Can I transcribe a Google Meet call without the host doing anything?
Yes, by capturing the audio on your own computer instead of using Meet's feature. Kalima records what your machine plays, so no permission in the host's Workspace applies. Tell the other participants you are doing it.
Related
- Google Meet transcription button missing: when the control is not there at all.
- Transcribe Google Meet in real time: the Meet workflow on your own device.
- Who can access the meeting transcript: the same question across Zoom, Teams, Meet, Webex and Slack.
- Multilingual meeting transcription: meetings where people switch language mid-sentence.
- Kalima pricing: session lengths and weekly minutes per plan.
Try Kalima on your next call.
Live transcription and translation, no bot in the meeting. Free to start.
Keep reading.
Your Company Blocked AI Notetakers. What You Can and Cannot Do Next
A blocked notetaker is either a switched-off transcription policy, a lobby that refused a bot, or a network that refuses the service itself. Only one of those is about something joining your call, and only one is a question you can answer without asking somebody first.
Can you record a job interview? Consent, state law and the AI Act question nobody answers
Five vendor blogs answer this with a state list and a consent form. None of them mention that a voice recording can trigger a biometric statute, none cover an EU employer interviewing a US candidate or the reverse, and none say what happens to the recording after the decision is made.
'99 % accurate' means nothing: how to read a transcription accuracy claim, and how to catch the errors that matter
Every transcription vendor publishes an accuracy percentage, and none of them mean the same thing by it. This is how word error rate is calculated, what it weighs equally that you do not, and a 20-minute test you can run on your own recordings.