Your meeting transcript didn't generate. Here's how to get it back

The meeting ended forty minutes ago. You opened Drive to grab the transcript for the follow-up email and it isn't there. Or it is there and the page is blank. Or you have a clean recording of the whole thing and no text at all, because the transcript toggle was never on.

One thing to know before you start looking: Google moved where all of this lives in July 2026, so a lot of the advice you'll find online points at a folder that no longer exists. Work down this list in order. Most people find the file in the first three steps.

Recovery paths, in order of likelihood

Look in the "Google Meet" folder, not "Meet Recordings." As of July 22, 2026 for rapid-release domains and July 30 for scheduled release, Meet writes recordings, transcripts, and notes into a folder called Google Meet in the host's My Drive, with a subfolder per meeting. Recurring meetings share one folder across instances. Your old files didn't vanish — Google renamed the "Meet Recordings" folder to "Legacy Meet Recordings" and moved it inside the new one. If you bookmarked the old folder, that bookmark now points somewhere different from where today's file landed.

Search Drive by content type instead of by name. Type type:document meeting or the meeting title into Drive search. Attendees now get shortcuts to meeting files in their own "Google Meet" folder, but shortcut creation depends on your access to the source file, so search catches cases the folder view misses.

Check the Meet homepage. meet.google.com now carries a hub that shows past meetings alongside their artifacts, specifically so you can find notes, recordings, and transcripts without digging through your inbox or Drive. Rapid-release domains got it July 21, 2026; scheduled release started August 17 and rolls out over roughly fifteen days. If your homepage still looks like the old one, you're in that window.

Work out whose Drive it actually went to. This is the step that solves the most cases, and it surprises people every time. Meet saves the transcript in the meeting organizer's Drive, not the Drive of whoever pressed the button. The email goes to the host, co-hosts, and the person who started transcription. Recordings behave the same way — the link email goes to the organizer and the person who started recording. For instant meetings this breaks down badly. One person described it plainly:

> if I am not the instant meeting host (and I can't always be), I can never see the transcription in my inbox or my drive unless it is forwarded to me by the host.

If you weren't the organizer, stop searching your own Drive and ask them.

Open the Calendar event. Gemini's notes document is automatically attached to the Google Calendar event and visible to internal invitees according to the organizer's sharing settings. People forget to look here constantly. The event is often the fastest route when Drive permissions are the thing standing in your way.

Treat notes and transcript as two separate files. "Take notes for me" produces a summary document. Transcripts are a different artifact with a different toggle. Having one does not mean you have the other, and an empty notes page does not mean the transcript failed. Check both before concluding anything.

On Zoom, go to the web portal, not the desktop app. Sign in at zoom.us, open Recordings in the left nav, click the meeting, and look for the file labelled Audio Transcript. The download button next to it gives you a .vtt file. One condition matters: transcripts are tied to cloud recordings. If you only made a local recording, there may be no separate downloadable transcript at all.

Know that the Zoom download is genuinely contested right now. Zoom's Hub — the file-sharing surface added to the desktop app and web in February 2026 — changed where people expect to find recordings and summaries, and a 20-reply community thread has users reporting the raw transcript download disappeared on July 22, 2026:

> Until yesterday, we had the option to download the raw transcripts from Zoom calls. Today, it has disappeared.

Zoom's community manager initially pointed people at the More (⋯) menu next to the transcript, the answer that has always worked. When users showed it wasn't there for them, the reply changed to an internal escalation with no timeline. Reddit threads say the same thing. Both accounts can be true — a staged rollout means the menu is present on some accounts and gone on others. Try the ⋯ menu. If it isn't there, don't assume you're doing it wrong.

If you have the recording but no transcript

This is the case Google has never solved. Meet's transcription happens at capture time only. There is no button anywhere that takes an existing recording and produces text from it, and people have been asking for one since 2023 in thread after thread after thread. The workaround one person landed on tells you how bad it is:

My only idea is to start a new meeting, play the recording on a shared screen and enable recording+transcript - seems cumbersome.

Another poster in that last thread noted the obvious comparison: "I know Microsoft Teams has the option to generate a transcript afterwards." Teams treats transcription as a post-processing job on the recorded file. Meet treats it as a live stream you either captured or didn't.

Your practical options, cheapest first:

Pull the audio out and send it to a transcription service. Download the MP4 from Drive, then strip the video. This gives you 16 kHz mono WAV, which is what most speech models want:

   ffmpeg -i meeting.mp4 -vn -acodec pcm_s16le -ar 16000 -ac 1 meeting.wav

Upload the WAV wherever you like. A one-hour file comes out around 110 MB, which is under most upload limits.

Run Whisper locally if the content shouldn't leave your machine. whisper meeting.wav --model medium on a laptop with a decent GPU handles an hour in a few minutes.

Use Team Meet's "Transcribe this recording" button. We built this because the gap is real and unfixed. Drop an existing recording in and it transcribes after the fact — no re-playing the meeting to a screen share.

Why it fails without telling you

Three mechanisms, all worth understanding so you can predict the failure instead of discovering it.

Capture-time transcription that produces nothing produces no error. If speech recognition never gets a usable stream, there is no moment where the system can say so. The meeting looks fine. You find out afterwards, when the file is empty or absent. One user described exactly this — the UI said it was transcribing and the result was an empty notes page. A separate thread reports the same for a full hour of conversation. Google's own documentation quietly explains part of it: notes are recommended for meetings of fifteen minutes or more, and the feature handles one language at a time. A short bilingual standup can produce nothing and report nothing.

Recording and transcription are separate switches. Turning one on does not turn the other on. Zoom has the same shape of problem — its community manager traced missing summaries to the meeting summary toggle needing to be on inside the live meeting, even for accounts with auto-start enabled org-wide. When the transcript is thin, Zoom returns a summary that isn't a summary:

A summary was not generated due to insufficient transcript.

The file lands in an account you can't see. Covered above, and it's the reason a lot of "missing" files aren't missing. We looked at 2,000 recent threads in the Google Meet community; 33 of them are about recordings not appearing in Drive. The titles say it all — "the meet recording still not show in My Drive", "Some recordings unavailable", "Where do I find my meeting recording". Some are propagation delay. Many are permissions.

One more, because it catches people who did everything right: transcripts don't work on iPhone or iPad. Google's documentation says the feature works on a computer, laptop, or Android device. If you hosted from an iPad, there was never going to be a transcript.

Stop it happening again

Be the organizer when you need the file, or confirm before the meeting who is.
Turn on recording and transcription. Two switches.
Watch for the transcript indicator in the first minute, not the last.
Don't host from an iPhone or iPad if you need text.
For Zoom, record to the cloud. Local recordings often produce no downloadable transcript.
Download the .vtt or Doc the same day you get it, rather than trusting it will stay where it is.

What we do differently

Team Meet runs transcription by default. There's no toggle to forget, because the failure mode we kept seeing wasn't broken speech recognition — it was a switch nobody pressed. The transcript appears in the side panel while the meeting is still running, so you can see words landing in real time. If nothing appears in the first thirty seconds, you know immediately, while you can still do something about it.

We also added the button Google hasn't: Transcribe this recording. Point it at a file you already have and it produces the text afterwards. That covers the meeting you recorded last month before you started thinking about any of this.

Two honest limits. In Chrome and Edge, transcription uses the browser's Web Speech API, which performs recognition on a remote server — your audio goes to Google, same as it would in Meet. In Safari and Firefox we run a Whisper model inside the tab, and the audio never leaves your machine, but that path is English-only for now. Pick your browser according to which limit you can live with.