Key Takeaways
The recording and the transcript are two separate things, and only the recording is reliable. Teams keeps it in the cloud: channel meetings in the channel’s SharePoint document library, everything else in the organiser’s OneDrive. Google Meet saves to the organiser’s Drive, in a folder made for meeting recordings. Zoom writes local recordings to the machine that ran the meeting, in a Zoom folder under the user’s documents, in a subfolder named for the meeting date and time. Download the file and transcribe it yourself and none of the platform’s rules apply any more.
People say “I recorded the meeting” and mean two different things. Sometimes they mean there is a video file sitting somewhere. Sometimes they mean the platform also produced a running text of the call. The first one nearly always happened. The second one depends on the platform, the account, and whether captions were on at the time.
So the job splits in two. Find the file, which is a matter of knowing where each platform puts it. Then get text out of it, which is either something the platform already did for you or something you do yourself from the downloaded file. The second route is slower to start and it works every time, which is why it’s worth knowing even when the first one is available.
Teams: the file is in the cloud, and which cloud depends on the meeting
A Teams recording is not on the laptop of whoever pressed record. It goes straight to the organisation’s cloud storage, and where it lands is decided by the kind of meeting it was.
If it was a channel meeting, the recording goes to that channel’s SharePoint document library, in among the channel’s other files. That is the friendlier outcome, because anyone with access to the channel has access to the recording without asking a person for it. If it was any other meeting, a scheduled invite or an ad hoc call, the recording goes to the organiser’s OneDrive. It belongs to that person’s storage. You may have a link to it from the meeting chat, and that link may still work, but the file itself lives in an account that isn’t yours.
This is worth knowing before you spend twenty minutes hunting. If you were an attendee at a scheduled meeting and the chat link is dead or you were never in the chat, the file is not somewhere you can search your way to. The person who set the meeting up has it, and the fix is to ask them, either for the file or for permission on it.
The other thing to know is that this arrangement is not permanent. Recordings sit under whatever retention policy the organisation has set, and when that window closes the file goes. If the recording matters to you, download a copy while you can see it. A downloaded copy is yours and stops being subject to anyone’s clock.
Google Meet: the organiser’s Drive, if the button was there at all
A Meet recording is saved to the organiser’s Google Drive, in a folder created specifically for meeting recordings. Same shape as Teams for non-channel meetings: it is one person’s storage, not a shared space, and access flows from that person sharing it or from an admin.
The wrinkle with Meet is upstream of all that. Recording is not available on every Workspace tier. That is why some people look for the record control, are told it should be under the menu with the other options, and find nothing there. They aren’t missing it. The account simply doesn’t have it. If you were on a call where nobody could record, there is no file to find and no transcript to recover, and no amount of searching Drive will change that.
If that’s your situation and the meeting mattered, the honest answer is that you reconstruct it from memory and from whatever anyone else wrote down, and you arrange your own recording next time so the file exists independently of the platform’s tier. A recording you made yourself is a file on your own device from the moment it stops, which sidesteps every question about whose Drive it went to.
Zoom: two different answers depending on how it recorded
Zoom is the one platform of the three where the file might genuinely be on a computer. A Zoom recording is either local or cloud, and the two behave nothing alike.
A local recording is written to the machine that ran the meeting. It goes under a Zoom folder in the user’s documents, and inside that there’s a subfolder named for the meeting date and time, which makes finding the right one straightforward once you know the pattern. If you hosted, it’s on your own machine and nobody can expire it out from under you. If someone else hosted, it’s on their machine, and it’s as safe as their machine is: still there if they kept it, gone if they wiped the laptop or never backed it up.
A cloud recording lives on the Zoom account instead, and behaves like the Teams and Meet cases. It’s tied to an account and to whatever retention the organisation applies. The practical difference between the two is who you have to ask. For a fuller walkthrough there’s a guide to where Zoom saves recordings.
Either way, the first move once you find it is the same. Get a copy of the file onto your own machine before you think about text.
What a platform transcript will and will not give you
All three platforms can produce their own transcript. When one exists and it’s readable, use it. There is no prize for redoing work the platform already did.
Know what you’re holding, though. A platform transcript is tied to the account and the retention policy in exactly the way the recording is. When the recording is deleted or an admin’s retention window closes, the transcript goes with it. They are not stored separately and finding one after the other is gone is not something you can usually arrange.
A platform transcript also covers what its own captions heard, and only that. It’s a single pass made live during the call. There is no second pass, so you cannot re-run it later at higher quality when it turns out the important five minutes came out as mush. And it typically will not include anyone who joined by phone in a way it could not attribute, which means the dial-in participant who asked the question that changed the decision may simply be absent from the record.
That last point catches people out most often. The transcript reads as complete. It has speakers, it has timestamps, it runs from the start of the call to the end. What it doesn’t do is announce the parts it missed.
Once the file is downloaded, the platform stops mattering
Download the video or audio and it becomes an ordinary file. From that moment, transcribing it is independent of the platform that made it. It doesn’t matter that the meeting was in Teams, or that the Zoom retention window is closing, or that the Meet recording sits in someone else’s Drive. Nothing about the file expires. You can transcribe it today, transcribe it again next year, transcribe it with something better when something better exists.
That’s the argument for treating this as the main route rather than the fallback. It has one extra step, the download, and in exchange it removes every dependency on someone else’s account, tier and policy.
Plenty of tools will take that file. SozAI is one of them: it runs on iOS, Android and macOS and takes audio or video files directly, producing text with speaker labels, a summary and translation across 99+ languages, and there’s more on turning a video file into text if the recording is a video rather than an audio export. Whatever you use, the thing that makes it work is having the file in hand.
What the text will actually be like, and who it belongs to
Set expectations before you read it. A transcript is only as good as the audio underneath it, and meeting audio is often poor: one person on a laptop microphone across a room, two people talking over each other, a dial-in with a hum. Nothing recovers words that were never clearly captured. If the file sounds bad to you, it will read badly.
Speaker labels help but they are a best guess. Crosstalk confuses them, and someone who speaks twice in a call may end up split across two labels or merged with a neighbour. A quick pass to correct names against the attendee list is usually worth the two minutes.
The larger thing is that a transcript is not an answer to “what did we decide”. It’s the raw material for one. Someone still has to read it and pull out the decisions, and if that’s the question you were asked, going from a wall of text to usable meeting notes is the step that actually finishes the job.
Finally, the recording of a work meeting is usually the property of the organisation that made it, and the rules on who may see it and where it may go are the organisation’s, not the platform’s. Downloading a copy to your own laptop does not change that. It makes the file more durable and more portable, and both of those are reasons to be careful about where it ends up next.
