It's the night before the exam, and the material isn't in your notes — it's scattered across nine weeks of recorded lectures you never had time to rewatch. Or you're the instructor, and a student has just asked whether you could "maybe put together a study guide" from six sessions you already ran live and don't have the hours to summarize again. Either way, the material already exists. It's just trapped in video form, one recording at a time.

Gemini Notebook — Google's tool for asking questions of and generating study material from your own documents, renamed from NotebookLM in July 2026 (same product, same URL, new name) — can turn a lecture into a study guide on demand. The catch is what it can actually read. This post covers the one step that has to happen first — getting a real, readable transcript into Drive — and then the two workflows built on top of it: a study guide from one lecture, and a study guide spanning a whole course.

What's actually happening

Zoom's own transcript is a .vtt caption file — a W3C-standardized format built for a video player's caption track, not for reading: every few seconds of speech is its own numbered cue with a start and end timestamp, and no paragraph breaks. Gemini Notebook's source picker doesn't accept a raw .vtt file, and a Zoom Cloud link won't reliably fare any better — it takes Google Docs, Slides, Sheets, PDFs, and a broad set of other file and web-source types, but a caption file isn't one of them. Google's own Gemini Notebook documentation covers what a notebook accepts as a source and what the Studio panel can generate from it.

The deep-dive on converting Zoom transcripts to Google Docs covers exactly what Zoom's raw file looks like and why it's a dead end for AI tools — this post picks up from there and assumes you're already convinced. Until the lecture's content exists as one of the file types Gemini Notebook actually reads, there's no study guide to generate.

How to fix it

1. Get the transcript into Drive as a clean Google Doc, not just the raw .vtt. RecordFlow uploads both automatically for every synced recording: the original .vtt untouched, and a native Google Doc with cue numbers stripped, consecutive lines from the same speaker merged into paragraphs, and each paragraph opening with a rounded [HH:MM:SS] timestamp and the speaker's name in bold. If you haven't set the backup itself up yet, the companion how-to on backing up Zoom recordings to Google Drive automatically covers the 60-second setup, and the deep-dive on converting Zoom transcripts to Google Docs covers exactly what changes in that conversion.
2. Open Gemini Notebook and add the transcript Doc as a source. In a new or existing notebook, choose "Add sources," pick Google Drive, and select the lecture's transcript Doc. RecordFlow names each meeting folder with the recording's date and the meeting topic, which is what lets you tell one week's lecture apart from another in the source picker.
3. Generate the study guide from the Studio panel. Choose the report option and pick "study guide" (alongside FAQ and briefing document as the other built-in report types) — Gemini Notebook grounds the output in the source you added and cites the part of the transcript each section comes from, so a claim in the guide traces back to the moment in the lecture that supports it.
4. For a whole course, add every session's transcript Doc to the same notebook first. A study guide generated from one notebook only reflects the sources sitting in it — the same principle behind turning a folder of transcripts into a queryable knowledge base. Add the transcript Docs for every lecture in the unit or term before generating the report, and the guide spans the whole course instead of a single session — useful for a final-exam guide that has to draw across nine weeks, not just the most recent one.

If the course is a recurring Zoom meeting, naming it with a shared prefix — BIO 201/Week 6 — lets RecordFlow collect every session's recording and transcript into one shared class folder automatically instead of a new folder each week, so building a term's worth of Gemini Notebook sources is adding one folder, not hunting down nine separate Docs. It's off by default and only applies to future syncs. Full mechanics.

Study guides are one workflow among several that open up once a lecture is in Drive — the ecosystem overview of Zoom recordings in Google Workspace covers what Docs, Gemini Notebook, and Vids can each do with the same archived recording.

What to check if something goes wrong

How RecordFlow fits

RecordFlow isn't the study tool here — Gemini Notebook is. RecordFlow's job stops one step earlier: sign in with Zoom, connect Drive, pick a folder — about 60 seconds — and from then on every lecture recording lands there automatically, transcript included as both the raw .vtt and a readable Google Doc, in a folder named by date and topic. RecordFlow never reads or summarizes what's in the transcript — it copies the file into a Drive folder you own and stops there; what Gemini Notebook builds from it after that runs on your own Google account. That combination — every session archived without anyone re-uploading anything, and transcribed into a document Gemini Notebook can actually read — is what makes "generate a study guide for the whole course" a five-minute task instead of a rewatch.

A client emails between sessions: "Can you send me Thursday's video? I want to check I'm doing the exercise right before I do it again tonight." You go looking. Maybe the recording already aged out under a retention setting you configured months ago and forgot about. Maybe it's sitting in a folder of forty files Zoom named "Zoom Meeting" and a date, with nothing to say which one was theirs. Either way, you're now explaining why the thing they actually need — not a memory of the session, the session itself — isn't there.

What's actually happening

In a lot of coaching relationships, a recording is a nice-to-have. In physical therapy, fitness coaching, and wellness/movement work, it's closer to load-bearing. A client doing home exercises between PT visits needs to check they're loading the joint the way you showed them, not the way they remember it three days later. A fitness client repeating a lift on their own wants to see their form next to yours, not guess. A wellness or movement client working through a multi-week protocol needs the actual sequence you walked them through, in order, not a paraphrase. The session isn't a record of work that already happened — it's a reference the client goes back to while doing the work.

That only holds up if two things are true: the recording still exists when they go looking for it, and they can actually find the right one. Zoom's cloud storage isn't built for either. Most paid plans pool a limited amount of storage across the whole account (full breakdown by plan), and account owners can turn on an automatic deletion setting that clears recordings after a set number of days — useful for housekeeping, quietly disastrous if a client's home-exercise reference disappears mid-program because someone (possibly a past you) turned it on and moved on. And a multi-week program generates a recording every session, all landing in the same undifferentiated pile unless the meeting titles say whose program they belong to.

Naming and finding sessions, program by program

Two habits do most of the work, and neither requires reorganizing anything after the fact:

1. Put the client or program in the Zoom meeting title, not just the date — with a slash if you want it grouped automatically. J. Torres — Knee Rehab Wk 4 already carries information a generic "Zoom Meeting" title doesn't, and that alone makes the recording easier to find later. Title it J. Torres — Knee Rehab/Week 4 instead — program name, then a slash, then the session — and it also sets you up for RecordFlow's grouping-by-series setting (below) to collect every session into one shared folder automatically, if and when you turn it on. Either way, fix the title once, at the point you schedule the session, and every later step inherits a name you can actually search.
2. Get consent before you record, every time — and say plainly what you'll do with it. This matters everywhere coaching happens over video, and it matters more here: a health, fitness, or wellness session can surface exactly the kind of personal detail a client wouldn't want circulating without their say-so. Ask up front, in plain language, and keep that consent current if what you do with the recording changes. (The consent walkthrough covers how to ask without making it feel like a legal formality.) To be direct about what this post is not claiming: it isn't a compliance guide, and RecordFlow doesn't offer or claim any particular health-data compliance standard. If your practice is subject to one, that review is yours to run — this is about the recording surviving long enough to be useful and being easy to find, nothing more.

If you're running the same multi-week program with a rotating or recurring cohort, the folder-organizing post for coaching recordings covers building a per-client view without moving anything RecordFlow already filed for you.

How RecordFlow fits

RecordFlow connects to Zoom and Google Drive once — a roughly 60-second setup — and from then on, the moment a Zoom cloud recording finishes processing, it copies the video, the audio-only file, the chat log, and the transcript into a Drive folder you own, named with the date and the session's title, grouped by year. Nothing to download by hand before a retention clock runs out, and nothing sitting on RecordFlow's own servers in between — the files move straight from Zoom to the Drive you control. (The setup walkthrough covers connecting it if you haven't yet.)

The transcript matters here too, past what a video alone gives you. Alongside the raw caption file, RecordFlow uploads a clean, speaker-labeled Google Doc transcript — so if a client asks "what did you say the rep count was for that one," the answer is a text search, not scrubbing through a video seeking bar looking for a moment you half-remember.

None of this requires a new workflow — it requires the meeting title to say whose program it is, consent to be asked before the call starts, and an archive that copies the recording somewhere durable before Zoom's own clock gets to it. Get those three right and the video is there the next time a client needs to check their form instead of guessing.

Zoom charges $1.50 for every gigabyte of cloud recording storage you add past a small tier. Amazon S3 charges $0.023. That is not a typo, and it is the arithmetic behind every "storage full" invoice that ever seemed high for a few dozen gigabytes of video.

Every list price below was checked against the vendor's own pricing page in the week this was published, and each one is linked — cloud prices move, and a cost comparison with a stale number in it is worse than no comparison at all.

What Zoom charges

Zoom publishes its add-on pricing on its cloud recording storage capacity page. The tiers, as listed there:

Two things about that table matter more than the headline numbers.

You buy a tier, not a gigabyte. There is nothing between 30 GB and 200 GB, so an archive that has grown to 50 GB costs $40, not $16.50 — the 30 GB tier no longer fits and the next one up is the only thing that does.

The overage rate is the punitive one. Spilling 20 GB past the 30 GB tier at $1.50/GB costs $30 a month on top of the $10 — more than simply buying the 200 GB tier. That is by design, and it is the number people discover on an invoice rather than in advance.

This is on top of your Zoom plan, which already includes a pooled allowance — 10 GB per licensed user on most paid plans, 15 GB on Business Plus, unlimited on Enterprise. The add-on is what you buy when that pool fills.

What object storage charges

The same gigabyte, at four S3-compatible providers. All figures are list price, storage line only, and I come back to what that omits below.

Against Zoom's cheapest published rate — $0.10/GB/month, reached at both the 1 TB and 5 TB tiers — S3 Standard is about four times cheaper and Glacier Instant Retrieval about twenty-five times cheaper. Against the rate a small account actually pays, the gap is an order of magnitude wider.

The same archive, priced five ways

Abstract per-gigabyte rates are easy to nod along to and hard to feel. So here is a real number, queried from our production database this week: across 334 accounts RecordFlow archives for, the mean archive is 46.2 GiB — about 50 GB as storage vendors count it. That is a working coach or trainer with a couple of years of sessions in it, not an outlier.

And at the top of our own range — the largest single archive we hold is just over 1,000 GiB, about 1,088 GB:

Those are ratios of roughly 35x (against S3 Standard) and 200x (against Glacier Instant Retrieval), on the same bytes, for an archive most people would describe as small.

What about the drive you already pay for?

For a lot of people the honest answer to "where should recordings live" is not a bucket at all. If you already pay for Google One, Microsoft 365 or Dropbox, or your employer pays for Google Workspace, you are already holding a couple of terabytes of storage that a recording archive barely dents — and the marginal cost of putting recordings there is genuinely zero until you fill it. Our Google Drive versus Zoom Cloud comparison works through that case, and the Microsoft 365 version does the same for OneDrive.

The reason to look at object storage instead is not that it is cheaper than a drive plan you already own. It is that a drive plan has a ceiling you periodically pay a vendor to raise, and object storage does not: it is priced per gigabyte, all the way up, with no plan to move to. If your archive is 40 GB and growing slowly, a consumer drive is the simpler and probably cheaper answer. If it is 400 GB and growing weekly, the per-gigabyte curve is where you want to be.

The part that actually lowers the bill

Here is what every version of this comparison gets wrong, including the ones that quote the numbers correctly.

Copying your recordings somewhere cheaper does not reduce your Zoom bill by a cent. A copy in S3 is a second copy. Zoom still holds the original, your pooled allowance is still full, and you are now paying for storage twice. You have made a backup, which is worth doing — but you have not made the bill smaller.

The bill only falls when recordings are archived and then removed from Zoom. That is the move that turns Zoom cloud storage from a permanent library, which you must keep buying, into a rolling buffer of the last few weeks, which you never have to buy again. The 50 GB in the table above stops being $40 a month of Zoom add-on and becomes $1.14 a month of S3 — but only if it leaves Zoom.

That is also the step people are right to be nervous about, because doing it by hand means deleting a recording on the strength of believing a copy exists somewhere. The safe version is mechanical, and it is the only order that works:

1. Copy the recording out, every file — video, audio, transcript, chat.
2. Verify it landed, by size, at the destination, not by assuming the upload returned successfully.
3. Only then remove it from Zoom, and leave a grace period before you do, so a bad day doesn't cost you a client's session.

The safe sequence for deleting a Zoom recording after backing it up walks through the manual version of that. RecordFlow copies and verifies every recording automatically; turn on its opt-in auto-delete toggle and it clears the Zoom copy the same way, only after the backup is confirmed at the right byte count, and it does not get distracted halfway through. Files stream straight from Zoom to the storage you choose — RecordFlow never holds a copy on its own infrastructure in between.

So what should you actually do?

• Archive is under ~100 GB and you already pay for a cloud drive. Put recordings there, turn on verified deletion from Zoom, and stop buying Zoom storage. The cost of the archive is zero on top of what you already spend.
• Archive is large or growing fast, or you are an admin covering a whole team. Object storage is where the per-gigabyte curve stops hurting. S3 Standard or R2 if you might read recordings back; a cold tier if this is a compliance archive nobody opens.
• You are on Zoom Enterprise with unlimited storage. The cost argument does not apply to you. The durability one still does — Zoom's maximum auto-delete retention is finite, and an unlimited pool that expires is not an archive.
• Whatever you pick, delete from Zoom afterwards. That is the step that changes the invoice.

Someone on your team is doing this right now: open Zoom, click into a recording, click Download, wait for a multi-gigabyte file to save, then open Drive or Dropbox and upload it back into the right client or project folder. Repeat for every recording, every week. It's usually a VA — a virtual assistant — or an office admin, and it's usually been the process since before anyone thought to question it.

It works — until the week your VA is out, swamped with something else, or moves on and isn't replaced right away. Zoom doesn't pause recording while that happens, and it doesn't pause its storage clock either. The recordings from that week are still sitting in your account, one storage cap or retention policy away from gone, and nobody finds out until someone goes looking for a specific one and it isn't there anymore.

What's actually happening

A manual backup process isn't really a process — it's a person, and it inherits every limit a person has. Downloading a Zoom cloud recording is a one-at-a-time action: open the recording's page, click Download, confirm the prompt, then repeat for the audio track, chat log, and transcript if you want those too. There's no bulk option in the Zoom web portal, so ten recordings in a week means ten separate click-throughs, and a bad connection or a large multi-hour file can make any one of them fail silently.

None of that is really the risk, though. The risk is what happens when the person doing it stops, even briefly. A VA who's out for a week, catching up on a backlog, or between contracts doesn't send you a notice that your backups have paused — the gap just accumulates behind them. Meanwhile Zoom keeps recording, and Zoom's side of the clock doesn't wait for anyone to catch up: storage quotas fill on their own schedule, and on accounts with an admin-set retention policy, recordings older than the policy window age out automatically regardless of whether anyone got around to downloading them first. Deleted recordings — whether removed by hand or by that retention policy — do sit in a 30-day trash window before they're gone for good, which is a real safety net, but only if someone notices in time and checks Trash. On accounts where an admin has separately turned Trash off entirely, any deletion skips that window and becomes permanent within about a day.

The failure mode that stings most isn't a recording that's obviously missing — it's the one nobody checks for until a client asks for it. A manual process has no alert for "this week didn't get backed up." It just quietly doesn't happen, and the first sign is usually someone asking for a session that turns out to no longer exist anywhere.

How to automate Zoom recording backups

The fix isn't a stricter checklist for whoever's doing the downloads — it's removing the human step entirely.

1. Connect Zoom to the cloud storage you already use. Google Drive, OneDrive, or Dropbox all work the same way: install from Zoom's own App Marketplace, sign in, authorize read access to recordings. About 60 seconds, and it's read-only on Zoom's side — nothing is deleted or changed there. From there, recordings stream directly from Zoom to the storage you chose; RecordFlow never stores or opens the files itself, only the encrypted access tokens needed to move them.
2. Pick the folder recordings should land in. From that point forward, every new recording — video, audio track, chat log, and transcript — copies itself into that folder automatically, usually within minutes of Zoom marking it ready. No one has to remember to do anything.
3. Backfill what your VA's manual process already missed. New-recording automation alone only starts from the day you connect it — it doesn't reach backward. If your team has been running a manual process for months or years, there's very likely a gap somewhere: a busy week, a stretch when the VA was out, a large file that silently failed. Widening the archive-history setting closes that gap by importing your account's existing recordings, going as far back as your full Zoom cloud history, the same reliable way it handles new ones.
4. If you run the Zoom account for the whole team, install it once at the account level instead of per person. An admin-managed install archives every enrolled member's recordings into one Drive you control, with a sub-folder per member — so the backup doesn't depend on each individual remembering to connect anything either.

That's the whole switch. The hours your VA was spending on downloads and re-uploads go back to work that isn't copy-paste — client follow-up, scheduling, whatever they were hired to actually do.

How RecordFlow fits

RecordFlow replaces the manual download-and-re-upload loop with the same chunked, verified transfer whether the account is one person or a whole team: connect once, and every recording since — plus, if you widen the archive-history setting, everything already sitting in the account — lands in the Google Drive, OneDrive, or Dropbox folder you choose, without anyone opening Zoom to click Download. Large files, multi-hour sessions, and password-protected recordings all transfer the same reliable way a short one does, and a failed chunk retries automatically instead of silently dropping the file — every recording moves on its own, at once, instead of one download at a time. For a team, the admin-managed install applies the same automation account-wide, one install instead of one VA keeping up with everyone's recordings by hand.

Zoom's "storage almost full" email lands, or your team gets the account-wide version of the same alert — and now there's a decision to make: where should these recordings actually go? RecordFlow's destination picker shows four options — Google Drive, Dropbox, OneDrive, YouTube — and there's no single best place to save Zoom recordings, only the right one for what you already run. Whether you're setting this up for the first time or rethinking it after that alert, the choice matters more than it looks: it decides what actually gets preserved, not just where it ends up.

The short version: three of the four are storage you own outright, and one is a publishing platform that only ever keeps the video. Which one is right depends less on features and more on what you already use, and what you actually need to keep.

What's actually happening

Google Drive, Dropbox, and OneDrive are what RecordFlow treats as container storage — a hierarchical place that accepts whatever bytes you send it, organized however you like. When RecordFlow archives a Zoom recording to any of the three, it copies the recording and its accompanying files: the video, the audio-only file, and — when Zoom generated one — the transcript (rendered as a Google Doc on Drive, a formatted Word document on Dropbox and OneDrive) and the meeting chat log. You control the folder, you can share it the way you already share files with clients or teammates, and nothing about those files changes in transit.

YouTube is a different kind of destination entirely — a media channel, not a file store. It accepts one thing: the video. There's no folder, no transcript, no chat log, because a video platform has nowhere to put them. YouTube also re-encodes every upload for playback — YouTube's own help documentation confirms it "always re-encodes videos to optimize their playback quality" — so what viewers watch isn't a byte-for-byte copy of the file Zoom produced, the way a Drive, Dropbox, or OneDrive copy is. RecordFlow uploads every video as Private. That's not a limitation to route around later; it's the right default for a recording of people who consented to being on the call, not to being published.

Zoom doesn't build any of these connections itself. Zoom's own developer guidance for moving cloud recordings to third-party storage points developers at building the integration on Zoom's API — webhooks and REST calls, not a setting Zoom ships. That's the gap RecordFlow closes for all four destinations, the same way, so the setup steps look nearly identical no matter which one you pick.

Google Drive vs Dropbox vs OneDrive vs YouTube for Zoom recordings

Current setup steps and account access live on each destination's guide above — check there for what's needed to connect.

Match the destination to what you already run

The fastest way to decide is to skip the feature comparison and ask what ecosystem the rest of your files already live in:

• Already on Google Workspace? Pick Drive. The recording lands next to every other document your practice or team already stores there — see how to back up Zoom recordings to Google Drive.
• Already on Microsoft 365? Pick OneDrive. Same reasoning — the recording joins the library where the rest of the team's files live instead of sitting off to the side in Zoom's cloud. Walkthrough: how to save Zoom recordings to OneDrive.
• Already sharing client files through Dropbox? Pick Dropbox — you're not adding a second storage habit on top of the one you already have. Walkthrough: how to save Zoom recordings to Dropbox.
• Running a class, cohort, or webinar series where students expect a replay? That's the one case none of the three storage options solve on their own — a Drive or OneDrive link isn't what a subscriber expects to find on the channel they already follow. See how to upload Zoom recordings to YouTube, and if the session involves anything confidential rather than a public class, read whether client recordings belong on YouTube at all first.

The tradeoffs worth knowing before you pick

A few honest details that don't show up until you're a few weeks into using one:

• Dropbox and OneDrive are app-folder scoped. RecordFlow requests permission to one dedicated folder — Apps/RecordFlow — inside your account, not your whole Dropbox or OneDrive. There's no folder picker for either, because the permission itself is what fixes the destination; RecordFlow genuinely cannot see or touch anything else in your account.
• Only Drive, Dropbox, and OneDrive keep the transcript and chat log. If a recording's value is partly in what was said and typed — not just the video — that alone probably settles the pick against YouTube.
• One destination at a time, today. A RecordFlow connection archives to Drive, Dropbox, OneDrive, or YouTube — not more than one simultaneously. Pick the one that matters most now; switching later from the dashboard doesn't touch anything already archived, it only changes where new recordings land going forward. If your workflow genuinely needs more than one destination at once — publishing to YouTube while also keeping a full archive, say — reach out through support and describe the use case; it's the kind of thing that shapes what RecordFlow builds next.

How RecordFlow fits

Every destination connects the same way: sign in with Zoom once, connect the destination you picked, done — about 60 seconds, no re-doing the setup per recording type. From then on, every new cloud recording, including passcode-protected sessions and multi-hour calls, transfers directly from Zoom to your chosen destination rather than sitting on RecordFlow's servers in between. Existing backlog doesn't have to be lost either — RecordFlow's archive-history setting can reach back into recordings from before you connected, on any of the three storage destinations. If you outgrow your first pick, switching destinations is a setting change, not a migration project.

An instructor teaching the same Tuesday cohort every week does the same manual chore after every single session: find last week's shared folder, or share a brand-new one, then post the link somewhere students will actually see it. Multiply that by every recurring class your academy runs, and it stops being one instructor's rounding error. It becomes a standing operational task nobody assigned to anyone — repeated every week, for every class, for the life of the program.

What's actually happening

Zoom has no concept of a recurring class as a single object. Even a recurring meeting — the closest thing Zoom offers — treats every occurrence as its own separate cloud recording, with its own share link and its own expiration clock. There's no built-in "this is week 6 of the same series" grouping a student — or an admin archiving on their behalf — can rely on. That's manageable for a single instructor tracking their own one class. It breaks down the moment an academy runs the same pattern across a full faculty roster: each instructor either has to reinvent their own naming and re-sharing habit, or the job falls to whoever's turn it is to remember.

The result shows up in two different ways depending on who's asking. A student who missed week 4 has to ask the instructor for a link, because there's no one place that always holds "this class's recordings." And for the academy or IT department archiving centrally, Zoom's recording storage is one pool shared across every host on the account — grouping by class isn't something Zoom's own storage model does for you; it's purely a filing problem that lands on whoever's doing the archiving.

How RecordFlow files every class into its own folder

RecordFlow's admin-managed app already archives every enrolled instructor's Zoom recordings into a Google Drive folder your institution controls, one sub-folder per instructor (see archiving across a multi-instructor academy). What's new is automatic class-level grouping inside that archive: recordings for the same recurring class collect into one shared folder per class, instead of landing as separate same-looking session folders an instructor has to hunt through.

Here's the mechanism, so it's clear what does and doesn't need to change on your end:

1. The instructor sets the Zoom meeting topic once, with a "/" separating the class name from the session title — for example Intro to Statistics — Fall 2026/Week 6: Regression. Nothing else about how they run the class changes.
2. RecordFlow reads everything before that first "/" as the class name and files that session into a folder named after it, nested under the instructor's year folder in your archive — so Intro to Statistics — Fall 2026 becomes one folder, and every week's session for that class lands inside it automatically.
3. The instructor (or the archive owner) shares that one class folder with students once, at the start of the term. Every subsequent session drops into a folder students already have access to — nothing to re-share, nothing to hand off week to week. As with any shared archive, let students know up front that the class folder is where sessions land — the same onboarding line covers it.
4. A new academic term starts a fresh class folder, because the class folder sits under the year folder rather than above it — so a Spring section's folder, and its sharing grants, are never inherited by the Fall section that reuses the same class name.

This applies to sessions synced from the point the feature is turned on — it doesn't reorganize anything already archived, so nothing already shared with students under an old folder name moves or breaks. And it's specific to folder-based destinations: a Google Drive, OneDrive, or Dropbox archive can hold a class folder, but a YouTube destination has no folder structure to group into, so this doesn't apply there.

If renaming meetings isn't realistic, there's a second rule. Asking every instructor to put a "/" in every meeting topic is a habit change, and habit changes leak. RecordFlow can instead recognise the class from the recurring Zoom meeting itself, so a recurring meeting called Intro to Statistics — Fall 2026 files its sessions into a folder of that name with nobody renaming anything. The trade-off is that it only covers meetings Zoom itself records as recurring — a session an instructor schedules by hand each week is a series to them and a string of unrelated one-offs to Zoom. When you turn the feature on you see both rules previewed against your own archive — how many sessions each would group, into how many folders — and pick whichever fits how your instructors actually work. The user guide covers both in full.

What to check if a session lands in the wrong place

How RecordFlow fits

Class-level folder grouping is available today as an early-access feature on RecordFlow's admin-managed app — contact support to have it turned on for your Drive, OneDrive, or Dropbox archive. Once it's on, instructors don't change how they run a class: either they put the class name before a "/" when they set the meeting topic, or — if their classes are already scheduled as recurring Zoom meetings — they change nothing at all. From there, RecordFlow's existing sync — video, audio, chat log, and a clean Google Doc transcript for every session — lands in the right class folder automatically, on top of the same per-instructor archive institutions already run (see Zoom recording storage for universities and colleges).

Tuesday's class finishes, the recording lands on your YouTube channel a few minutes later, and it's marked Private — meaning nobody, not even the cohort who just paid for the session, can watch it yet. That's not a bug and it isn't stuck. It's the one deliberate pause between "recorded" and "published," and clearing it takes about four clicks once you know where to look.

What's actually happening

RecordFlow uploads every recording to your channel as Private, and that default isn't configurable — not a setting you can flip to skip the step. The people on a Zoom call consented to being recorded, not to being published on a channel with an audience, so a course-creator automation shouldn't quietly make that call on their behalf. Publishing is a decision you make per session, with the context only you have (is this cohort paying for replay access, or is this a trailer meant to bring in new students?), so it stays yours to make in YouTube Studio, not baked into the upload.

Once a video is sitting in your channel, YouTube gives you three visibility states to choose from, and the definitions matter more than they look:

Private vs. Unlisted vs. Public

• Private — "can only be seen by you and whomever you choose." Won't show up on your channel page or in search. This is where every RecordFlow upload starts.
• Unlisted — "can be seen and shared by anyone with the link," and the viewer doesn't need a Google account to watch it. It won't appear on your channel's Videos tab or in YouTube search results either — normally the link is the only way in (one exception below).
• Public — visible to anyone on YouTube, discoverable in search and on your channel.

(Source: Change video privacy settings, YouTube Help.)

For a paying cohort, Unlisted is usually the fit: drop the link into your course platform or a weekly email, and a student who's never touched YouTube before can click straight through with no sign-in prompt.

Public makes sense when the recording itself is the marketing — a free workshop replay or a course trailer you want to be found.

Private is where a recording should stay if it's genuinely not meant for anyone but you — which, for a class replay, is rare, but worth remembering when a session veers into something more personal than the rest of the series.

How to change a recording's visibility

1. Sign in to YouTube Studio with the Google account connected to the channel RecordFlow uploads to.
2. Click Content in the left sidebar — every video on the channel is listed here, RecordFlow's uploads included, each showing its current visibility.
3. Find the recording (RecordFlow titles it with the session name and date, so a term's worth of classes sorts the way an actual course list would) and click the down-arrow under Visibility next to it.
4. Choose Unlisted or Public, then click Save. It's a metadata change, not a new upload — no reprocessing wait like the original video went through.

Do this once per session as each class wraps, or batch it weekly from the Content list if you'd rather publish a term's worth of replays on a fixed schedule.

What to check before you publish

How RecordFlow fits

RecordFlow's job stops at the upload: connect your Zoom account to your YouTube channel once, and every new class or session recording lands there automatically, titled and dated, Private by default. Everything after that — Unlisted for the cohort, Public for a trailer, or left Private because a session isn't meant for wider viewing — is a decision you make in YouTube Studio, session by session, with full context RecordFlow doesn't have and shouldn't guess at. YouTube only ever receives the video itself; if you also want the audio track, chat log, and transcript preserved, a connected Drive course library keeps the rest of the session archived alongside the channel upload — YouTube is where students watch the replay, not where the full session record lives.

If your practice or your team runs on Dropbox instead of Google Workspace, your Zoom recordings have had nowhere automatic to go — until now. Dropbox is a fully available RecordFlow destination as of today, alongside Google Drive: pick it on the connect screen, nothing to request or wait for, and about 60 seconds to connect.

What shipped: Zoom recordings, backed up to Dropbox

Connect Zoom and Dropbox, and RecordFlow copies everything Zoom generates for a cloud recording — video, audio-only file, transcript, and chat log — into a dedicated Apps/RecordFlow folder in your Dropbox, organized by year and meeting. If Zoom produced a transcript, RecordFlow also renders it as a formatted Word (.docx) document with speaker labels and timestamps, dropped in alongside the recording, instead of leaving you with a raw .vtt file.

Dropbox's own Zoom connection already does something adjacent — it copies new recordings into Dropbox once you switch it on in Settings → the Apps tab. What it can't do is reach backward: it only ever catches recordings from the moment you enable it, so a backlog built up before that point stays exactly where it was, and the original recording still sits in Zoom's cloud storage either way.

RecordFlow's archive-history setting closes that backfill gap — widen it in Settings and RecordFlow reaches into your existing Dropbox-bound library too, streaming even large files in chunks so a multi-year backlog moves as reliably as a single meeting. Freeing up Zoom's own storage afterward is a separate, opt-in step you control, not something either connection does automatically.

Getting started

You'll need a paid Zoom plan with cloud recording enabled — cloud recording isn't available on free plans, and local-only recordings never leave the machine they were saved on. On the Dropbox side, either a personal account or a Dropbox Business member account works.

1. Confirm cloud recording is on in Zoom Settings → Recording. Local-only recordings never reach a cloud-based automation.
2. Install RecordFlow from the Zoom App Marketplace — one-click OAuth, no password sharing.
3. Connect Dropbox and pick it as your destination. RecordFlow requests Dropbox's app-folder scope, so there's no folder picker — it creates and writes to Apps/RecordFlow and genuinely can't see anything else in your Dropbox.
4. Set your archive-history depth in Settings if you want existing recordings backfilled, not just new ones going forward. A new connection starts on the past month by default.

Full walkthrough with screenshots: how to save Zoom recordings to Dropbox automatically.

What to check if a recording doesn't arrive

How RecordFlow fits

This is the same archiving pipeline that's backed up Zoom recordings to Google Drive since launch, now pointed at a second destination. Every recording — new or backfilled — transfers directly from Zoom to your Dropbox rather than sitting on RecordFlow's servers in between, retries automatically if a transfer fails partway through, and gets caught by an hourly safety sweep even if a webhook notification is missed. Setup is about 60 seconds, and it's free during beta.

A student messages you Thursday: "Is Tuesday's replay up yet? I want to rewatch the Q&A part before the assignment's due." You know the recording exists — Zoom finished processing it days ago — but "up" where? Your students don't have Zoom accounts, don't want one, and definitely don't want to dig through a flat list of "Cohort Call" entries hoping one matches. They think in terms of a channel they can subscribe to and a playlist they can scrub through, the way they watch everything else.

What's actually happening

Zoom Cloud has no concept of a course library. Every session you record is a standalone entry in a flat list — no module numbers, no playlist, nothing that reads as "Week 4 of 10" instead of a timestamp. Zoom's own developer guidance for moving recordings anywhere outside Zoom points at building the connection yourself against Zoom's API — there's no native YouTube publish button, and no native "make this a browsable series" option either.

Even once a recording lands on YouTube, "browsable" and "private" pull in opposite directions, and the platform is explicit about which one wins by default. A video you upload isn't automatically part of any collection — a YouTube playlist is something you or a viewer builds by hand, video by video, it doesn't happen from an upload alone. And an unverified channel can't even accept a full-length class in the first place: without phone verification, YouTube caps uploads at 15 minutes — a single lecture or workshop routinely runs longer. Verify the channel once (YouTube Studio → Settings → Channel → Feature eligibility) and the ceiling jumps to 256 GB or 12 hours, whichever comes first, so this is a one-time setup step, not a recurring wall.

How to build the replay library

Steps 1–5 are one-time setup — done once per instructor, channel, or cohort. Step 6 is the only one that repeats: a 30-second click each time a new class finishes uploading.

1. Turn on cloud recording for every instructor who teaches a session, not just the account owner — Zoom Settings → Recording & Transcript, Cloud recording toggled on per host. A guest instructor recording locally to their own laptop is invisible to any backup automation, so this is the step that quietly loses a session mid-term if it's skipped.
2. Verify your YouTube channel once, before connecting anything. YouTube Studio → Settings → Channel → Feature eligibility → complete phone verification. This removes the 15-minute cap so your first automated class upload doesn't bounce.
3. Connect Zoom and YouTube — about 60 seconds. Go to recordflow.org/sign-in, sign in with Zoom, then connect the Google account that owns your channel. Once connected, every class recording uploads to that channel automatically, titled <session name> — <date> from the Zoom meeting's own topic — so put the cohort and module in the topic (Fall 2026 — Module 03 — Pricing) and the title on YouTube reads the same way.
4. Know what "uploaded" means before a student asks for the link. Every video RecordFlow uploads lands Private — the people on the call consented to being recorded, not to being published, so nothing goes out to a public or even semi-public audience automatically. That's the correct default, and it's also the one manual step standing between "recorded" and "replay library."
5. Make one playlist per cohort, once. In YouTube Studio, create a playlist (Fall 2026 Cohort) and set the playlist itself to Unlisted so it doesn't show up on your channel's public Videos tab. This is a native, free YouTube feature — anybody can create and share a playlist, no special access needed.
6. Flip each session's video to Unlisted and add it to that playlist, right after it uploads. Unlisted videos can be seen and shared by anyone with the link, and viewers don't need a Google Account to watch — the same no-login experience your students already get from a shared Drive or OneDrive folder. This step matters even after step 5: a private video stays unviewable to everyone but you no matter what playlist it's sitting in — playlist visibility and video visibility are two separate settings, and both need to say Unlisted for a student to actually press play.
7. Share the playlist link once, at kickoff or in your course platform's module page. From then on, each new class you connect and record adds itself to the channel automatically — the only recurring manual step is the 30 seconds it takes to switch a fresh upload from Private to Unlisted and drop it in the playlist.

What to check if a replay doesn't show up

Where the archive fits — and where it doesn't

A replay library and a client archive are two different jobs, and it's worth being precise about which recordings belong in which. Publish to YouTube: a live class, a cohort call, a webinar — anything the enrolled group already expects to rewatch together. Keep out of YouTube entirely, even Unlisted: a confidential 1:1 coaching or therapy session, or anything covered by a professional confidentiality obligation — we've written the straight answer on why Unlisted isn't the same thing as private storage for that case specifically.

How RecordFlow fits

RecordFlow's job is the automatic half of this: connect Zoom and YouTube once, and every class or cohort session uploads to your channel within minutes of Zoom finishing processing — titled and dated from the Zoom meeting topic, landing Private so publishing is always your decision, never an automatic one. The one YouTube Studio step that turns a private upload feed into an actual student-facing library — flipping a session to Unlisted and dropping it in the cohort playlist — stays exactly that: a 30-second click per session, not a re-upload. And because YouTube only ever gets the video, connecting a storage destination alongside it keeps the audio-only file, chat log, and a clean transcript archived too — the replay is what students watch; the archive is everything else from the session, kept in storage you control.

A comment lands under last week's upload: "Is Tuesday's replay up yet?" You've published every class to the channel for a month straight — but this week's session is still sitting in Zoom's cloud, because "download it, then re-upload it" is the first thing that slips when the week gets busy. For a course, cohort, or webinar series, the replay isn't a courtesy; it's the thing students expect to find waiting on the channel they already subscribed to.

What's actually happening

Zoom has no built-in YouTube destination. Zoom's own developer guidance for moving cloud recordings anywhere outside Zoom points developers at building the connection yourself on Zoom's API — there's no setting to flip on. So "publish to YouTube" defaults to a manual loop: log into Zoom, download the recording, log into YouTube Studio, upload, wait for processing, repeat next week.

Two things about that manual loop are worth knowing before you fight them for the tenth time:

• An unverified channel caps uploads at 15 minutes. YouTube's help center is explicit: without phone verification, "you can only upload videos that are 15 minutes or shorter." (Upload videos longer than 15 minutes) A single class or webinar almost always runs longer, so this is usually the first wall a new channel hits — verify the channel once and it's gone for good. A verified channel's ceiling is generous by comparison: up to 256 GB or 12 hours, whichever comes first.
• Every upload gets scanned and re-encoded. "When a video is uploaded to YouTube, it's automatically scanned by Content ID" (How Content ID works) — that description is triggered by the upload itself, with no carve-out for Private or Unlisted visibility. And YouTube "always re-encodes videos to optimize their playback quality" regardless of the source file (Video and audio formatting specifications) — the copy that ends up on the channel isn't byte-for-byte what you uploaded. Neither of these is a reason to avoid YouTube; they're just facts worth knowing about what "uploaded" actually means there. (If you're weighing whether a specific confidential session belongs on YouTube at all — a 1:1 rather than a class replay — we've written the straight answer on that separately.)

There's also a channel-level daily cap, though YouTube doesn't publish an exact number for it — its own uploading-errors page says only that it limits "how many videos a channel can upload in a 24-hour period," and that the "limits may vary by country/region or channel history." (Common uploading errors) None of these limits are exotic, but clearing the channel-verification wall and re-doing the upload flow every week is exactly the kind of repeated manual step that's easy to automate away.

How to upload Zoom recordings to YouTube automatically

1. Verify cloud recording is on. In Zoom Settings → Recording, Cloud recording should be toggled on. If Zoom is only saving locally, no cloud-based automation can see the file to upload it.
2. Verify your YouTube channel, once. In YouTube Studio → Settings → Channel → Feature eligibility, complete phone verification if you haven't already. This is what removes the 15-minute cap — do it before connecting anything, so your first automated upload doesn't bounce.
3. Connect the automation to Zoom. Install RecordFlow's Zoom App from the Zoom App Marketplace — a one-click OAuth install that only asks for read access to cloud recordings.
4. Connect your YouTube channel. Sign in with the Google account that owns the channel and grant access. RecordFlow requests upload access, plus the narrow read permission it needs to find your channel and avoid uploading the same recording twice — nothing else: no reading your existing videos' analytics, no deleting or editing anything already on the channel, no changes to channel settings.
5. Record your next class or session to the cloud. Once Zoom finishes processing, RecordFlow uploads the video to your channel automatically, titled <session name> — <date> so a term's worth of sessions sorts and reads like an actual course list instead of a pile of identical "Zoom Meeting" entries.

Every upload lands Private by default, and that's deliberate rather than a limitation to work around later: the people on that call consented to being recorded, not to being published on a public channel, so RecordFlow doesn't make that call for you. Switching a specific session to Unlisted or Public afterward — sharing it with a cohort, or opening it up publicly — is a decision you make per video, on your own terms, in YouTube Studio.

One more thing worth planning around: YouTube only ever gets the video. The audio-only file, the chat log, and the transcript Zoom generates don't have anywhere to go on a video-hosting platform, so if you want those preserved too, connect a storage destination alongside YouTube — an OneDrive course library (or a Google Drive one if that's your stack) is built for exactly that. YouTube is where students watch the replay; the archive is where everything else from the session lives.

What to check if an upload doesn't arrive

How RecordFlow fits

RecordFlow closes the manual step between a Zoom recording finishing and it showing up on your channel: connect Zoom, connect YouTube once, and every class or webinar recording after that uploads automatically — titled and dated, no re-downloading a file just to re-upload it an hour later. Every video lands Private by default, so nothing goes out to viewers without you deciding it should; publishing a specific session is still your call, made where it belongs, in YouTube Studio.

If your team runs on Dropbox instead of Google Workspace or Microsoft 365, every Zoom recording is still stuck in Zoom's own storage — racing the same quota as everyone else's, in a cloud you didn't choose. Dropbox does have its own Zoom connection, tucked away in Settings → Connected apps. It's easy to miss, and even once it's on, it only ever reaches forward.

RecordFlow's Dropbox destination is now generally available — no waitlist, nothing to request.

What's actually happening

Dropbox's own "Copy Zoom cloud recordings to Dropbox" feature — documented on Dropbox's help site — watches for new cloud recordings and copies them into your Dropbox once you turn it on in Connected apps. Three things about it matter more than whether it's switched on:

• It's go-forward only. It starts catching recordings from the moment you enable it. Anything already sitting in your Zoom cloud storage — a year of client calls, a semester of class recordings — stays exactly where it is.
• It's all-or-nothing. There's no way to pick which recordings come over or route different meeting types to different folders; every cloud recording either gets copied or none do.
• It doesn't free Zoom's storage. The recording gets copied to Dropbox, but the original stays in Zoom's cloud, still counted against your plan's quota. Copying to Dropbox doesn't buy you back any Zoom storage on its own.

Its exact status has flip-flopped over the past couple of years, so if the built-in copy has stopped working for you at some point, you're not imagining it — but whatever its current state, none of that changes the three limits above. On Zoom's own side there's no first-party Dropbox export at all: the connection has only ever lived inside Dropbox, and Zoom's developer guidance for moving cloud recordings to third-party storage points developers at building it themselves on its API — the same path RecordFlow takes.

For a Dropbox-native consultant or small team, that combination is an awkward gap: the backlog you most want protected — months or years of client sessions — is exactly what the built-in copy can't reach, and even the recordings it does catch keep taking up room in Zoom.

What you need

1. A paid Zoom plan (Pro, Business, Business Plus, or Enterprise) — cloud recording is disabled on free plans.
2. Cloud recording turned on in your Zoom account settings.
3. A Dropbox account, personal or a Dropbox Business member account.
4. An automation that runs reliably on large recordings and password-protected calls, and can reach back into your existing backlog — RecordFlow is built for exactly this.

On Google Workspace or Microsoft 365 instead? The steps are the same, aimed at a different destination — see how to back up Zoom recordings to Google Drive or how to save Zoom recordings to OneDrive.

How to save Zoom recordings to Dropbox

1. Verify cloud recording is on. In Zoom Settings → Recording, Cloud recording should be toggled on. Without this, Zoom saves recordings to the local machine instead, and no cloud-based automation — RecordFlow included — can see them.
2. Connect the automation to Zoom. Install RecordFlow's Zoom App from the Zoom App Marketplace — a one-click OAuth install. Zoom asks you to authorize read access to cloud recordings; you're never sharing your password.
3. Connect Dropbox. Sign in with your Dropbox account and grant access. RecordFlow requests Dropbox's app-folder scope, which creates one dedicated folder — Apps/RecordFlow — inside your Dropbox. There's no folder picker because the permission itself fixes the destination: RecordFlow can read and write inside that one folder and genuinely cannot see or touch anything else in your Dropbox.
4. Record your next meeting to the cloud. Once Zoom finishes processing the recording — a few minutes for a typical one-hour call, longer for multi-hour sessions — RecordFlow copies the video, the audio-only file, any transcript, and the chat log Zoom generated into your Apps/RecordFlow folder, organized by year and meeting. If Zoom generated a transcript, RecordFlow also renders it as a formatted Word (.docx) document, with speaker labels and timestamps, dropped in alongside the recording.

Already have months or years of recordings sitting in Zoom's cloud from before you connected anything? That's the gap Dropbox's own connected app can't close — it only ever catches what's recorded after it's turned on. RecordFlow's archive-history setting reaches back into your existing backlog too, and you decide how far. It starts at the past month, included free, so a new connection doesn't dump years of video into your Dropbox on day one. Reaching further back — 6 months, 2 years, or your full 10-year history — is a one-time paid unlock; once it's on, widening triggers a backfill of everything newly in range, streaming even large files to Dropbox in chunks so a multi-year backlog moves as reliably as a single meeting.

What to check if a recording doesn't arrive

How RecordFlow fits

RecordFlow closes both gaps Dropbox's own connected app leaves open: it backs up every new recording automatically, the same way, and it can also reach backward into whatever you already have sitting in Zoom — something a go-forward-only connection was never built to do. Sign in with Zoom, connect Dropbox, done — about 60 seconds. From then on, every cloud recording lands in your Apps/RecordFlow folder within minutes of Zoom marking it ready, including passcode-protected sessions and multi-hour calls, transferred directly from Zoom to your Dropbox rather than stored on RecordFlow's servers in between, and any Zoom transcript arrives as a Word document instead of a raw .vtt file. If a transfer fails it retries automatically, and an hourly safety sweep catches anything a webhook notification missed. Once your recordings are safely archived, freeing up Zoom's storage is a separate, opt-in step you control — not something that happens as a side effect of the copy itself.

A student pings you two weeks into a new term: "Where's the recording from Tuesday's cohort call? I had a scheduling conflict." Your syllabus, your slides, your worksheets — everything else in the course — already lives in OneDrive; the one thing your students actually rewatch doesn't. You open Zoom's recordings list looking for it, and every entry reads some variant of "Cohort Call" with a timestamp — no module numbers, no way to tell which session is Tuesday's without opening each one and scrubbing to the intro.

What's actually happening

Zoom Cloud is built around a single meeting, not a growing library. Every session you record adds a file against your account's cloud storage — 10 GB per licensed host on Zoom Pro or Business, pooled at the account level. A weekly one-hour call for an eight-to-twelve-week cohort can chew through a meaningful slice of that pool before the term wraps — faster if you run office hours alongside the main session, or teach more than one cohort in parallel. Once the pool is full, Zoom stops saving new cloud recordings for the account, which mid-term means the risk isn't losing an old file, it's failing to capture this week's live call at all.

There's a second problem that shows up the moment a student tries to watch instead of you trying to store. If your account has authentication enabled for viewing cloud recordings turned on, a Zoom share link demands a Zoom login before it plays — and a student who enrolled through your course platform, not through Zoom, often doesn't have one and doesn't want to create one just to watch a replay.

Underneath both is the same gap: Zoom doesn't ship a OneDrive connector for cloud recordings. Zoom's own developer guidance on moving recordings to third-party storage points at building the connection yourself on Zoom's API — webhooks and REST calls, not a setting you flip on. So the recordings sit in Zoom's cloud, disconnected from the OneDrive library everything else in the course already lives in, racing the same storage cap as everyone else's, with no concept of "Module 3 of a 10-module course" — just a flat list of meeting titles and dates.

How to build a course video library in OneDrive

1. Turn on cloud recording for every instructor who teaches a session, not just the account owner — Zoom Settings → Recording, Cloud recording toggled on per host. Cloud recording needs a paid Zoom plan (Pro, Business, Business Plus, or Enterprise) — it's off entirely on free accounts, so a guest instructor on a Basic plan can't produce a cloud copy no matter what's toggled. A co-facilitator recording locally to their own laptop is invisible to any backup automation, and invisible to you the moment their machine is unavailable. Say once, at enrollment, that live sessions are recorded — most course terms of service already cover this, and it's worth a line in yours if not.
2. Put the cohort and module number in each Zoom session's meeting topic, separated by a slash. Title the meeting Fall 2026/Module 03 — Pricing (cohort name before the slash, then module number, always two digits). RecordFlow names each session's OneDrive folder from the recording's date plus that topic, so 2026-08-18-1400-Fall 2026_Module 03 — Pricing reads the way a student thinks about the course, filed under a folder for the year the session ran — not the way Zoom's flat meeting list does. The slash matters beyond readability: it's what step 4 below uses to group every module into one shared cohort folder.
3. Connect Zoom and OneDrive. Go to recordflow.org/sign-in, sign in with Zoom, then connect your Microsoft account. RecordFlow's Microsoft permission is scoped to a single app folder, so it automatically creates one dedicated Apps/RecordFlow folder and can read and write only inside it — there's no folder to pick, one less setup decision. (This targets a personal OneDrive or a work/school account's own default drive — a shared SharePoint document library isn't supported.)
4. Turn on Group recordings by series in Settings. With it on, RecordFlow turns the cohort prefix from step 2 into an actual per-cohort folder: every module sharing that exact prefix collects in one place automatically, instead of sitting loose as separate dated subfolders under the year folder. It's off by default — see the linked docs for how to turn it on — and it only applies to sessions synced after it's turned on, not anything already archived.
5. Share the class folder with students directly, not a Zoom link. Turn on OneDrive's "Anyone with the link" sharing option on the cohort folder from step 4 — it opens without a Microsoft or Zoom sign-in, the same way a student already opens a shared doc elsewhere on your course platform. Share it once at kickoff and every future module for that cohort appears inside it automatically. Running several cohorts through the same account, share each one's class folder individually so one cohort's students aren't looking at another cohort's replays. On a school or work tenant, an admin can disable "Anyone" links account-wide, which is worth checking before you promise students a no-login replay.
6. Already have a term or two of past classes sitting in Zoom from before you connected anything? RecordFlow's archive-history setting reaches back into your existing backlog, not just what's recorded going forward. It starts at the past month by default, and you can widen it in Settings whenever you're ready — widening triggers a backfill of everything newly in range, streaming even large files to OneDrive in chunks so a semester's backlog moves as reliably as a single class.

What to check if a session recording goes missing

How RecordFlow fits

RecordFlow connects Zoom to OneDrive once — about 60 seconds — and from then on, every live session lands in your Apps/RecordFlow folder within minutes of Zoom finishing processing: the video, the audio-only file, the chat log, and if Zoom generated a transcript, a formatted Word document with speaker labels and timestamps, so a student can search a class instead of scrubbing an hour of video to find the five minutes on pricing that mattered. Each folder is named from the date and your meeting topic and filed under the year the session ran, so a term's worth of classes reads like an actual course archive, sitting in the same OneDrive your syllabus and slides already live in — not a separate storage location for the one asset students actually come back to.

If a term or two of past sessions are still sitting in Zoom's cloud, widening archive history backfills them into the same library instead of leaving them behind, using the same chunked, verified-before-anything-else transfer that handles a fresh class. And if your program runs on Google Workspace instead of Microsoft 365, the same pattern — automatic backup, one archive per account, topic-driven folder names — applies directly to a Drive course library.

The "cloud recording storage is almost full" email lands. If you're a Microsoft 365 shop, the instinct is to look for the OneDrive setting that already backs everything else up — SharePoint, Teams files, OneDrive sync on every laptop. Zoom doesn't have one. The recordings filling that pool sit entirely outside the Microsoft 365 library the rest of your files live in, and the only levers Zoom hands you are "delete something" or "pay for more room" — neither of which gets a single file into OneDrive.

What's actually happening

Zoom's cloud recording storage is a separate, capped pool — 10 GB per licensed user on Pro, Pro Plus, and Business plans, pooled at the account level (15 GB on Business Plus, unlimited on Enterprise tiers). It has nothing to do with your Microsoft 365 storage — Zoom doesn't read from or write to OneDrive, SharePoint, or any Microsoft Graph API on its own. Zoom's own developer guidance on getting cloud recordings into third-party storage points at building the connection yourself on Zoom's API — there's no setting to flip.

That gap matters more for an M365 shop than a generic one. Your team's files, search, and permissions already live in SharePoint and OneDrive; a Zoom recording that's never copied out sits invisible to all of it — not indexed, not searchable from the same place, not backed up by whatever retention policy already covers the rest of your Microsoft 365 tenant. Zoom warns at 80% of the pool and blocks new cloud recordings once it's full — for everyone on the account, not just whoever filled it — and buying Zoom's storage add-on only raises that same ceiling. It doesn't get anything into OneDrive; it just delays the next "almost full" email.

A quick note on scope: Zoom recordings can currently be archived to a personal OneDrive or the default drive on a work/school Microsoft 365 account — a shared SharePoint document library isn't a supported destination. So if your team's convention is "everything important lives in a shared SharePoint site," today's fix lands recordings in OneDrive first, not directly in that site.

How to fix it: auto-archive to OneDrive instead of paying for more Zoom room

The durable fix isn't a bigger Zoom pool — it's getting every recording out of Zoom and into OneDrive automatically, the moment it's ready, so the pool never climbs toward the cap in the first place. The full OneDrive setup walkthrough covers this end to end, including the archive-history setting for backfilling months or years of existing recordings; here's the short version:

1. Confirm cloud recording is on. Zoom Settings → Recording → Cloud recording should be toggled on — off, and recordings save locally instead, invisible to any cloud automation.
2. Connect RecordFlow to Zoom and OneDrive. RecordFlow installs from the Zoom App Marketplace as a one-click OAuth app (read access to recordings, never your password), then connects to your Microsoft account via an app-folder-scoped permission — it creates and confines RecordFlow to one dedicated Apps/RecordFlow folder inside your OneDrive, and genuinely can't see or touch anything else there.
3. Record your next session to the cloud. Once Zoom finishes processing, RecordFlow copies the video, audio-only file, chat log, and any transcript into that OneDrive folder — the transcript arrives as a formatted Word (.docx) document with speaker labels and timestamps, not a raw .vtt file.

Once a backup is confirmed, you can clear the Zoom copy safely — the back-up → verify → delete sequence works the same whether the backup landed in Google Drive or OneDrive, and the delete step is opt-in and never runs ahead of a verified copy.

What to check if a recording doesn't arrive

How RecordFlow fits

RecordFlow closes the exact gap Zoom leaves open for a Microsoft 365 shop: sign in with Zoom, connect OneDrive, done — about 60 seconds, no Power Automate flow to build or maintain, free during beta. Every cloud recording lands in your Apps/RecordFlow folder within minutes of Zoom marking it ready, transcripts included as Word documents, and a failed transfer retries automatically with an hourly safety sweep behind it. RecordFlow never stores your recordings on its own infrastructure — files stream directly from Zoom to your OneDrive. The pool stays small because recordings leave it continuously, not because you keep paying Zoom to make room for more.

When the OneDrive plan has a ceiling too

Moving recordings to OneDrive fixes the Zoom pool, and for most Microsoft 365 shops the terabyte per user that comes with the licence swallows a recording archive without anyone noticing. If yours is the case where it doesn't — a heavy recorder, a shared archive, or a tenant already tight on storage — then you have swapped one plan ceiling for another, and the option worth knowing about is storage priced per gigabyte with no ceiling at all. What Zoom recording storage actually costs puts Zoom's add-on rates, consumer drive plans and object storage side by side with the list prices checked.

You just finished a 1:1 Zoom session, the client asked for the recording, and YouTube is sitting right there — free, familiar, and it already knows how to host a video. Set it to "Private," share the link, done in two minutes — except "Private" on YouTube doesn't mean what you'd assume, and for a confidential coaching or therapy session, that gap matters. The reasons come straight from YouTube's own policies, not speculation.

What "Private" on YouTube actually means

Three things are true about a YouTube upload that most people don't check before relying on one:

The Terms of Service license doesn't carve out private uploads. When you upload to YouTube, you grant YouTube "a worldwide, non-exclusive, royalty-free, sublicensable and transferable license to use that Content (including to reproduce, distribute, prepare derivative works, display and perform it)" in connection with the service and YouTube's business — and that grant applies to whatever you "provide to the Service," full stop, with no separate clause for Private or Unlisted visibility. That's a platform-wide license, not a hosting arrangement, and it's the same license whether the video is public or seen by nobody but you. After you delete a video, YouTube's terms say the license continues for "a commercially reasonable period of time," and YouTube "may retain, but not display, distribute, or perform, server copies" of removed videos — deletion isn't instant erasure. (YouTube Terms of Service)

Content ID scans videos at upload, not at "made public." YouTube's own explanation is direct: "When a video is uploaded to YouTube, it's automatically scanned by Content ID." That description is triggered by the upload itself, not by a separate "made public" step — YouTube's Content ID documentation simply doesn't carve out Private or Unlisted uploads as exempt, and creators routinely report Content ID matches on videos they never made public. A recording that includes a Spotify playlist in the background or a clip from a paid course can get matched by the rights holder's system before you've decided who, if anyone, gets to see it. (How Content ID works)

Your file doesn't stay your file. "YouTube always re-encodes videos to optimize their playback quality," regardless of what you upload — meaning the file you sent isn't the file that gets served back. If a client ever needs the original video — for a records request, a professional-body audit, or just to open it outside YouTube's player — what's sitting on YouTube isn't it. (Video and audio formatting specifications)

There's a fourth data point worth knowing even if you'd never touch the YouTube API yourself: Google's own developer policy defaults new integrations to the same caution. "All videos uploaded via the videos.insert endpoint from unverified API projects created after 28 July 2020 will be restricted to private viewing mode" until that integration passes a compliance audit. (YouTube Data API — Videos: insert) Even Google, building automation on top of its own platform, treats "private by default until verified" as the safe posture. That instinct is worth borrowing for anything that touches a client's confidential recording.

The straight answer

None of this makes YouTube unsafe to use — it makes YouTube the wrong tool for one specific job. The line that matters isn't "public vs. private," it's what the recording is for:

• Publish on YouTube: a course trailer, a marketing testimonial, a public workshop replay, anything you'd be comfortable seeing resurface somewhere unexpected years later.
• Keep out of YouTube entirely: a confidential 1:1 coaching or therapy session, anything covered by a professional confidentiality obligation, anything a client shared expecting it to stay between the two of you.

Consent to record a session and consent to publish it are two different permissions, and a client who agreed to be recorded for their own reference didn't agree to have that recording live on a platform with a standing content license and automated scanning. The safer default for confidential work is storage you control outright — a Google Drive folder shared only with that client — where the file that lands there is the exact file you uploaded, nobody else's license touches it, and access is a permission you can revoke, not a platform setting you're trusting to hold.

Where RecordFlow fits

RecordFlow's job is the other half of this decision: making "storage you control" the easy option instead of the extra step. Connect your Zoom account to a Google Drive folder once, and every cloud recording — video, audio-only track, chat log, and a clean transcript Doc — lands in a dated subfolder automatically, the moment Zoom finishes processing. The files move directly from Zoom to your Drive; RecordFlow doesn't hold a copy on its own servers. Sharing a session with one client afterward is the same three clicks as any Drive file: right-click the folder → Share → "Anyone with the link can view" → copy URL — the same consent-aware handoff described for coaching deliverables applies here, whether or not you ever put a single frame on YouTube.

You need a Word copy of a Zoom transcript — to send a client a written record of the session, paste key lines into a report, or just have something you can search and edit without opening a video. You download the transcript from Zoom's web portal, open the file, and find a wall of sequence numbers and timestamps with your sentences chopped into fragments between them. That's not a document. It's a captioning file, and turning it into something you'd actually hand someone takes real cleanup.

What's actually happening

Zoom's cloud recording can generate an audio transcript for a meeting — a setting you (or your account admin) turn on under the account, group, or personal Recording settings, in the Advanced cloud recording section as "Create audio transcript." Once it's on, Zoom transcribes the spoken audio for that meeting and, per Zoom's own documentation, "appears as a separate VTT file in the list of recorded meetings." Two things about that are easy to miss: the setting only applies going forward — it can't be turned on retroactively for a meeting you already recorded — and it requires cloud recording to be enabled for that meeting in the first place, since the transcript is generated from the cloud copy.

The format itself is WebVTT, a W3C standard built to drive closed captions in a video player, not to be read on its own. A real Zoom transcript looks like this:

WEBVTT

1
00:00:03.120 --> 00:00:06.480
Priya Anand: The main thing I want to flag before

2
00:00:06.480 --> 00:00:09.760
Priya Anand: we get into the budget numbers is

3
00:00:09.760 --> 00:00:11.200
David Klein: Sure, go ahead.

Every three-to-five seconds of speech is its own numbered cue with its own timestamp range. A single sentence routinely spans two or three cues. Word will open a .vtt fine — it's plain text — but what you'll see is exactly this structure, not a readable transcript.

How to convert it by hand

If you're doing this manually, the steps are:

1. Download the .vtt from Zoom. In the web portal, go to Recordings and Transcripts, open the meeting, and find Audio Transcript in the list of files. Click Download and it saves to your computer as a .vtt file.
2. Open it as plain text. Most word processors, including Word, will open a .vtt directly, or you can rename the extension to .txt first.
3. Strip the cue numbers and timestamp lines. This is the tedious part — either delete every sequence-number and --> timestamp line by hand, or run a find-and-replace pass to remove them. For a 10-minute call that's a few dozen lines; for a full hour it's several hundred.
4. Merge the fragments and clean up speaker labels. Once the cue lines are gone, you're left with one line per fragment, still broken mid-sentence. Combine consecutive lines from the same speaker into paragraphs, and reformat the speaker name however you want it to read — bold, a colon, a new paragraph, whatever your document style calls for.

None of this is hard, but it doesn't scale. One transcript is an annoying ten minutes. A full week of client sessions is an afternoon you don't have.

How RecordFlow fits

If your RecordFlow archive is on OneDrive or Dropbox, every synced recording gets a real .docx transcript, rendered directly — no Google Doc step, no download-and-convert. It's built the same way you'd clean one up by hand: a heading, the meeting date, a speakers list, then one paragraph per cue with a rounded [HH:MM:SS] timestamp and the speaker's name bolded, cue numbers and fragment breaks already gone. It lands next to the video and the raw .vtt every time a recording syncs, and the transfer goes straight from Zoom to your own OneDrive or Dropbox — RecordFlow doesn't keep a copy anywhere in between. If your archive is on Google Drive instead, you get the same clean transcript as a native Google Doc, which downloads to .docx in two clicks from Drive — see the companion guide on getting Zoom transcripts into Google Doc and AI tools for that path.

If your team lives in Microsoft 365, every Zoom recording is sitting outside the OneDrive library the rest of your files live in — racing the same storage cap as everyone else's. There's no official Zoom-to-OneDrive connector to fix that: search "save Zoom recordings to OneDrive" and page one is a mix of university IT help-desk PDFs and generic no-code automation templates, because the automatic transfers some organizations built for themselves a few years ago mostly aren't running anymore.

What's actually happening

Zoom doesn't ship a OneDrive connector for cloud recordings. Zoom's own developer guidance on moving cloud recordings to third-party storage points developers at building the connection yourself on Zoom's API — webhooks and REST calls, not a setting you flip on.

A number of IT departments closed that gap themselves a few years back, usually with a scheduled Power Automate flow that watched a Zoom folder and copied files into OneDrive. Several of those flows have since been retired — Chapman University's IT department documented shutting theirs down in 2023, a maintenance burden common to DIY flows built on top of Zoom's API. Without one running, recordings just accumulate in Zoom's cloud storage until the account's quota fills or a retention policy clears them out.

For a Microsoft 365 shop, that's an awkward place for a recording library to live. The recording sits in Zoom's storage instead of the OneDrive or SharePoint library where the rest of the team's files already are, isn't indexed alongside them, and is exactly as exposed to Zoom's storage cap as anyone else's.

What you need

1. A paid Zoom plan (Pro, Business, Business Plus, or Enterprise) — cloud recording is disabled on free plans.
2. Cloud recording turned on in your Zoom account settings.
3. A Microsoft OneDrive account — personal or the default drive on a work/school (Microsoft 365) account.
4. An automation that runs reliably on large recordings and password-protected calls — RecordFlow is built for exactly this workflow.

On Google Workspace instead of Microsoft 365? The steps below are the same, aimed at Drive instead — see How to Automatically Back Up Zoom Recordings to Google Drive.

How to save Zoom recordings to OneDrive

1. Verify cloud recording is on. In Zoom Settings → Recording, Cloud recording should be toggled on. Without this, Zoom saves recordings to the local machine instead, and no cloud-based automation — RecordFlow included — can see them.
2. Connect the automation to Zoom. Install RecordFlow's Zoom App from the Zoom App Marketplace — a one-click OAuth install. Zoom asks you to authorize read access to cloud recordings; you're never sharing your password.
3. Connect OneDrive. Sign in with your Microsoft account and grant access. RecordFlow requests Microsoft's app-folder-scoped permission, which creates one dedicated folder — Apps/RecordFlow — inside your OneDrive. There's no folder picker because the permission itself fixes the destination: RecordFlow can read and write inside that one folder and genuinely cannot see or touch anything else in your OneDrive. (v1 targets a personal OneDrive or a work/school account's own default drive — a shared SharePoint document library isn't supported.)
4. Record your next meeting to the cloud. Once Zoom finishes processing the recording — a few minutes for a typical one-hour call, longer for multi-hour sessions — RecordFlow copies the video, the audio-only file, any transcript, and the chat log Zoom generated into your Apps/RecordFlow folder, organized by year and meeting. If Zoom generated a transcript, RecordFlow also renders it as a formatted Word (.docx) document, with speaker labels and timestamps, dropped in alongside the recording.

Already have months or years of recordings sitting in Zoom's cloud from before you connected anything? A go-forward automation like a Power Automate flow only ever catches what's recorded after it's turned on — RecordFlow's archive-history setting reaches back into your existing backlog too, and you decide how far. It starts at the past month, included free, so a new connection doesn't dump a decade of video into your OneDrive on day one. Reaching further back — 6 months, 2 years, or your full 10-year history — is a one-time paid unlock; once it's on, widening triggers a backfill of everything newly in range, streaming even large files to OneDrive in chunks so a multi-year backlog moves as reliably as a single meeting.

What to check if a recording doesn't arrive

How RecordFlow fits

RecordFlow closes the gap Zoom leaves open: sign in with Zoom, connect OneDrive, done — about 60 seconds, no Power Automate flow to build or maintain. From then on, every cloud recording lands in your Apps/RecordFlow folder within minutes of Zoom marking it ready, including passcode-protected sessions and multi-hour calls, and any Zoom transcript arrives as a Word document instead of a raw .vtt file. If a transfer fails it retries automatically, and an hourly safety sweep catches anything a webhook notification missed — so the backup doesn't quietly depend on one script someone wrote once and forgot about.

If your organization runs on Microsoft 365, the "Zoom storage almost full" email lands differently than it does for everyone else. You're not choosing between "pay Zoom for an add-on" and "find somewhere else to put these recordings" — you're already paying for a terabyte of OneDrive storage per person that's probably half empty. Recording every meeting into Zoom Cloud and then paying Zoom again for more room is asking the budget to cover the same problem twice.

This post is the honest Zoom Cloud vs OneDrive comparison for teams and Microsoft-365 shops already on a paid Zoom plan. Same four questions as any storage decision: cost, retention, sharing, and where the archive actually needs to live.

If you're on Google Workspace instead, the Google Drive vs Zoom Cloud comparison covers the same ground for that side of the world.

There's no official Zoom-to-OneDrive integration

Worth clearing up before anything else: Zoom doesn't ship a native feature that copies cloud recordings into OneDrive. Zoom's own developer guidance for getting recordings into third-party storage is to build on the recording-completed webhook and the recording API yourself — listen for the notification, download the file, upload it wherever it needs to go. If you remember an automated Zoom-to-OneDrive flow from a few years back, it was almost certainly a homegrown Power Automate script, not a Zoom product, and several of those were retired when their owners moved on. Zoom Workplace (the current name for Zoom's desktop client) records to Zoom Cloud; getting a copy into OneDrive is on you, one way or another.

What Zoom Cloud storage actually costs

Zoom's cloud recording storage is pooled at the account level and capped by plan — most paid plans include 10 GB per licensed user, shared by everyone who records. Once that pool fills, Zoom blocks new cloud recordings until someone frees space or the account buys more. The cheapest published Zoom storage add-on is roughly $10 a month for 30 GB, and the per-gigabyte rate only gets meaningfully better once you're committing to a full terabyte — most solo practitioners and small teams never buy that much.

OneDrive storage, on the other hand, usually isn't a separate purchase at all. Microsoft 365 Business Basic and Business Standard both include 1 TB of OneDrive storage per user, bundled into a subscription most teams already have for email and Office apps. A solo practitioner on Microsoft 365 Personal gets 1 TB on its own for about $9.99 a month; Microsoft 365 Family stretches that to up to 6 TB (1 TB per person) for about $12.99 a month across up to six people.

That 1 TB is per person, not pooled the way Zoom's storage is — each OneDrive is its own allocation, not a shared bucket the whole account draws from. For a solo practitioner archiving into their own account, that's still headroom Zoom's add-on can't match. For a team, what matters is the single OneDrive the archive actually lands in: RecordFlow's admin-managed app connects one Zoom account admin's OneDrive as the archive root, with a sub-folder per member, so it's that one person's 1 TB doing the work, not the sum of everyone's individual quotas. Even counted that way, one person's largely-unused terabyte comfortably outlasts a shared 10 GB Zoom pool split across ten licenses — and upgrading that one OneDrive is cheaper than paying Zoom's per-GB add-on for the whole account.

Does OneDrive auto-delete recordings?

No — not by default. OneDrive keeps a file until someone with access deletes it. If a file does get deleted, it goes to the Recycle Bin first: 30 days for a personal Microsoft account, or up to 93 days total across the first- and second-stage Recycle Bin for OneDrive for Business and SharePoint, where an admin can also restore from the second stage after a user empties the first. An organization can layer a retention or deletion policy on top through Microsoft Purview, but that's an explicit admin choice, not a default behavior.

Zoom's failure mode is the opposite shape. There's no retention policy required for recordings to disappear — the account-wide storage cap does that on its own once the pool fills, and an account owner can separately turn on auto-delete after a set number of days, which is easy to forget is active. If the goal is "recordings stick around until we choose to remove them," OneDrive's default already matches that; Zoom's doesn't.

What about sharing recordings outside the org?

OneDrive sharing links work the way your team already shares a proposal or a contract: pick view or edit access, set an optional expiration date, revoke access any time. A client or student doesn't need a Microsoft account to open a view-only link, though your organization's sharing defaults — set by a Microsoft 365 admin — can restrict links to specific people or block external sharing outright, so check that setting if a client says they can't get in.

Zoom's share links are tied to the meeting they came from, not the recording as a long-lived asset, and an account admin can turn on "require authentication to view," which locks out anyone without a Zoom login on the same account. For a recording that needs to reach a client, a parent, or an outside auditor, that's a setting worth checking before you rely on the link.

Where do recordings need to be reachable?

Once a recording lands in OneDrive, it's inside the same OneDrive account as the rest of your files — searchable from OneDrive itself, and reachable by Word, Copilot, or whatever else your organization already runs against Microsoft 365 content. A recording stuck in Zoom Cloud is reachable by Zoom-aware tools and not much else. If your organization ever moves off Zoom, the archive doesn't move with it — it's already sitting inside the Microsoft 365 tenant the rest of your documents live in.

When Zoom Cloud is still the right call

A few situations where keeping recordings in Zoom Cloud makes sense:

• You need a shareable link seconds after the meeting ends. Zoom Cloud gets you a URL faster than any pipeline that copies the file elsewhere afterward.
• Your compliance story is built around a Zoom-specific contract or BAA that doesn't extend to OneDrive. Don't unwind a working compliance arrangement to save $10 a month.
• You're comfortably under the storage cap and never share recordings outside Zoom. If there's no problem, there's nothing here to fix.

What changes when you move to OneDrive

Zoom keeps recording to its cloud exactly as it does now — nothing about the meeting or the recording process changes. What changes is that once a recording is ready, a copy lands in OneDrive, and from that point OneDrive is the durable copy. Once you've confirmed a few backups landed safely, you can let Zoom's own storage settings clear its copy on a schedule you control, instead of racing the storage cap every few weeks.

How RecordFlow fits

RecordFlow watches for finished Zoom cloud recordings and streams each one — video, audio, transcript, and chat log — into a dedicated Apps/RecordFlow folder in your OneDrive, the moment Zoom marks it ready. The transcript renders as a Word document rather than a Google Doc, so it opens directly in the Microsoft tools your team already uses, and meeting-summary archiving turns Zoom's AI Companion summary into a Word document too. This works the same way whether you're a solo practitioner connecting your own account or a Zoom account admin archiving every member's recordings into one OneDrive with a sub-folder per person — RecordFlow's admin-managed app handles a whole team from one install. See our Privacy Policy for how recordings are handled in transit; RecordFlow never stores recording bytes on its own infrastructure.

The years of Zoom recordings already sitting in your account are still one storage cap or retention policy away from gone — even after you set up a backup tool. Most of these tools only start capturing recordings from the moment you connect them. Everything that was already there — client sessions, training replays, board meetings, whatever your account has accumulated — is exactly as exposed as it was before you set anything up.

For a lot of accounts, that "everything already there" isn't a few weeks of gap — it's a handful of years. That's the migration people actually show up to do: not "protect tomorrow's recording" but "move the entire history before something forces the issue."

That backlog is usually the bigger risk, not the smaller one. New recordings get caught the moment they land. It's the years of existing recordings racing the storage cap right now that most backup setups quietly leave behind — and the accounts we hear from most aren't missing a week or two, they're carrying a handful of years of history that's never been touched.

What's actually happening

Most Zoom backup integrations — no-code automations, first-party connectors, anything triggered by a "recording completed" event — are built to react going forward. They watch for new recordings and copy each one as it lands. None of that logic reaches backward into what's already in your account, so a backlog built up over months or years just sits there, unprotected, no matter how long the automation has been running.

Even setups that do attempt to pull older recordings tend to choke on the files themselves. A single hour of Zoom recording typically runs a few hundred megabytes once Zoom finishes compressing it. A lot of general-purpose file-transfer automations cap how large a single file transfer can be — built for spreadsheets and form submissions, not hour-long video. Point one at a multi-year backlog and the failure mode is predictable: it works fine on short clips, then silently drops or errors out on anything longer than a few minutes.

Zoom's own web portal doesn't help either. Downloading a cloud recording means opening it and downloading it from its own page, one recording at a time, with no bulk-export option in the recordings list — impractical past a handful of meetings and genuinely not viable across a backlog that spans years. Meanwhile the clock on that backlog keeps running: storage pools fill and, on accounts with a retention policy set, recordings older than the policy window age out automatically — regardless of whether anyone got around to backing them up first.

That one-at-a-time limit is exactly why the job often ends up delegated: a virtual assistant or admin opens each recording in the Zoom portal, downloads it, and re-uploads it to Drive by hand, one meeting at a time. It's how a lot of solo practitioners and small teams have been keeping up — until the VA's hours run out, they move on, or the backlog quietly outgrows what anyone signed up to do manually. What's left afterward isn't "mostly backed up with a small gap" — it's however many months went by since the last person touched it, on top of whatever was never covered in the first place.

How to migrate the whole backlog, not just what's new

RecordFlow's archive history setting exists specifically for this — it controls how far back into your existing Zoom recordings a connected account reaches, separately from the fact that it also archives everything new going forward.

1. Connect Zoom to your Google Drive. About 60 seconds — sign in with Zoom, connect Drive, pick a folder. This part is read-only; nothing is deleted or changed in Zoom. Consolidating to Dropbox or OneDrive instead works the same way — the archive-history setting below is the same regardless of destination.
2. Open Settings and set Archive history to match your backlog. Four depths are available: the past month, the past 6 months, the past 2 years, or your full 10-year Zoom cloud history. A new connection starts on the past month, included free, so a decade of video doesn't land in your Drive on day one. Going deeper than the past month is a one-time paid unlock — pick a deeper option and Settings shows a "contact support" panel; send your invoicing details and we'll turn it on. Once unlocked, picking a deeper option than what's currently set starts importing the older recordings immediately — narrowing it later only limits future imports, and nothing already archived to Drive is ever removed. (Comparing Drive's cost against Zoom's paid storage add-ons is worth a look if the price of a deep backfill is giving you pause.)
3. Let it run. Recordings appear in your Drive folder progressively as each one is fetched and verified, not all at once. A backlog of a few dozen meetings usually finishes in minutes; a library spanning years and thousands of meetings runs in the background over a longer stretch — RecordFlow has completed single-day backfills of well over a thousand meetings without manual intervention.
4. Running the archive on behalf of a team? An admin-managed install applies the same backfill account-wide — one admin connects once, and every enrolled member's existing recordings import into their own sub-folder under a Drive root the org controls.

The part that makes a large, old backlog actually finish is how each file moves. RecordFlow streams recordings from Zoom to your storage in small chunks rather than holding an entire multi-gigabyte video in memory at once. A three-hour training recording transfers the same reliable way a five-minute session does, and if one chunk fails partway through, the transfer resumes rather than restarting the whole file from zero.

How RecordFlow fits

Backfilling isn't a separate mode bolted onto RecordFlow — it's the same archiving pipeline that handles new recordings, just pointed at a deeper slice of your Zoom history. Widen the archive-history setting and the same chunked-transfer, verified-before-anything-else logic that copies tomorrow's meeting also reaches back and copies last year's — years of client sessions and board meetings included, transferred directly from Zoom to your Drive rather than stored on RecordFlow's servers in between. Once your backlog is safely in Drive, auto-delete is there if you want Zoom's copy cleared too — but only after each recording's Drive copy is verified, never before, and always opt-in.

Three weeks after your best rep closes a deal, the sales manager wants that discovery call as a coaching example for the next new hire — and nobody can find it. If you're a solo rep instead of a manager, you've hit the same wall on your own: the exact line that got a hesitant prospect to say yes is buried somewhere in your Zoom recordings, if it hasn't already aged out. Every deal call is a business asset the moment someone needs it again — onboarding, a lost-deal review, a clip for the next pitch deck — and nothing about where Zoom stores that recording makes it easy to find twice.

What's actually happening

Most sales teams run their calls through one shared Zoom account, with each rep as a Licensed user hosting their own meetings. When a call ends, Zoom's cloud recording lands under that rep's own account — not filed by deal, account name, or pipeline stage, just a meeting topic and a date. A sales manager can see every recording across the account from Zoom's account-wide recording view (Account Management → Recording and Transcript Management), but that view is a list by host, not a library organized around the deal.

The bigger problem is that the recording isn't durable. Zoom's cloud storage is pooled across the whole account, not per rep, and once it fills, Zoom can block new cloud recordings account-wide — the full storage math is covered here if you want it. Some accounts also run a retention or auto-delete policy to manage that pressure, which ages recordings out on a fixed schedule — including the exact objection-handling example a manager wanted to reuse eight months later.

So a sales call recording has two problems working against it at once: it's siloed under whoever happened to host it, and it isn't guaranteed to still exist by the time someone wants it again.

How to record Zoom sales calls to Google Drive automatically

1. Get every rep's calls landing in one place automatically. Instead of a recording staying wherever Zoom put it, route it to a Google Drive folder the team already uses — the moment Zoom marks the recording ready, not whenever someone remembers to go find it.
2. Keep it organized by rep and date, not one flat pile. A sub-folder per rep, named the way your team already thinks about ownership, means a manager pulling up "Jordan's calls from March" doesn't have to guess which recording is which.
3. Turn the transcript into something searchable. Alongside the video and audio, a clean, timestamped Google Doc transcript means finding the exact line a manager wants to quote in a coaching session is a text search, not twenty minutes of scrubbing video.
4. Point downstream tools at the Drive folder, not the Zoom recording page. Once a call is filed in Drive, that's the stable link to hand to a CRM note, a clip-editing pass, or a shared deal-review doc — it doesn't expire when Zoom's storage clock runs out.
5. If storage pressure is what's driving cleanup, don't let it race the backup. The safe way to auto-delete Zoom recordings is to confirm the Drive copy first and only then let Zoom clear its own copy — so freeing up space never costs you a recording nobody backed up yet.

For a single rep managing their own Zoom account, that's the individual RecordFlow setup: sign in with Zoom, connect a Drive folder, done in about 60 seconds. Every call that rep hosts from then on lands in Drive automatically, passcode-protected sessions included. For a whole sales team on one shared Zoom account, RecordFlow's admin-managed app is the better fit — whoever runs the account installs once, connects a single Drive folder, and every enrolled rep's calls land in their own sub-folder under it. No individual rep has to set anything up. Recordings stay attributed to whoever hosted the call — nothing merges reps' calls into one pile — and enrollment for the team version is admin-controlled per rep, the same opt-in toggle used for any other org, so nobody's calls start archiving without the admin switching them on.

How RecordFlow fits

RecordFlow doesn't touch your CRM, doesn't generate clips, and isn't a call-intelligence tool — it does one job: land every Zoom recording — video, audio, transcript, and chat log alike — into a Google Drive folder the team owns, automatically and within minutes of the call ending. Since these are calls with people outside your org, the same recording disclosure Zoom already requires covers the archive too — RecordFlow doesn't change what participants were told, it just makes sure the file doesn't disappear afterward. Once a deal call is sitting in a Drive folder organized by rep, whatever your team already uses to pull quotes into the CRM, cut a clip, or build a coaching library is working from a file that isn't going anywhere — not a Zoom link running against a storage clock.

A registrant who had to drop off early emails asking for the webinar replay. You go looking for it in Zoom's recordings list, and it isn't there — somewhere between running that session and the next one on the calendar, the account's cloud storage filled up, and the reply you send back is an apology instead of a link.

That's the webinar-specific version of a problem plain Zoom meetings don't hit quite as hard: bigger files, a separate recording setup, and a replay that has to stay reachable for people who never showed up live.

What's actually happening — and where a webinar recording actually lives

Zoom Webinars isn't a bigger meeting — it's a distinct product with its own license, layered as the Webinar add-on on top of a paid Zoom plan, scaling from 500 up to 1 million view-only attendees depending on the tier purchased. It also draws a hard line meetings don't: panelists are full participants who can share video, share their screen, and appear on camera, while attendees are view-only unless the host unmutes them. That split carries straight into the recording. A Zoom Webinar recording can produce separate output files for the main video, the chat log, the Q&A panel, and the panelists — more distinct files per event than a standard meeting recording generates, and more data behind each one.

All of that still lands in the same place as everything else you record: the same pooled cloud storage sitting on your Zoom account, 10 GB per licensed user on Pro and Business, scaling up by plan. Webinars don't get a separate bucket — they draw down the identical pool your regular meetings do, just faster per event. A solo host running just one webinar a month still watches that add up quietly in the background — the kind of slow drain that's easy to ignore until the day it blocks a recording — and a production team or agency running several webinars for different clients out of one Zoom account can burn through it in weeks. And when the pool is empty, Zoom stops starting new cloud recordings for the whole account — not just webinars, everything — until someone frees space or buys more.

If you use Zoom's on-demand webinar feature, the replay problem looks solved on paper: registration stays open after the event, and anyone who registers gets a link — a live join link if they register before or during the webinar, and a direct link to the cloud recording if they register after it's over. It's a genuinely useful lead-capture mechanic, and checking the "make the webinar on-demand" box automatically turns on cloud recording for you. But it comes with real limits: on-demand only works with cloud recording, and it flatly doesn't support recurring webinars. If your webinar is a standing weekly training or a recurring office-hours session rather than a one-off, on-demand isn't available to you at all — Zoom generates no automatic replay link, and getting the recording to a late registrant is entirely on you.

How to save every webinar recording to Google Drive

1. Turn on cloud recording for every host who runs a webinar under the account, not just the account owner — Zoom Settings → Recording → Cloud recording. A co-host recording locally is invisible to any backup automation and gone the moment their laptop isn't around.
2. Decide whether on-demand is the right fit case by case. Turn it on for a genuinely one-off, non-recurring webinar where you want Zoom to auto-issue replay links. For a recurring series, plan from the start to send the replay yourself — on-demand won't do it for you.
3. Connect an automation that copies every webinar recording into a dedicated Drive folder — video, audio, chat log, Q&A, and panelist files — the moment Zoom finishes processing. RecordFlow does this without you ever opening the Zoom portal to download anything by hand.
4. Name the Zoom webinar's topic consistently (Series Name — Session 04, always the same pattern) so the backup lands labeled the same way in Drive. A producer scanning a folder six months later shouldn't have to open five files to find the right one. Running the same webinar every week? Naming the topic Series Name/Session 04 (series before the slash) lets RecordFlow group the whole series into one shared folder automatically instead of a flat list — off by default; the linked docs cover how to turn it on.
5. Put a Drive link, not a Zoom link, in the follow-up email to registrants. Sharing straight from Google Drive opens for anyone with the link, no Zoom account required on their end — the same fix that solves this for a client who can't open a Zoom recording link works just as well for a registrant list, and the replay doesn't age out with your account's storage clock or a retention policy set independently of your webinar settings.
6. Running webinars for more than one client? If each client has their own Zoom account, connect RecordFlow separately for each one — every connection gets its own Drive destination, so handing off a finished engagement is a folder transfer, not a search through someone else's Zoom recordings list. Running multiple clients' webinars through one shared Zoom account instead? Use a client-named subfolder inside your single connected Drive destination to keep them apart.

How RecordFlow fits

RecordFlow connects your Zoom account to a Google Drive folder once — about 60 seconds — and every webinar recording lands there automatically from that point on: video, audio, chat log, any separate Q&A and panelist files Zoom generates, and a clean Google Doc transcript with speaker labels and timestamps, so a producer can search a session for the exact minute a question was answered instead of scrubbing an hour of playback. Files move straight from Zoom to the Drive folder you already own — RecordFlow never keeps a copy on its own infrastructure — and it works the same way whether you're a solo host running one webinar series or a production team archiving several client accounts in parallel. Once a replay is safely in Drive, the account's storage pool stays small, and the next scheduled webinar is never at risk of failing to record because an old one is still sitting in Zoom's cloud.

You have forty coaching calls, or a semester of class recordings, or a quarter of discovery calls — each one already backed up, each one already transcribed. And you still can't answer the question you actually have. What did clients keep asking about this month? Which objection came up across six of my last ten sales calls? When did we first talk about the pricing change? A single transcript answers a question about one meeting. Those questions span all of them, and re-watching forty recordings to find the pattern isn't realistic.

The fix isn't a new tool. It's treating the folder itself as the asset — a knowledge base you can ask questions across — instead of dozens of separate documents you'd open one at a time.

Why a folder of transcripts is a knowledge base

Gemini Notebook — Google renamed NotebookLM to Gemini Notebook in July 2026, same product, same URL, new name — takes Google Docs, PDFs, and a handful of other file types from Drive as "sources," and answers questions grounded only in the sources you've added, citing the specific source document behind each part of the answer. Add one transcript Doc and you can ask about that one call. Add every transcript Doc from a client's history, a cohort's sessions, or a quarter of calls, and the same question — "what themes came up across these?" — now has an answer with citations back to the individual sessions that raised each one.

Two things have to be true for that to work. First, each recording needs a transcript Gemini Notebook can actually read — not the raw .vtt caption file Zoom hands you, which is fragmented into three-second cues and isn't accepted as a Gemini Notebook source at all. RecordFlow uploads a clean, readable Google Doc transcript into Drive alongside the raw .vtt for every recording it syncs; the companion deep-dive on converting Zoom transcripts to Google Docs covers that conversion in full, so this post won't re-explain it — it assumes you're already there and focuses on what happens once you have a folder of these Docs, not just one.

Second, you need to be able to tell the sessions apart once you're picking sources. A notebook with thirty transcript Docs all named "Zoom Meeting" or "Transcript" is not a knowledge base — it's an unlabeled pile you have to open each file to identify. This is where the recording's file name does real work, not just bookkeeping.

For the wider picture — what Docs, Gemini Notebook, and Vids can each do with a Zoom recording once it's in Drive — see the ecosystem overview of Zoom recordings in Google Workspace.

Build the knowledge base

1. Get every recording's transcript into Drive as a clean Google Doc. If you haven't set this up yet, RecordFlow does this automatically the moment a Zoom recording finishes — see the companion how-to on backing up Zoom recordings to Google Drive automatically for the 60-second setup, and the transcript-to-Doc conversion post for what the Doc looks like once it lands.
2. Pick the corpus boundary before you build the notebook. A knowledge base is only useful if it answers questions about a coherent set of sessions — one client's full history, one cohort's class recordings, one quarter of discovery calls. Decide the boundary first; it becomes the notebook.
3. Create a Gemini Notebook and add the transcript Docs as sources. In Gemini Notebook, start a new notebook, choose "Add source," pick Google Drive, and select the transcript Docs for the sessions inside your chosen boundary. Because RecordFlow names each meeting folder with the start date and the meeting topic (for example 2026-06-03-Quarterly review), you can tell sessions apart in the source picker without opening each one first.
4. Ask across the set. Try questions that only make sense across many sessions, not one: What objections came up more than once? Which commitments did this client make and never revisit? What questions has this cohort asked most often? Gemini Notebook grounds every answer in the sources you added and cites which transcript it pulled from, so you can jump from the answer straight to the exact call.

How RecordFlow fits

RecordFlow isn't the AI here — Gemini Notebook is. RecordFlow's job is narrower: the moment a Zoom recording finishes, it copies the video, audio, chat log, and transcript into a Drive folder you own, and lands a clean Google Doc transcript alongside the raw .vtt, in a folder named by date and topic. RecordFlow never reads or analyzes what's inside those transcripts — it copies the file into your Drive and stops there; what Gemini Notebook does with it from that point on runs on your own Google account, not ours. That combination — every session landed automatically, transcribed into a document Gemini Notebook can actually read, and named so you can tell sessions apart — is what turns a folder of recordings into a corpus you can build a notebook from, instead of a pile of files you'd have to sort by hand first.

You're looking for one call. The client mentioned something in March about switching jobs, and you want to hear how you responded before tomorrow's session. So you open Drive, land in a folder with 200-odd entries named after whatever Zoom happened to call the meeting that day, and start opening files one at a time. Ten minutes later you still haven't found it, and the search box hasn't helped because nothing in the file names says who the call was with.

Backup already solved the scary version of this problem — the recording exists, it didn't vanish when Zoom's storage filled up. This is the quieter version: the recording exists somewhere, and finding it costs you ten minutes you don't have between sessions.

What's actually happening

A folder that works fine at twenty files stops working at two hundred, and the failure isn't really about volume — it's about naming.

Google Drive's own search is genuinely capable: you can search by file name, filter by date, or use operators like title: and after: to narrow results (Google's search-operators guide covers the full list). None of that helps if the thing you're searching for — the client's name — isn't in the file name to begin with. A search engine can't find text that was never written down.

Zoom's own naming makes this worse by default. A recording folder or file named after whatever the meeting was auto-titled ("Zoom Meeting", or a recurring meeting's generic topic) carries no information about who the call was with. Multiply that by every client and every week, and you get exactly the pile described above — searchable in theory, useless in practice, because search only works on words that are actually there.

The fix: three habits, not a reorganization project

The instinct is to block off an afternoon and rebuild the whole archive. Don't — a one-time reorg degrades back into a mess within a few months unless the underlying habit changes. Three small habits, done consistently, do more than one big cleanup:

1. Put the client's name in the Zoom meeting title, not the Drive folder

This is the highest-leverage fix and it happens before the recording exists. When you schedule or start a Zoom session, name the meeting with the client (or cohort) it's for — Jane Smith — Session 4, or Cohort 3 — Week 6, whatever pattern fits your practice. That title becomes the meeting's topic, and it's the one piece of metadata that flows automatically into everything downstream: the recording file names, the transcript, and (if you're on RecordFlow) the archive folder name. Fix it once, upstream, and every tool that touches the recording afterward inherits a name that's actually searchable.

2. Build a client view with shortcuts — don't move the original folders

Once recordings land somewhere with consistent, client-tagged names, the temptation is to drag each one into a Clients/Jane Smith/ folder. Resist that specifically if RecordFlow is archiving for you: it creates a fresh dated folder per meeting and re-uses that exact folder if a later webhook event adds another file to the same session (a transcript that finishes processing after the video, for example) — and it finds that folder by looking inside the same parent it created it in. Move the folder out from under it and a later addition can land in a brand-new duplicate folder instead of the original.

The fix is Google Drive's shortcuts, not a move. Right-click any meeting folder → Organize → Add shortcut, and drop the shortcut into Clients/Jane Smith/. The shortcut points at the same folder — opening it takes you to the exact same files — without changing where the real folder lives or who its parent is. You get a tidy per-client view layered on top of the archive, and RecordFlow's own folder lookups keep working exactly as before, because as far as Drive and RecordFlow are concerned, the folder never moved.

3. Split active from archived — with shortcuts, not deletion

The working set is usually much smaller than the whole archive: current clients, this quarter's cohort. A top-level Active clients/ folder holding shortcuts to current clients, and an Archived clients/ folder you sweep an ended engagement into once a quarter, keeps the folder you actually browse day-to-day small — without touching the underlying dated archive at all. Nothing gets deleted or moved; a client's shortcut just shifts from one folder to the other.

A folder tree to copy

No download needed — this is the whole system, and it's three folders and a naming habit:

My Drive/
└── RecordFlow Recordings/        (RecordFlow's archive — untouched)
    └── 2026/
        └── 2026-03-14-Jane Smith — Session 4/
└── Active clients/
    └── Jane Smith/                (shortcuts to that client's meeting folders)
└── Archived clients/
    └── Past Client Name/          (shortcut shifted here at engagement end)

Once the client's name is in every meeting title, "the March call with Jane" is a Drive search for Jane filtered to after:2026-03-01 before:2026-04-01 — five seconds, not ten minutes.

How RecordFlow fits

RecordFlow already does the part of this system that has to happen automatically: the moment a Zoom cloud recording finishes processing, it copies the video, audio, chat log, and transcript into a dated folder — YYYY-MM-DD-Topic — inside a year folder in the Drive location you chose, no manual download or upload step. (The setup walkthrough covers the 60-second connection if you haven't set that up yet.) Because that folder name is built straight from the Zoom meeting's title and start date, habit #1 above — naming the meeting for the client — is the only manual step in the whole system; everything else, including the searchable Google Doc transcript that lands alongside the raw files, happens without you touching Drive at all.

The shortcut-based client view sits on top of that archive. And once a client's folder is easy to find again, the handoff post covers turning it into something you send them directly.

The question rarely comes from a lawyer. It comes from an instructional-technology director halfway through approving a new tool, pausing to ask: "wait — does this touch student data covered by FERPA?" For a Zoom cloud recording, the honest answer is "sometimes, and it depends on where it ends up" — which is a worse answer to give a security reviewer than a clean yes or no, but it's the accurate one, and it's worth working through properly before you install anything.

What's actually happening

FERPA doesn't regulate recordings as a category. It regulates education records — and the U.S. Department of Education's Student Privacy Policy Office defines those as records that are directly related to a student and maintained by the institution (or by a party acting on the institution's behalf), in any format, explicitly including video and audio.

That two-part test decides more than it looks like it does:

• A lecture recording where only the instructor speaks, with no student identifiable in video, audio, or chat, isn't a student record at all — there's no student it's "directly related to."
• The moment a student asks a question on camera, answers a cold-call, or presents to the class, that portion of the recording identifies them — and if the institution keeps a copy, it's now an education record, same as a transcript or grade file.
• A recording an instructor keeps purely to themselves — never shared, not stored anywhere the institution administers — generally isn't "maintained by the institution" either, under FERPA's carve-out for records kept in an individual's sole possession as a personal memory aid. That's a fragile position to rely on by accident, though: the same recording, the moment it's synced to a departmental drive or shared with a TA, stops being a private note and becomes an education record the institution maintains — whether or not anyone decided that on purpose.

Neither Zoom's nor Google's infrastructure is itself "FERPA compliant" — compliance describes how an institution and its agents handle records, not a feature of software. When a third-party service handles those recordings on the institution's behalf, FERPA's school-official exception (34 CFR 99.31(a)(1)(i)(B)) is the relevant test: the service has to perform work the institution would otherwise do with its own staff, stay under the institution's direct control over how those records are used and maintained, and be bound by 34 CFR 99.33(a)'s limits on redisclosing the personally identifiable information it touches. None of that is automatic — the institution has to be able to demonstrate it, usually through a written agreement plus a setup that actually reflects direct control in practice, not just on paper.

Retention: FERPA doesn't set a clock, your institution does

FERPA itself doesn't specify how long a class recording has to be kept, or how soon it must be deleted — that's a common misread. Once something qualifies as an education record, it falls under whatever records-retention schedule your institution (or your state's public-records law, for public institutions) already applies to education records generally. There's no separate "recording retention" rule to look up; there's only your existing retention schedule, now applying to a new kind of file.

In practice that cuts both ways. A recording archived automatically to Drive doesn't get to sit there forever by default just because it's convenient to keep — if your retention schedule says grade-related materials get reviewed or purged after a set period, an archived class recording that qualifies as one is subject to the same review. And the reverse risk is the one that actually costs people: Zoom's own cloud storage isn't built to preserve anything on your institution's retention schedule — it ages recordings out on Zoom's terms, not yours, which is precisely the gap an institution-owned archive is meant to close.

Why an institution-owned archive is the defensible setup

Direct control is easy to assert and hard to demonstrate once recordings are scattered across individual instructors' personal accounts. If an adjunct's own Google Drive is where a semester of class recordings lives, the institution can't apply access controls to it, can't audit who's opened a file, and has no guarantee the recordings survive after that adjunct's contract ends and their account gets deactivated — the opposite of controlling how records are used and maintained.

An archive that lands in a Drive folder the institution itself owns and administers — a Workspace-managed account, or better, a shared Drive the department controls — is what actually lets IT show a reviewer that student recordings sit somewhere the institution can govern, not somewhere it merely hopes an instructor is being careful.

What to check before you rely on any recording archive

How RecordFlow fits

Here's the part worth stating plainly, because it's the part a vendor is tempted to blur: nothing below makes your institution FERPA-compliant, and we don't claim it does. RecordFlow is infrastructure your institution configures within its own compliance posture, not a certification that stands in for your own legal review. Whether a given recording is an education record, who needs a legitimate educational interest to see it, and what your written agreements say — that's a determination for your institution and its counsel, not for our marketing page.

What RecordFlow's admin-managed app does give you is the shape FERPA's school-official test rewards. One Zoom account admin installs it once, connects a single Google Drive folder the institution owns as the archive root, and enrolls instructors from a dashboard — nobody's recordings start archiving until an admin flips their toggle on. Every enrolled instructor's sessions land in their own named sub-folder under that institution-controlled root, the same layout our universities and colleges guide walks through for semester turnover. And RecordFlow itself never stores a recording's bytes on its own infrastructure — files stream from Zoom straight into the Drive folder your institution controls, detailed end to end in how RecordFlow handles your data. The institution-owned destination and the admin-only enrollment toggle are what make direct control demonstrable — the pieces your reviewer actually asks about, running automatically instead of depending on someone remembering to do it by hand.

The storage alert always lands during finals week, when every course on campus is recording at once. It lands on IT — not on the professor who filled the pool. Those recordings aren't incidental. They're the lecture a student with an accommodation is owed, the defense a graduate committee needs on file, the guest lecture a department wants to reuse next year. And because Zoom's storage is one shared account-wide pool, one over-recording department can block cloud recording for every other course on campus the moment it fills.

How Zoom storage management works for university IT

Zoom's cloud recording storage is granted per licensed user and pooled at the account level on every plan — but Education tiers start from a much smaller allowance than a standard Business plan. Education Core and Education Legacy give just 0.5 GB per licensed user; Education School & Campus steps up to 5 GB; School & Campus Plus and Enterprise Essentials step up again to 10 GB; only Enterprise Plus and Premier go unlimited (the full table is in our plan-by-plan storage breakdown). Multiply whichever tier your institution licenses by however many faculty, TA, and staff seats you have, and the resulting pool is what every course, every department, and every guest lecture draws against simultaneously — nobody's recordings get a private allotment, whether your institution calls itself a school, a college, or a university.

That pooling is compounded by a second problem specific to a campus: turnover. Adjuncts rotate in and out every semester; TAs graduate; a department loses a lecturer mid-year. Deactivating a Zoom user doesn't offer any way to hand off their recordings — that option only appears when an admin unlinks or deletes the user, not when they simply deactivate one — and even then, transferring their cloud recordings to another licensed user is a checkbox the admin has to select on purpose during that flow, not something that happens by default. Miss it in the rush of an end-of-term offboarding batch, or deactivate instead of unlinking or deleting, and a semester's worth of lecture recordings is now only as durable as whether anyone remembered.

Both problems point the same direction: Zoom's storage model is built around one host's recordings inside one term, not an institution's teaching archive that has to survive every semester's faculty turnover.

How to fix it

1. Install RecordFlow's admin-managed app once, as the Zoom account admin — for a department or the whole institution, not per instructor. One authorization covers everyone you enroll.
2. Connect one Google Drive folder as the archive root. A shared drive the institution or department owns is worth the extra setup step over a personal Drive — it survives staff turnover the same way the archive is meant to.
3. Enroll instructors and TAs from the admin dashboard. New members can be archived automatically by default, or leave that off and add each person deliberately as adjuncts rotate in every semester — either way, an instructor never has to install or configure anything themselves.
4. Each instructor's sessions land in their own named sub-folder under the shared root, dated and organized the same way every term, so a program coordinator, registrar, or accreditation reviewer can find "last spring's Thursday Organic Chem lecture" without emailing five people who may not even work there anymore.
5. Toggle an instructor off when their contract ends — don't rely on an offboarding checklist catching it. Because the archive already lives in your Drive by the time each session finishes, a departing adjunct's prior recordings are already safe; you're only deciding whether their future sessions keep flowing in.

What to check if a recording didn't archive

How RecordFlow fits

RecordFlow's admin-managed app is the version an instructional-technology director or department IT lead installs — the setup above, running for every enrolled instructor, with nothing for the instructor to set up on their end. If storage pressure is what triggered the search in the first place, our admin storage-management guide covers what Zoom's own Reports and auto-delete tools can do on top of an archive that's already running.

One thing worth being precise about: this post isn't a FERPA compliance statement, and we don't make one. What we can state plainly is what our own systems do — RecordFlow never stores a recording's bytes on its own infrastructure; files stream directly from Zoom to the Drive folder your institution owns and controls, and enrollment is an admin-only toggle a member can't turn on for themselves. The full account of what we store, minimize, and delete — the kind of detail a security or compliance reviewer actually asks for — is in how RecordFlow handles your data. Your institution's FERPA obligations are yours to evaluate with your own counsel; RecordFlow is the processor moving the recordings, not the office that clears them for release.

The cost side, at institutional scale

A department archiving a semester of lectures for a few dozen instructors is not in the same cost regime as an individual, and the per-gigabyte figures stop being rounding errors. It is worth pricing the options explicitly before renewing an add-on tier or a storage plan for another year: Zoom's own published add-on rates run from $0.33 down to $0.10 per gigabyte per month, and object storage the institution owns runs from $0.023 on S3 Standard down to well under a cent on an archive tier nobody reads back. The full comparison is here — including why copying recordings somewhere cheaper does not, on its own, reduce what you pay Zoom.

Somewhere in your Zoom account settings is a toggle that will start deleting recordings on a schedule the moment you turn it on. Most admins never touch it until the "storage almost full" alert forces the question — not because they've decided against a retention policy, but because nobody's gotten around to deciding on one. So the org defaults to the other failure mode instead: every recording anyone has ever made sits in the account's storage pool, growing, until the quota actually fills and someone has to triage it under pressure anyway.

Neither is a policy. One is silence; the other is a delete button nobody wants to be the one to press. This post is about the account-wide version of the decision — setting retention for the whole org, not how long an individual practitioner should keep their own client recordings, which is a related but separate question with a different answer.

What Zoom's account-level retention setting actually does

Zoom's cloud recording auto-delete lives in Account Management → Account Settings → Recording & Transcript, under a toggle usually labeled something like "delete cloud recordings after a specified number of days." It requires a paid Zoom plan — Pro, Business, or Enterprise (cloud recording isn't available on the free Basic tier at all), and it's off by default for most accounts — Zoom's own documentation doesn't spell out a universal default, but leave it untouched and nothing ages out on its own. Left off, recordings simply sit in the account's cloud storage pool until someone deletes them by hand. A full storage quota doesn't trigger any retroactive cleanup either — it just blocks new cloud recordings from starting until an admin frees space or buys more, which is a very different problem than "Zoom quietly clears old recordings for you."

Turn it on and you specify a day count; recordings older than that get deleted automatically, account-wide, on a fixed daily schedule. The setting also exists at the group and individual-user level, and each level inherits from the one above it unless an admin locks it — click the lock icon after saving to stop a group admin or a licensed user from quietly loosening the account-wide default for their own corner of the account. Skip the lock step and a policy you thought was org-wide might only be a suggestion for anyone with settings access at a lower level.

Two mechanics matter more than the toggle itself:

• It's blind to backups. Zoom's auto-delete has no idea whether a recording has been copied anywhere else. It deletes on day N regardless. If your policy window is shorter than however long it takes someone to notice and save a copy, the recording is gone before anyone gets the chance.
• Deleted isn't gone-gone, briefly. Recordings removed by auto-delete land in Zoom's Trash first, typically recoverable for around 30 days before permanent deletion. That's a grace period for a mistake, not a second backup — don't set a policy assuming Trash will bail you out.

The safe order: archive first, then set the policy

The failure mode isn't the retention window you pick — it's the order you do things in. Setting a Zoom-side auto-delete policy before every member's recordings are backed up somewhere durable means the policy can outrun the backup. The fix is the same "back up, verify, then delete" discipline as clearing an individual's storage safely, just applied at account scope:

1. Get every member's recordings archived to a Drive root you control, first. Before you touch the retention toggle, make sure there's a durable, account-owned copy of what's already in the account — not scattered across each member's personal Drive, if they're saving anything at all. Check how far back that archive actually reaches before you trust it: RecordFlow's Archive history setting starts at the past month, and you widen it — to 6 months, 2 years, or 10 years — to pull in the older recordings a retention window would otherwise be the first thing to delete. Archiving the whole account into one admin-controlled Google Drive is the piece that makes everything after this step safe.
2. Decide the window on purpose, not by default. For most orgs without a specific compliance requirement, a flat 1-3 year default is a low-drama starting point — write it down, and treat any client agreement, program terms, or licensing-board guidance your members have separately committed to as a floor that overrides your default for those specific recordings.
3. Set it at Account Management → Account Settings → Recording & Transcript, and lock it. Enter the day count, save, then click the lock icon. Locking is what keeps a group-level or user-level setting from silently overriding the account policy you just decided on.
4. Tell your team before the clock starts. A retention policy that surprises people reads as a data-loss incident even when it's working exactly as designed. A short note — what the window is, and where the durable archive lives if they need something older — heads that off.
5. Check in occasionally, not obsessively. New members inherit whatever the account default is at the time they're added; a quick quarterly glance — not a new recurring chore — is enough to confirm new hires and any newly-created groups are actually covered, and that nobody's quietly unlocked the setting for their corner of the account.

How RecordFlow fits

This is a policy decision Zoom's own settings screen makes you own — RecordFlow doesn't set it for you, and it shouldn't. What RecordFlow removes is the risk in step one: our admin-managed app archives every enrolled member's cloud recordings into a Google Drive folder you control, automatically, within minutes of each recording finishing, and reaches as far back into the existing library as you set Archive history to go — so by the time you sit down to set an account-wide retention window, the "is everything actually backed up" question is already answered instead of something you're taking on faith.

From there, Zoom's account-level auto-delete becomes a tool you can turn on with confidence instead of anxiety, because the durable copy in Drive isn't waiting on that decision. RecordFlow's admin-managed app has its own opt-in auto-delete toggle too — set once for the account, off by default — and it clears a recording from Zoom only after that specific recording's Drive copy is verified, with a three-day grace period built in: the same backup-first order this post argues for, just automated instead of manual.

Six months in, a client says the thing coaches dread hearing: "I'm not sure this is really working." Nothing has gone wrong — they've kept showing up, kept doing the work between sessions — but progress that happens gradually is easy to stop noticing, and easier still to doubt out loud. You could tell them how far they've come. Or you could pull up the recording from their first session and let them watch themselves say it.

What's actually happening

Progress rarely feels like progress while it's happening. It's a lived experience the client updates every day, so each day looks almost identical to the one before it — the change is real, but it's happening below the resolution the client can perceive day-to-day. By the time six months pass, the person who started is genuinely gone, but there's no single moment that marked the shift, so there's nothing for memory to anchor to. What's left is a vague, hard-to-defend feeling that things are probably better, sitting right next to the very concrete feeling that today's session still had a hard moment in it.

This isn't unique to coaching. A large Harvard Business Review analysis of workday diaries found incremental progress is the single strongest driver of motivation — and the easiest thing to lose track of without something external marking it. Coaching runs on the same mechanic: the client is inside the change, which is exactly the vantage point from which change is hardest to see.

A recording sidesteps the whole problem. It doesn't ask the client to trust their memory of who they were — it shows them, in their own voice, on a dated recording, saying the things they said before any of the work had happened. That's the same underlying reframe covered in the companion post on giving clients their session recordings: the recording isn't the coach's filing problem, it's the client's asset. A progress comparison is simply that asset used for a specific job.

Using recordings as a progress mirror

The comparison does the work that reassurance can't:

1. Pull the actual first session, not a summary of it. "You've grown a lot" is an opinion the client can politely doubt. A recording of them describing the exact problem they had in month one is not something they can argue with, because it's their own words, at a timestamp, before any of the growth happened.
2. Watch a few minutes side by side, not the full hour. The point isn't a re-run of the whole session — it's the specific moment where the old pattern shows up clearest, set next to a recent moment where it doesn't. A short, sharp contrast lands harder than an hour of vague nostalgia.
3. Let the client narrate the difference themselves. The strongest version of this conversation isn't the coach pointing out growth — it's the client watching their earlier self and saying, unprompted, "I can't believe I used to think that." Self-generated insight is more convincing than anything a coach can assert, and it's also just a more honest use of the moment: showing evidence and letting the client draw their own conclusion, not steering them toward one.
4. Use it as the natural on-ramp to renewal — not a pitch. "Let's watch where you started" is a question about the work, not a sales script. If the contrast is real, the client reaches the "of course I'm continuing" conclusion on their own, which is a healthier renewal moment than any framing a coach could construct around it.
5. Treat the archive as a timeline, not a pile. One recording is a nice moment. A dated sequence of them — month one, month three, month six — is a record of an entire engagement's arc, and it's the only version of "how far you've come" that doesn't rely on anyone's memory. If a client's sessions currently sit mixed in with everyone else's in your Drive archive, naming their Zoom topic with a consistent prefix — Client Name/Session 12 — can now collect that client's whole arc into one shared folder automatically going forward. It's off by default; the linked docs cover how to turn it on.

None of this requires a formal review process. It requires the early session to still exist, be easy to find months later, and be exactly as long as the client wants to watch — a few minutes, usually, not the whole hour. It's the same underlying habit as the one covered in the post on why replays deepen coaching results: the value isn't in recording the session, it's in someone actually going back to it.

How RecordFlow fits

The reason this rarely happens today isn't that coaches doubt its value for client retention — it's that month-one recordings don't survive to month six. Many Zoom accounts are configured to auto-delete cloud recordings after a set retention window, and even a recording that hasn't hit that clock yet is easy to lose track of in an app coaches don't otherwise use day to day. By the time a progress conversation would be useful, the evidence is often already gone.

RecordFlow keeps the archive intact from the day you connect it — and for an engagement that started earlier, you choose how far back it reaches: the Archive history setting opens on the past month, so your Drive isn't flooded on day one, and widens to 6 months, 2 years, or 10 years whenever you want, backfilling the older sessions as soon as you do. Connect Zoom and Google Drive once — a one-time, roughly 60-second setup — and every recorded session lands automatically in a Drive folder you own the moment Zoom finishes processing it: the video, the audio file, the chat log, and a clean, readable transcript as a native Google Doc, in a folder named with the date and session topic, grouped by year. (The full mechanics are in the pillar guide on backing up Zoom recordings to Drive.) Because nothing expires and nothing depends on anyone remembering to download it before Zoom's retention window closes, the session-one recording is still there — findable in seconds — the day a client wonders whether any of this is working.

The transcript matters here as much as the video. Scrubbing through an hour-old recording to find "the part where they said X" is friction most coaches won't bother with mid-session; searching a clean, speaker-labeled Google Doc transcript for the phrase takes seconds — which is the difference between a progress comparison that actually happens and one that stays a nice idea. RecordFlow never keeps a copy of the recording on its own servers either; the files move straight from Zoom to the Drive folder you control, which matters for a document as personal as a coaching archive.

The work already happened — session by session, mostly invisible while it was underway. All a recording does is keep the receipt. Six months from now, that's the difference between telling a client they've grown and letting them watch it — and, on a sales page, it's another reason a recorded, transcribed archive reads as a premium deliverable rather than a pile of files nobody revisits.

You're staring at a Zoom recording from three months ago, cursor hovering over delete. Keep it and it counts against your storage. Delete it and — what if you needed it? A client dispute, a credentialing application, a "can you resend that session" request you didn't see coming.

Most people resolve this by not deciding: recordings pile up until Zoom's storage cap forces the question, or they get deleted in a panic-clean the day before a "storage almost full" email turns into a hard block. Neither is a retention policy. Both are the absence of one.

What's actually happening

There's no single correct answer to "how long should I keep a meeting recording?" — and the reason isn't that nobody's figured it out, it's that the honest answer depends on three separate things that rarely line up:

• What you promised. If a client agreement says sessions are available for 90 days, that's your floor for that client, regardless of what your storage plan can hold.
• What your profession expects. Some fields have publicly documented record-keeping norms — the American Psychological Association's record-keeping guidelines, for instance, discuss retention windows for client records that many therapists use as a reference point (they're guidelines, not law, and specifics vary by state licensing board). Coaching, consulting, and tutoring generally don't have an equivalent industry-wide standard — you're setting your own norm, informed by your client agreements and your own risk tolerance.
• What your business records require. If a session recording doubles as evidence of billable work, the IRS's general guidance on how long to keep business records (commonly three years, longer in specific situations) is the closest thing to an authoritative default — though it's about records generally, not recordings specifically, so treat it as a floor to reason from rather than a rule that names Zoom recordings.

None of this is legal advice, and this post isn't going to pretend otherwise. If your profession is licensed or regulated, the retention window that actually protects you comes from your licensing board, your malpractice insurer, or your own attorney — not a blog post. What this post can do is separate the retention decision (how long should this exist) from the storage problem (Zoom's cloud fills up), because conflating them is what causes most of the damage: people delete recordings early because Zoom is full, or keep everything forever because deleting feels risky, and both are worse than picking a number on purpose.

It's also worth naming the platform mechanic underneath this. Zoom itself has a configurable cloud recording auto-delete setting that account owners and admins can turn on, set to a fixed number of days, and apply account-wide. Where it's enabled, it runs on a fixed daily schedule that has no idea whether a given recording has been backed up anywhere else — it just deletes on day N. That's a fine tool for storage hygiene once you've decided what "day N" should be, but it's a bad way to arrive at that number in the first place, and a genuinely risky one if nothing else has a copy by the time it fires. (This post is about the individual, one-person version of that decision — if you're setting the policy for a whole org instead, see setting a Zoom recording retention policy for your organization.)

How to set a retention window that actually holds

1. Write down what you've already committed to. Check client agreements, intake forms, and program terms for any stated retention or availability window. That's your floor for those sessions specifically, and it overrides any generic default below.
2. Check your profession's guidance, if one exists. Licensed fields (therapy/counseling being the clearest example) often have published record-keeping guidance from their governing body. If you're in ICF credentialing territory, note that ICF's ask is narrower than general retention — it's about keeping a qualifying session and transcript available at application time, not a fixed number of days, so "until my credential is awarded" is the practical rule there, not a day count.
3. Set a default for everything else. For sessions with no specific requirement, pick one window and apply it consistently — 1 year and 3 years are common, low-drama defaults for solo practitioners. Consistency matters more than the exact number: a rule you actually follow beats a "smarter" one you keep making exceptions to.
4. Back up before you touch the retention clock. Whatever window you land on, apply it to a copy you control — not to Zoom's cloud copy directly. Zoom's storage was never built as a long-term archive (see the breakdown of Zoom's storage limits by plan for why it fills as fast as it does), so treat "still in Zoom" and "still retained" as two different questions. Automatic backup to the cloud storage you own turns this from a manual chore into a non-issue — once every recording lands in a folder you own, on Google Drive, OneDrive, or Dropbox, you're applying your retention window to a durable archive instead of racing Zoom's storage cap.
5. Delete from Zoom only after the backup is confirmed. This is the same safe order covered in how to auto-delete Zoom recordings without losing anything: back up, verify the copy landed, then delete. Never let a deletion — yours or Zoom's own auto-delete policy — run ahead of a confirmed backup.

How RecordFlow fits

RecordFlow doesn't set your retention policy — that decision is yours, informed by your agreements and your profession's guidance — but it removes the two failure modes that make people get retention wrong: forgetting to back something up before it matters, and deleting on Zoom's schedule instead of yours. Every cloud recording is archived to storage you own — Google Drive, OneDrive, or Dropbox — within minutes of Zoom marking it ready, so the "did I save this before the window closed" question goes away entirely.

From there, retention is your call to apply on your own terms: keep everything in your archive indefinitely, prune it on whatever schedule fits your policy, or turn on RecordFlow's own opt-in auto-delete — which clears the Zoom copy only after a backup is verified and a three-day grace period passes, never on a blind fixed-day countdown. The rest of the Zoom storage & retention guides cover the neighbouring problems — what happens when Zoom's storage cap actually fills, and how to delete safely once a backup exists.

Before you approve a third-party app for your whole Zoom account, "trust us" isn't an answer a security reviewer accepts. You want specifics: does it keep a copy of the recording? Can it see people who haven't opted in? What actually happens the day you remove it? A privacy policy page can say anything — what matters is whether the claims hold up against the code that runs in production.

So this post makes exactly the claims our marketing makes about the admin-managed app, and for each one, says what we checked to confirm it's true rather than just asserting it.

What's actually happening

RecordFlow's admin-managed app asks a Zoom account admin for five read-only permissions at install: seeing who's on the account, reading the admin's own profile, and three for reading recordings (listing them, listing the files inside each, and reading those files — the transcript rides along as one of those files). No write scope, no delete scope. What we do with that access — what we store versus discard, who controls it, what disappears on removal — is the part worth verifying rather than trusting.

What we never store: recording bytes

A recording's video, audio, transcript, and chat files never touch a database or a disk we control. RecordFlow streams each file from Zoom's API in chunks, directly into an upload to your chosen destination — a Google Drive, OneDrive, or Dropbox folder, or a YouTube channel — a chunk sits in Worker memory for the moment it's mid-transfer and is gone once it's written there. There's no object-storage bucket or cache layer holding recording content anywhere in RecordFlow's infrastructure; what little caching the sync pipeline does is limited to destination folder/container IDs, so it doesn't recreate the same folder twice mid-run — never file content. If you deleted RecordFlow's entire database tomorrow, no recording would be in it, because none ever was. That's also what keeps the service secure by construction: there's no recording archive on our side for an attacker to go after in the first place.

What we minimize: the account-wide roster scope

To show an admin who's on their Zoom account, RecordFlow requests a single scope — user:read:list_users:admin. Zoom's response for that call carries more fields than we need; RecordFlow keeps exactly four per person — Zoom user ID, name, email, and active/inactive status — and discards the rest before anything is written to our database. Those four fields are the entirety of what we retain about a member before they're enrolled. The scope is never used to read anyone's recordings; recording access runs through entirely separate scopes, and only for members an admin has enrolled. Practically: installing the app and seeing your roster doesn't put a single byte of anyone's recording content in front of RecordFlow. That only starts once an admin turns a specific member on.

Who controls enrollment — and it isn't the member

Here's a claim worth being precise about, because it's easy to overstate: enrollment is admin-controlled, not a self-service member toggle. Only a Zoom account admin can flip a member's switch on the admin dashboard — there's no member-facing "opt in" button, by design; the admin is the one accountable for who gets archived. What is true, and matters just as much: the switch is fully reversible at any time, disabling a member stops their future recordings from archiving immediately, and a later roster refresh never silently re-enables someone an admin switched off. If you're a member who wants out, the path is to ask your admin to switch you off, or email us directly and we'll route the request — both work, and we confirm back to you either way.

What actually happens when you remove the app

When the last admin on a Zoom account removes RecordFlow, Zoom sends us a deauthorization notice, and we delete the account's data in the same request that handles it — every member record, every admin's stored tokens, and the account's sync history, gone before we acknowledge the webhook. It isn't a queued job that runs sometime later; it's synchronous, comfortably inside the 30-day deletion window our Privacy Policy and Data Processing Addendum commit to. Two things are deliberately excluded from that deletion:

• The auto-delete audit log, but only for accounts that ever turned on the optional Auto-delete after archive feature — an immutable, INSERT-only record of each attempt to move a recording to Zoom's Trash, kept for 24 months for security and dispute resolution. It logs deletion attempts, not general sync activity, and never contains recording content.
• The recordings already sitting in your chosen destination — those are yours, and were never RecordFlow's to delete.

If other admins on the account still have RecordFlow installed, only the departing admin is offboarded; the account and its archive keep running for the rest of the team.

Where the files actually live — and who's responsible under GDPR

Every enrolled member's recordings land in their own named sub-folder under one folder the admin connects — the archive root, on Drive, OneDrive, or Dropbox. (On YouTube, recordings upload directly to the channel rather than a folder tree.) A meeting Jane Smith hosted on June 4 lands at Your folder / Jane Smith / 2026 / 2026-06-04-Board meeting, the same layout described in our account-wide archiving post. That folder belongs to whoever authorized it — the admin's Google, Microsoft, or Dropbox account — not to RecordFlow; we upload into it and never read from it again afterward. Under GDPR, that split is explicit: the admin's organization is the data controller for the recordings being archived, and RecordFlow is the processor acting on the controller's documented instructions, per Article 28. Our full processor obligations and sub-processor list are in the DPA linked above.

How RecordFlow fits

None of this is unusual for RecordFlow specifically — it's the shape any tool should take when it's handling recordings on behalf of people who never installed it themselves. We built the admin-managed app assuming a security reviewer would eventually ask these exact questions, and wrote this post instead of waiting for that email. None of the verification above changes what running RecordFlow day to day feels like: enrollment is still a toggle, archiving is still automatic once it's flipped, and nobody on the team has to think about it again. If your organization is evaluating RecordFlow for account-wide archiving, migrating off scattered individual installs, or archiving a multi-instructor academy's recordings alongside a storage cleanup, the same guarantees on this page apply everywhere in the product — nothing here is a special case written just for this post.

An instructor who taught your Tuesday cohort for two semesters gives notice. Before their Zoom access is deactivated, someone on your team is supposed to make sure every session they recorded is somewhere safe — except nobody ever set that up, because it was never anyone's explicit job. You find out it didn't happen the day a student asks for a session from three months ago and the recording is nowhere to be found.

For a training academy, multi-instructor institute, or online college running courses across a faculty roster, the recorded session library isn't a courtesy — it's the product students enrolled for. And it's scattered across as many Zoom accounts as you have instructors, which means it's only as reliable as the least organized person on your roster.

What's actually happening

Zoom cloud recordings belong to the host who recorded them, live in that host's account, and count against a single storage pool shared across your entire Zoom account, sized by your plan and licensed-user count. Nothing about that model changes because five, ten, or thirty instructors are recording into it instead of one person. It just means the pool fills faster, from more directions, and no single instructor can see the whole picture — only the account admin can.

That creates two separate problems for a coordinator running an academy instead of a solo practice. First, storage: one instructor running back-to-back sessions can push the whole account toward its cap, and once it's full, Zoom stops saving new cloud recordings for every host on the account — not just the instructor who filled it. A student in a completely unrelated cohort can lose access to recording because someone they've never met ran an extra office-hours call.

Second, and less obvious until it happens: continuity. When an instructor leaves, deactivating their Zoom account doesn't offer any way to hand off their recordings — that option only shows up if you remove the user entirely, and even then, transferring their cloud recordings to another licensed user is a checkbox the admin has to select on purpose, not something that happens on its own. Miss that step, or simply deactivate instead of remove, and every session that instructor ever recorded is now only as durable as whether anyone remembered it during a busy offboarding.

Both problems come from the same gap: Zoom's storage model is built to hold one host's recordings, but a training academy needs one institutional archive that survives any single instructor coming or going.

How to archive recordings across a multi-instructor academy

1. Install the admin-managed app once, as the Zoom account admin or account owner — not per instructor. This is the version built for exactly this shape: one person authorizing on behalf of the whole account, rather than every instructor separately connecting their own Drive.
2. Connect one Google Drive folder as the archive root. Every instructor's recordings land in sub-folders under that single root, so the library lives in one place your institution controls — not in fifteen instructors' personal Drives.
3. Enroll your instructors from the admin dashboard. New members can be archived automatically by default, or you can leave that off and add instructors deliberately as they onboard — either way, an instructor never has to do anything on their end beyond recording as usual.
4. Let each instructor's sessions land in their own named sub-folder, dated and organized the same way underneath the shared root, so "last month's Module 4 replay from the Thursday cohort" is a lookup, not an investigation across several people's Zoom accounts.
5. Toggle an instructor off — don't wait for an offboarding checklist item to be remembered. Because the archive lives in your Drive from the moment each session finishes, a departing instructor's prior recordings are already safe; you're only deciding whether their future sessions keep flowing in.

What to check if a recording didn't archive

How RecordFlow fits

RecordFlow's admin-managed app is the version an academy coordinator installs: one authorization on behalf of the Zoom account, one Drive folder as the archive root, a sub-folder per instructor underneath it. You pick who's enrolled from a dashboard, and each instructor's sessions — video, audio, chat, and a clean Google Doc transcript — start landing automatically within minutes of Zoom finishing each recording, with no separate sign-in or setup required from the instructor. We store each instructor's name, email, sync status, and archive history needed to run the enrollment — see our Privacy Policy for the full account-level list — and the recording itself streams straight from Zoom to your Drive without ever being stored on RecordFlow's own infrastructure in between. As with any admin-managed archive, let instructors know their sessions are being archived to your Drive — a line in onboarding covers it.

Because a shared sync budget covers the whole account on every run, RecordFlow processes whichever enrolled instructor has waited longest since their last archive first — so an instructor teaching several sessions a day doesn't repeatedly crowd out a colleague who only teaches once a week. Nobody's cohort recordings get starved because someone else on the roster records more.

The same archive layout composes cleanly with the two content patterns an academy typically runs — an ongoing one-to-one tutoring roster for individual sessions and a cohort or course library for group classes — both landing in the same instructor-scoped archive, so a coordinator running both formats doesn't need two separate systems. And if Zoom's own storage-side tools are also part of your cleanup routine, our admin storage-management guide covers what those can and can't do on their own.

For an instructor teaching several recurring cohorts at once, Group recordings by series adds one more layer inside their own sub-folder: every session that shares a class name in its meeting topic collects into one folder automatically, so "last Thursday's Cohort 3 replay" is a single folder, not a search across that instructor's whole archive. It's off by default — the linked docs above cover how to turn it on — and it only shapes future syncs, so nothing already archived gets reorganized.

You've got months of client sessions, workshops, or cohort calls sitting in Zoom Cloud. They're recorded, they're technically "saved" — and they do nothing for you. You can't search across them, you can't hand one to a teammate to summarize, you can't cut a highlight reel from one. A recording in Zoom Cloud is a file Zoom is holding, not a tool you can use.

The fix isn't a new app. It's moving the recording — and its transcript — one layer over, into Google Drive. The moment they're there, three Google tools can reach them: Docs for a readable transcript, Gemini Notebook (formerly NotebookLM, renamed in July 2026) for asking questions across many sessions at once, and Vids for turning footage into an edited clip. Docs and Gemini Notebook work with any Google account; Vids' ability to open an existing Drive video for editing needs an eligible Workspace plan (more on that below). This post is the ecosystem overview — what each tool actually does with a recording once it's in Drive, and where to go for the deeper how-to on each.

Why Zoom Cloud can't do any of this

Zoom Cloud is built to notify you a recording is ready, not to feed it into anything else. None of Google's tools read a Zoom Cloud URL directly — not Docs, not Gemini Notebook, not Vids. They read files in Drive. So the first move, before any of the workflows below are possible, is getting the recording out of Zoom's silo and into a Drive folder you control. If you haven't set that up yet, the companion how-to on backing up Zoom recordings to Google Drive automatically covers the 60-second setup, and the Zoom Cloud vs Google Drive comparison makes the case for why Drive is the better long-term home in the first place.

Once a recording and its transcript land in Drive, they stop being a Zoom artifact and become an ordinary file — which is exactly what makes the rest of this work.

Three things you can do once a recording is in Drive

1. Read it — a clean transcript in Google Docs

Zoom's own transcript is a raw .vtt caption file: cues just a few seconds long, no paragraphs, timestamps on every line. It's built for video players, not for reading, and none of the tools below will touch it directly.

The fix is a readable version. RecordFlow uploads each transcript into Drive twice — the original .vtt, and a native Google Doc with cue numbers stripped, consecutive lines from the same speaker merged into paragraphs, and a rounded timestamp plus bolded speaker name at the start of each one. That Doc is what makes the transcript searchable in Drive search, skimmable on its own, and downloadable as a Microsoft Word file in two clicks (File → Download → Microsoft Word) if you need to hand it to someone who isn't in your Drive.

The full walkthrough — what Zoom's .vtt actually contains and why the raw file breaks every downstream tool — is the companion deep-dive on converting Zoom transcripts to Google Docs.

2. Ask it questions — Gemini Notebook across many sessions

Gemini Notebook — Google renamed NotebookLM to Gemini Notebook in July 2026; same product, same URL, new name — takes Google Docs, Slides, PDFs, and a handful of other source types from Drive and lets you ask questions grounded in exactly those documents, with citations back to the source. Point it at a stack of transcript Docs — a quarter of coaching calls, a cohort's worth of class sessions — and you can search across sessions instead of re-watching them one at a time. Gemini Notebook cannot read a raw .vtt or a Zoom Cloud link; it needs the Doc version sitting in Drive, which is the artifact from workflow #1. Setting up a notebook, source limits, and what a good prompt looks like is covered in full in the companion deep-dive on Zoom transcripts and Gemini Notebook — that's the one to read next if this is the workflow you want.

3. Cut it — turning footage into a clip with Google Vids

Google Vids is Google's browser-based video editor, and it works directly against files already in Drive: open a recording from Drive and choose "Open with Google Vids," and the clip drops straight into a new project as the first scene, ready to trim, reorder, or combine with other footage — no download-then-reupload step (Google's guide to editing Drive videos in Vids). That's the workflow for pulling a five-minute highlight out of an hour-long workshop recording, stitching together the best moments from a multi-session cohort, or turning a client testimonial call into something shareable. This specific capability — opening an existing Drive video straight into Vids — requires an eligible Google Workspace plan, and individual clips inserted this way are capped at 35 minutes and 4 GB (Google's Vids getting-started guide), so check your plan's access before you build a workflow around it. For anyone already on a qualifying Workspace plan, the ability to edit is already sitting on top of whatever RecordFlow has archived, no separate upload required.

What this doesn't require

None of the three workflows above need the recording reorganized first. RecordFlow groups recordings into year folders and names each meeting folder with the date and topic — that's enough to find the right session by eye or by Drive search, and Gemini Notebook and Vids both let you pick individual files as sources regardless of where they sit in the folder tree. Don't rename the meeting folders, though: that date-plus-topic name is what disambiguates "which session was this?" once you're three files deep in a Gemini Notebook source picker or a Vids project.

How RecordFlow fits

RecordFlow isn't an AI tool, and it doesn't try to be Docs, Gemini Notebook, or Vids. Its job is narrower and more mechanical: sign in with Zoom, connect Drive, pick a folder — about 60 seconds — and from then on, the moment Zoom marks a recording ready, RecordFlow copies the video, audio, chat log, and transcript into that folder, transcript included as both the raw .vtt and a readable Google Doc. How much of what's already sitting in Zoom Cloud comes along is your call: the Archive history setting starts at the past month, so your Drive isn't flooded on day one, and widens to 6 months, 2 years, or a full 10 years whenever you want — backfilling the newly-included sessions as soon as you widen it. Everything past that point is Google's tools reading files you already own in a folder you already control. RecordFlow is the plumbing; what you build on top of it is up to you.

If your team's Zoom recordings already back up automatically, there's a good chance it's because a few people signed up for RecordFlow on their own — each one connecting their own Google Drive individually. That's exactly how RecordFlow started: one person signs in with Zoom, connects Drive, and their own recordings archive automatically from then on. It works well for that one person. For a team, though, it isn't really one archive — it's as many separate ones as you have installs, and as the person who runs your team's Zoom account, you have no way to see who's actually covered.

What's actually happening

RecordFlow's individual app was built for exactly that: one person archiving their own recordings. For a long time it was also the only way in — the admin-managed app that lets one admin install once and cover the whole team is newer. If your team adopted RecordFlow before that existed, or before anyone noticed it had shipped, each member who wanted a backup had to sign up individually and connect their own Google Drive — and that's likely the setup you're still running today.

The individual app never gave you, as the Zoom account admin, any visibility into who was actually covered. Each person's archive lives in a Drive only they control. Zoom's own account-wide recording view — Account Management → Recording and Transcript Management — shows you every cloud recording still sitting in Zoom's own storage, searchable by host, but it says nothing about which of those hosts already has a personal RecordFlow backup running and which doesn't. That gap doesn't live in Zoom's admin tools; it lives in the fact that each install is a separate, personal connection you were never part of.

The result compounds quietly. A new hire never gets around to signing up. Someone leaves the team, and their personal archive — tied to their personal Google account — goes with them, whether or not you knew it existed. Six months in, "our recordings are backed up" is true for some fraction of your team, and you can't say which fraction without asking everyone individually.

Signs your team has fragmented installs

• You can name who definitely signed up for RecordFlow, but not who didn't — there's no roster, just word of mouth.
• Recordings are scattered across as many personal Google Drives as you have team members, instead of one place you can point a new hire to.
• Someone leaving the team is also, quietly, an archive leaving the team — nobody transferred ownership because nobody knew there was anything to transfer.
• You've fielded some version of "do I have to sign up for this myself?" more than once.

How to fix it

1. Install RecordFlow's admin-managed app once, as the Zoom account admin. That replaces asking each member to sign up individually. Zoom shows you exactly what it's granting on install: read-only access to see who's on the account and to read recordings — no write, no delete.
2. Connect one Google Drive folder. Use your own, or a Shared Drive the organization owns if you want the archive to outlast any single person's Google account. This becomes the archive root for the whole team.
3. Enroll members from the admin dashboard. New members are enrolled automatically by default, so once Drive is connected, coverage extends to your whole roster without a single member having to do anything. Notice what's missing here: you never have to connect any individual member's Google Drive by hand — the toggle does it for the whole roster at once. Prefer to add people yourself instead? Turn off Automatically enable new members and enroll individually.
4. Confirm the first few recordings land. Check each member's sub-folder under the archive root, then stop thinking about it — new recordings file themselves the same way going forward.
5. Retire existing individual installs. Switching to the admin app doesn't reach back and merge recordings anyone already archived through their personal install — those stay exactly where they are. But once the admin-managed archive is confirmed covering someone, there's no reason for their individual install to keep running in parallel. To remove it, have each member go to Zoom Marketplace → Manage → Added Apps, find RecordFlow - backup recordings to Google storage, and remove it — that disconnects their personal Google Drive without touching the admin-managed archive you just set up.

Enrollment is admin-controlled and reversible either way — a member's recordings only start flowing to your Drive once the admin has them switched on, and any member can be switched off without touching anyone else's archive.

What to check if coverage still looks patchy

One install replaces however many individual ones your team has accumulated, with a single dashboard that shows every member's enrollment status and last-archived time in one place — a sub-folder per member, so nobody's recordings get mixed together. If storage pressure is what pushed the team toward backups in the first place, account-wide storage management covers the other half of that problem.

A student emails halfway through week six: "Can I get the replay from Module 3? I was traveling and missed the live call." You go looking, and the Zoom recordings list has forty session titles that all say some variant of "Cohort Call" with a timestamp, no module numbers, no way to tell which one was week three without opening each and scrubbing to the intro. For a course creator, that's not a minor annoyance — the recorded library is the product a student paid for, and "I'll have to get back to you" is not the answer anyone wants to send mid-cohort.

What's actually happening

Zoom Cloud is built around a single meeting, not a growing library. Every session you record adds a file against your account's cloud storage — 10 GB per licensed host on Zoom Pro or Business, pooled at the account level. A weekly one-hour live call for an eight-to-twelve-week cohort, run at typical HD compression, can chew through a meaningful slice of that pool before the course even wraps — faster if you run office hours or a Q&A call alongside the main session, or if you're teaching more than one cohort in parallel. Once the pool is full, Zoom stops saving new cloud recordings for the whole account until you clear space or pay for an add-on — which, mid-cohort, means the risk isn't losing an old file, it's failing to capture this week's live call at all.

There's a second problem that shows up the moment a student tries to watch instead of you trying to store. If your account has "require authentication to view cloud recordings" turned on, a Zoom share link demands a Zoom login before it plays — and a student who enrolled through your course platform, not through Zoom, often doesn't have one and doesn't want to create one just to watch a replay. Even with that setting off, Zoom's recording list has no concept of "Module 3 of a 10-module course" — it's a flat list of meeting titles and dates, which is exactly why a support request like the one above takes longer than it should.

Both problems come from the same mismatch: Zoom treats the recording as a notification you've already acted on, while a course needs it to become a permanent, browsable library.

How to save your course recordings to Google Drive

1. Turn on cloud recording for every instructor who teaches a session, not just the account owner — Zoom Settings → Recording, Cloud recording toggled on per host. A co-facilitator recording locally to their own laptop is invisible to any backup automation, and invisible to you the moment their machine is unavailable. Say once, at enrollment, that live calls are recorded — most course terms of service already cover this, and it's worth a line in yours if not.
2. Pick one Drive folder as your course archive, and put the cohort and module in each Zoom session's meeting topic. Title the Zoom meeting Spring 2026 — Module 03 — Pricing (cohort name, then module number, always two digits). Backup automation carries that topic straight into the session's folder name inside your one connected Drive folder, so 2026-07-22-Spring 2026 — Module 03 — Pricing reads the way a student thinks about the course, not the way Zoom's flat meeting list does. RecordFlow syncs to a single destination folder per account — if you run several cohorts at once, they land in that same archive by default, and the cohort name in the topic is what keeps them identifiable, not a separate folder per cohort. If you'd rather each cohort collect in its own folder automatically, RecordFlow can group sessions by class: name the topic Spring 2026/Module 03 — Pricing (cohort before the slash), and every future session sharing that exact cohort prefix lands together in one shared folder instead of the undivided archive. It's off by default — the linked docs above cover how to turn it on.
3. Connect an automation that copies each session into that Drive folder the moment it's ready. Doing this by hand — download from Zoom, rename, upload to Drive, repeat every week for every cohort you're running — is the step that quietly slips during a launch week or a busy module. RecordFlow does this automatically once you connect Zoom and Drive, and files land within minutes of Zoom finishing processing.
4. Share the relevant session folders directly, not a Zoom link. Google Drive's "anyone with the link can view" sharing opens on any device with no sign-in required — the same way a student already opens a shared doc or a linked resource inside your course platform. Running a single cohort, share your whole connected Drive folder once at kickoff. Running several cohorts through the same archive, share each session's dated subfolder individually instead, so one cohort's students aren't looking at another cohort's replays. Drop the link into your course platform's module page (Teachable, Kajabi, Podia, or your own site all support linking out to an external URL) and the replay is one click away, no Zoom account needed — nothing new for a student to learn, since it's the same click they already use for every other resource on that page.
5. Turn on RecordFlow's auto-delete once Drive backups are confirmed. It's an opt-in switch that only clears a session from Zoom after the Drive copy is verified, with a three-day grace period built in — safer than Zoom's own retention policy, which runs on a fixed schedule regardless of whether a backup ever actually succeeded. Either way, the shrinking Zoom pool means next week's live call is never at risk of failing to record.

What to check if a session recording goes missing

How RecordFlow fits

RecordFlow connects your Zoom account to a Google Drive folder once — about 60 seconds — and from that point on, every live session lands there automatically: video, audio, a chat log, and a clean Google Doc transcript with timestamps and speaker labels, so a student can search a session instead of scrubbing an hour of video to find the five minutes on pricing that mattered. Once a session is in Drive, it's a normal folder, yours to reorganize the same way you organize anything else there — nest it into a per-cohort subfolder, move it into a shared folder scoped to one group of students, rename it — the kind of access control and clean, per-course structure Zoom's flat recordings list was never built to offer.

It works the same whether you're running one small cohort or several in parallel — the same automatic-backup pattern that works for a per-cohort group coaching program or an ongoing tutoring roster applies directly to a course library, and if a co-instructor connects their own account, their sessions land automatically too — no chasing anyone to download and re-upload their own recordings. RecordFlow never keeps a copy of the recording on its own infrastructure; the file moves straight from Zoom to the Drive folder you already own.

If you're weighing Drive against staying on Zoom Cloud for the full library, the Google Drive vs Zoom Cloud comparison lays out the cost and retention math side by side — and if a student ever tells you a link won't open, the share-without-a-Zoom-account fix covers exactly that case in more detail.

If your team backs up Zoom recordings to Google Drive at all, here's the question worth asking before you trust that archive: whose Drive? If the honest answer is "whoever hosted the call, into their own personal My Drive," the archive isn't really an archive. It's a folder someone else can take with them, forget the password to, or accidentally leave out of the next reorg's file-sharing pass. The fix isn't a better backup habit — it's a different kind of Drive folder, one the organization owns instead of any one person, and a way to save every member's recordings to it automatically.

Why personal Drive backups don't hold up for a team

A file dropped into someone's My Drive belongs to that person's Google account, full stop. That's fine for a solo coach archiving their own sessions. It breaks down the moment a team is involved: each member's recordings land in a different personal Drive, so there's no single place to look, no consistent folder structure across members, and no guarantee the files survive whatever happens to that person's account.

Google is explicit about this distinction for its own Shared Drives feature: "files in shared drives belong to the team instead of an individual," and when someone leaves the organization and an admin removes their account, files they added or created in a shared drive stay right where they are — visible and accessible to the rest of the team (Google Workspace Admin Help). My Drive doesn't offer that guarantee; ownership transfer is a manual step someone has to remember to do before an account is closed, and it's an easy one to miss during an offboarding rush.

For a small org — a coaching collective, a faculty, an agency, a nonprofit running cohort programs — that gap is exactly where recordings go missing. Not because Zoom deleted them, but because they were never in a place the organization controlled to begin with.

How to back up team Zoom recordings to a Shared Drive

1. Create the Shared Drive. In Google Drive, choose Shared drives → New, name it something a new admin would understand at a glance (Team Recordings, 2026 Session Archive), and add the people who should have standing access. Shared drives are available on Google Workspace Business Starter and up, plus Education and Nonprofits editions — though Business Starter can't configure sharing restrictions on its shared drives the way Standard and up can, so check your plan's controls before you rely on them. A personal Gmail account with no Workspace subscription won't see the option at all (Google Workspace Admin Help).
2. Set member roles deliberately. Shared drives support five access levels — Viewer, Commenter, Contributor, Content Manager, and Manager — so you can give most of the team Contributor access (they can see and add files) while reserving Manager for whoever owns the archive long-term.
3. Point your Zoom-to-Drive automation at the Shared Drive, not a personal folder. If you're using RecordFlow as the account admin, the Drive-connection step lets you pick any folder in either My Drive or a Shared Drive as the archive root — select the Shared Drive you just created.
4. Enroll members from the admin dashboard. Once the archive root is a Shared Drive, every member you enroll gets the same sub-folder treatment as before — one folder per member, named after them — except now that whole structure lives inside a Drive the org owns, not any one person's account.
5. Confirm the first few recordings land correctly, then let it run. New recordings continue to file themselves into each member's sub-folder inside the Shared Drive, automatically, as Zoom marks them ready.

What to check if recordings aren't landing in the Shared Drive

How RecordFlow fits

RecordFlow's account-wide admin app already lets you pick any Drive folder as the archive root — a Shared Drive works exactly the same way a personal folder does. One install, one Shared Drive, a sub-folder per member, and every recording lands there automatically within minutes of Zoom marking it ready — no one has to remember to move files out of their own account. If you haven't set up the account-wide archive yet, Archive Every Zoom Recording Across Your Account covers the full admin install; this post is specifically about pointing that archive at a Shared Drive instead of a personal one so the files stay with the org, not the person.

If you're archiving your own recordings rather than a whole team's, the individual backup guide and the Drive vs Zoom Cloud comparison cover that path — and if your team is a tutoring institute or training academy specifically, saving session recordings to Drive walks through the per-student or per-cohort version of the same idea.

Zoom storage management for admins usually starts the same way: the storage alert lands in your inbox, not the host's. Zoom's cloud recording pool for the account is almost full, and as the admin, that's now your problem — except the storage was filled by dozens of people you don't supervise minute-to-minute. You have no idea which of them is actually responsible. You open the account and start guessing.

You don't have to guess. Here's how to find out who's using the pool, what Zoom's own admin tools let you do about it today, and why the triage never really ends until you change what fills the pool in the first place.

What's actually happening

Zoom's cloud recording storage isn't allocated per person — it's pooled at the account level, with each licensed user contributing an allowance based on your plan (our plan-by-plan storage breakdown has the exact numbers). Whoever fills the pool doesn't have to be whoever gets the alert: Zoom emails the billing admin once usage hits 80% of the account's storage limit, and again when the limit is reached — regardless of which of the account's hosts drove the number up. If you're the admin but not the billing contact, you may not even see that first email; ask whoever holds that role to forward it, or check the usage report directly instead of waiting for a warning.

Once the pool actually fills, the blocking is account-wide, not per-host: no member can start a new cloud recording until storage is freed or increased, even if their own usage is trivial. One heavy recorder — a training team running daily sessions, a faculty member who never deletes anything — can lock out recording for everyone else on the account.

How to fix it: managing Zoom's cloud storage across your whole account

1. Find out who's actually using the storage. Go to Account Management → Reports → Cloud Recording in the Zoom web portal. The report graphs cumulative storage over a window and breaks the total down by host, so you can see exactly which members are driving the number instead of guessing from the alert alone. Standard accounts can pull up to a 30-day window within the past 6 months — enough to spot a pattern, not a full account history.
2. Search and clear specific recordings. Account Management → Recording and Transcript Management → Recordings tab is the account-wide view of every cloud recording on the account, searchable by host, date range, meeting topic, and even transcript keywords, with a CSV export of the results. From there you can delete recordings you've already confirmed are backed up elsewhere — the same "verify before you delete" discipline applies here as it does for an individual clearing their own storage, just at account scale.
3. Set an auto-delete policy, and narrow who can record to the cloud. The same admin settings let you configure an automatic deletion window for cloud recordings past a certain age, and restrict cloud recording access to only the groups that actually need it instead of leaving it open account-wide.
4. Don't skip the offboarding step. When someone leaves and you deactivate or delete their Zoom user, transferring their cloud recordings to another licensed user is a deliberate, opt-in choice you make during that deletion flow — it does not happen automatically, and the receiving user has to be licensed to accept it. Skip that step in the rush of an offboarding checklist and whatever that person recorded is no longer something you can easily account for.
5. Buy more storage, if you have to. It works, but it's the same recurring line item every solo user faces, scaled up by however many hosts are on your account — and it doesn't change how fast the pool refills.

Every one of these is a real, working option. None of them is a one-time fix. The report, the deletion pass, the offboarding checklist — they're all things you have to keep doing, because nothing stops the pool from filling again the moment you stop watching it. (The rest of the Zoom storage & retention guides cover the individual-user side of the same problem, if members ask you how to keep their own recordings once you tighten the account, and the Admin/IT guides cover the account-wide archiving and consolidation moves that go beyond storage cleanup.)

How RecordFlow fits

RecordFlow's admin-managed app does the one thing Zoom's own tools don't: it moves recordings out automatically, the moment each one finishes, so nothing needs a manual export. Install it once as the account admin and connect a folder on the storage you already run — Google Drive, OneDrive, or Dropbox, so IT admins standardized on Microsoft 365 aren't forced onto Google Drive just for this. New members are archived automatically unless you turn that default off, and any individual member can be toggled off without touching anyone else's archive. RecordFlow gives each member their own sub-folder under that root, and recordings stream straight from Zoom to your storage — we never store the bytes on our infrastructure in between.

Archiving on its own doesn't shrink Zoom's storage pool — the archived copy and the copy in Zoom's cloud are two separate things until you remove the Zoom one. That's what auto-delete is for: a separate, account-wide toggle in Settings, off by default, that clears a recording's Zoom copy only after its backup is confirmed. Turn it on once and the pool stays low on its own; leave it off and RecordFlow still saves you the manual export, but Reports → Cloud Recording will keep climbing until you clear things yourself.

Because the archive lives in storage you control, not the departing member's Zoom account, a recording a former team member made stays exactly where it landed — whether or not anyone remembered to run the transfer step during offboarding. (If you're trying to pull scattered recordings back together after the fact, consolidating a team's Zoom recordings into one admin-controlled archive covers that cleanup directly.)

Putting a number on it before the next renewal

Storage triage has a cost you can measure and a cost you can't: the add-on tier on the invoice, and the afternoons. The first one is worth pricing explicitly before you renew, because Zoom's own published add-on rates — $0.33 per GB per month at the entry tier, $0.10 at 1 TB, $1.50 for spilling past a small tier instead of upgrading — are high against every alternative. A drive plan the organisation already pays for is usually the cheapest answer; object storage the organisation owns is the one that keeps being the cheapest answer as the archive grows. The full comparison, with current list prices, also covers the part that decides whether any of it lands on the invoice: archiving alone doesn't reduce a Zoom bill, archiving and then clearing does.

The Zoom recordings your team makes aren't really yours. Each member's account holds their own copies — so when someone leaves the org, the recordings leave with them. The board minutes from the director who changed roles last quarter? Gone with their account. The training your senior coach delivered before parental leave? Same. Owning a Zoom account on behalf of a team means the archive is scattered across other people's accounts, and you usually don't notice until something you need is already gone.

Zoom's cloud isn't built to be that archive, either. If your account has a retention policy, recordings age out on a schedule someone set; if it doesn't, they pile up against a storage quota you pay to keep expanding. Either way, the recordings your org depends on are sitting somewhere temporary.

The fix isn't more Zoom storage — it's a single Google Drive folder you control, with every member's recordings landing in a sub-folder named after them, automatically, within minutes of Zoom finishing each recording.

Why we built an admin-managed version

RecordFlow started life as an individual tool. A coach signs in with Zoom, connects Drive, and their own recordings start backing up to Google Drive automatically. That works for a one-person practice — and it's what most of our users do. But for a team, the model fell apart. Each member had to install separately and connect their own Drive separately. The org had no view of who was archiving and who wasn't. The recordings landed in fifteen different Drives owned by fifteen different Google accounts.

So we built an admin-managed version — same product, same code, same archive layout — installed once by the Zoom account admin instead of by each member individually. The admin authorizes for the whole account, picks a single Google Drive folder as the archive root, and chooses which members to archive from a dashboard. The individuals don't have to do anything. The recordings still belong to the people who created them — each member gets their own sub-folder — but the archive belongs to the org. If a staff member leaves, their recordings stay where they are.

You don't have to figure out which version you need. Whether you run the Zoom account for a team or just want to archive your own recordings, start at our sign-in screen — it routes you to whichever flow matches your role.

How account-wide Zoom archiving works

You install once, as a Zoom admin. When you install, Zoom shows you what we're asking for: permission to see who's on your account, and permission to read recordings. That's it. No write, no delete.

You land on the admin dashboard. The first thing you see is a list of every active and inactive user in your Zoom account, each with an on/off switch. By default new members are enrolled automatically — connect Drive and their recordings start flowing. Prefer to add people by hand? Turn off Automatically enable new members, and new members arrive switched off until you enable them. Either way, you can toggle any individual member off whenever you want.

You connect a Google Drive folder you own — your personal Drive, or a shared Drive your team uses. That folder becomes the archive root.

With Drive connected and a member enrolled, the next time a meeting from that member's Zoom account finishes processing, Zoom tells us the recording is ready. RecordFlow looks up the member, confirms they're enabled, and streams the recording — video, audio, transcript, chat — into a sub-folder under your archive root named after that member. So a meeting Jane Smith hosted on June 4 lands at Your folder / Jane Smith / 2026 / 2026-06-04-Board meeting. The same naming scheme the individual app uses, just one level deeper to keep members separated.

Toggle a member off and their future recordings stop archiving — sibling members keep going as normal. The per-member switch is the only thing that decides what flows into Drive, so anyone whose recordings shouldn't be archived is one click from off (or leave auto-enroll off and add people deliberately).

The dashboard shows you, across the whole account, when each member was last archived. If another admin in your Zoom account installs RecordFlow, they see the same dashboard. You can pass the baton without losing visibility.

Security and scope

Plain English on what we ask for, because consent screens are the worst genre of reading. We ask Zoom for five read-only permissions: who's on your account (so you can pick who to archive), your admin profile (so we know it's you), and three for reading recordings — listing a member's recordings, listing the files inside each one, and reading those files. (The transcript rides along as one of those files.) No write, no delete, all read-only. And nothing leaves Zoom until you've connected a Drive folder to archive into — that's the archive's on-switch.

Every member shows up in the dashboard with a switch, and new members are enrolled automatically unless you turn that default off. We store name, email, the on/off toggle, and when we last archived them — nothing else. No photos, no phone numbers, no profile fields. The Drive files are owned by your Google account (or your shared Drive); we never see them again after the upload.

The most important guarantee, for the org's general counsel: when the last admin removes the app, everything goes. Zoom tells us the moment an admin clicks Remove. If other admins still have RecordFlow installed, we offboard just the admin who left — the account keeps running on the remaining admins. When the last admin removes it, we delete everything we hold for the account — tokens, every member, every record of past syncs — within seconds, and email that admin a confirmation. The Drive folder is untouched (it belongs to your Google account or shared Drive, not us). Removal is the cleanup.

GDPR, in plain terms

When you, the admin, install the admin-managed RecordFlow app for your organization's Zoom account, you become the data controller for the recordings being archived. RecordFlow becomes a processor. The admin-managed model makes the controller relationship explicit in a way the individual app doesn't — the org owns the archive, the org's admin decides who's enrolled, the org's Google Drive holds the files.

We've published a Data Processing Addendum for the processor relationship; the Privacy Policy and Terms of Use cover how the admin-managed model handles data and the install lifecycle.

Two things admins should think through before recordings start flowing. First: because new members are enrolled automatically by default, people can be archived before they've explicitly opted in — so they should know their meeting recordings are being archived to a folder you control. Zoom already tells participants a meeting is being recorded — that covers half of it. The new half: that the recording is being archived to your org's Drive. GDPR gives you a one-month window to tell people. A line in your meeting-recording policy, plus a heads-up in onboarding for new hires, covers it. Second: if your org has a Records Retention Policy, the archive folder is now in scope for it — the recordings live there as long as you decide they live there, not as long as Zoom's default retention dictates.

Pricing

Free during beta. We're using the beta to learn fast from organizations of every shape — coaching collectives, faculties, small Ops teams, nonprofits running cohorts. The broader the feedback now, the sharper the product gets before we settle on pricing. Pricing comes later, after we've earned the right to charge by being genuinely useful to a lot of different teams. Early adopters who stick with us through the beta will get founding-member pricing when we do introduce paid plans. The storage itself is your Google Drive, so the storage bill stays where it always was.

Install

Start from our sign-in screen — it routes you to whichever app matches your role. If you run the Zoom account for your team, the admin-managed version is the one you want.

Maybe you just got the "cloud recording storage is almost full" email, or you're staring at the admin Reports page trying to work out why one heavy recorder pushed the whole account toward the wall — or you're on Enterprise and want to confirm the "unlimited" claim against Zoom's own docs before you rely on it. Either way, the number underneath is more opaque than it should be: Zoom cloud storage limits aren't a flat number, they're a per-licensed-user allowance pooled across your whole account, except on Enterprise and Enterprise Plus, where there's no cap at all. How much storage does your plan actually give you, how is it calculated for more than one person, and what happens the instant it's gone?

What is Zoom's Enterprise plan cloud storage limit?

Unlimited. Zoom Enterprise and Enterprise Plus both include unlimited cloud recording storage — there's no per-licensed-user allowance, and because the figure is unlimited, there's no pool that can ever run out. That's a structural difference from the plans below Enterprise, not just a bigger number: Pro, Business, and Business Plus each grant a fixed amount per licensed user, which Zoom then pools across the account — so the ceiling still exists, it just scales with headcount. Enterprise and Enterprise Plus skip the per-license figure in Zoom's own plan table entirely, rather than listing a very large one.

In practice, that means an Enterprise admin never sees the 80%-full billing alert, never buys add-on storage tiers, and never has a new cloud recording blocked for lack of room. This unlimited allowance only applies to accounts actually provisioned on Enterprise or Enterprise Plus — every plan below it, including Business Plus at 15 GB per licensed user, still has a real, poolable ceiling, covered next.

How much cloud storage does Zoom actually give you?

Zoom doesn't assign your account a single flat number. Storage is granted per licensed user, then pooled at the account level:

That "per licensed user" detail is the part most people miss. Zoom pools the allowance across the whole account — a Business account with one licensed user gets a 10 GB pool; a Business account with 10 licensed users gets a 100 GB pool, shared by everyone who records to the cloud. It isn't 10 GB walled off per person; it's one shared bucket that scales with headcount, and anyone on the account can draw it down.

For a solo coach, consultant, or trainer on a single Zoom Pro license, that pooling detail doesn't change the number — you get 10 GB, full stop, the same as the account would get with just one license. It matters the moment you add a second license, a co-facilitator, or a training team: the pool grows, but so does the number of people recording into it. (If the cap itself sounds like the dealbreaker, it's worth first checking whether cloud is the right call for you at all — cloud vs. local recording walks through when each one wins.)

What happens when the pool runs out

Zoom warns before it blocks. The billing admin gets an email alert once usage hits 80% of the account's storage limit — the "almost full" email most people recognize. If nothing changes and the pool actually fills:

• A recording already in progress keeps recording until the meeting ends. Zoom doesn't cut off an active cloud recording mid-call.
• Once that meeting ends, no new cloud recording can start — for anyone on the account — until storage is freed or increased.

There's no per-meeting grace period and no soft warning in the moment you press Record. If the pool is full when you try to start a new cloud recording, it fails immediately. (If that's already happened to you mid-workday, the immediate fallback — local recording — and the safe cleanup sequence afterward are worth bookmarking separately from this post.)

The math that fills the pool faster than it looks

A single hour of HD Zoom recording runs a few hundred megabytes after compression. For a solo practitioner running 10 GB on Zoom Pro, a typical 10-15-sessions-a-week caseload adds up to several gigabytes of new recording every week — enough to fill the pool in roughly two to five weeks, not months. Longer sessions or heavier video settings shrink that window further.

Scaling up a team doesn't buy the relief it looks like on paper. Adding a fifth licensed user to a Business account moves the pool from 40 GB to 50 GB — but that fifth person is also recording into the same shared bucket, so the pool fills at roughly the same relative rate. Pooling spreads the allowance across more people; it doesn't stretch it further per recording. If you're the admin trying to work out who's driving that shared number, Zoom storage management for admins covers the per-host Reports view and the account-wide levers you actually control.

Paying Zoom for more room

Once the included pool is gone, Zoom sells additional cloud recording storage in fixed monthly tiers, billed on top of your plan and scaling from 1 GB up to multiple terabytes — check Zoom's current storage add-on pricing before you buy, since tiers and prices are billed separately from your base plan and can change. It's a legitimate option if you need the recording reachable inside Zoom itself for some specific reason. For most solo practitioners and small teams, though, it's recurring spend to keep files in a tool that was never built to be a long-term archive in the first place — the Google Drive vs. Zoom Cloud comparison walks through why that trade rarely favors Zoom once you look at cost per gigabyte.

The fix that keeps the pool from filling at all

The durable answer isn't a bigger pool — it's keeping the pool small by moving recordings out of it as soon as they're ready. RecordFlow does exactly that: connect it once (sign in with Zoom, connect the cloud storage you own — Google Drive, OneDrive, or Dropbox — pick a folder, about 60 seconds) and every cloud recording copies there automatically within minutes of Zoom marking it ready. RecordFlow never stores your recordings — files transfer directly from Zoom to your storage, so nothing sits on our infrastructure in between. Once a backup is confirmed, you can let Zoom clear its own copy on whatever schedule you choose and never buy an add-on tier. Running a small team instead of a solo practice? The same idea works account-wide: one admin connects once and archives recordings for every opted-in member into a shared folder root, so the whole pool stays small, not just one person's. The full walkthrough for setting up automatic Zoom-to-Drive backup covers setup end to end, including what to check if a recording doesn't show up. The rest of the Zoom storage & retention guides cover the neighbouring problems — what to do the moment recording is blocked, and how to delete safely once a backup exists.

What the add-on actually costs per gigabyte

Zoom's add-on tiers are easier to judge once you divide them out. The 30 GB tier at $10 a month is $0.33 per gigabyte per month; the 1 TB tier at $100 is $0.10; and spilling past a small tier instead of upgrading is billed at $1.50 per additional gigabyte. Those are high numbers for cold video — object storage starts at $0.023 per GB per month on S3 Standard and drops to well under a cent on cold tiers. The full side-by-side, with every list price checked and the one caveat that decides whether any of it lowers your bill, is in what Zoom recording storage actually costs.

A parent messages you Sunday night: can my daughter watch Tuesday's algebra session again before her test Thursday? You open the Zoom portal to find the recording — and it's already gone. Auto-delete kicked in, or the storage cap finally hit, or you just can't remember which of forty session titles it was. Either way, the session you ran is unrecoverable, and the message you have to send back is the one every tutor dreads: "I'm sorry, I don't have that one anymore."

For a tutor or a small teaching institute, a recorded session isn't a courtesy — it's the study material. Students replay it before a test. Parents ask for it after a missed lesson. A course coordinator points a new student at last month's sessions to catch them up. Losing one isn't an inconvenience; it's a broken promise to whoever paid for the seat.

What's actually happening

Zoom Cloud is built around the meeting that produced the recording, not the archive a tutoring business needs it to become. Once a session ends and processes, the file just sits there against your account's storage quota — 10 GB per licensed host on Zoom Pro or Business, pooled at the account level. A solo tutor is working with a single 10 GB pool; a small institute's capacity only grows as fast as it buys more licenses. Either way, a tutor running four or five one-hour sessions a day fills their share faster than it looks like it should, and once it's full, Zoom stops saving new cloud recordings until you buy an add-on or clear space. Institutes running an auto-delete policy for storage hygiene lose recordings even sooner — on a schedule that the student on the other end never sees.

There's a second problem that shows up the moment you try to share instead of store. If your account has "require authentication to view cloud recordings" turned on — common at institutes that lock things down by default — a Zoom share link demands a Zoom account before it'll play. A ten-year-old student, or a parent checking a lesson from their phone, doesn't have one, and doesn't want to make one. The recording exists; nobody can watch it.

Both problems trace back to the same root cause: the recording is living somewhere designed to be temporary, when the job actually requires it to be permanent and easy to hand off.

How to save tutoring session recordings to Google Drive

1. Turn on cloud recording for every tutor who teaches, not just the account owner — in Zoom Settings → Recording, Cloud recording must be toggled on per host. A session recorded locally to someone's laptop is invisible to any backup automation and to you the moment that laptop is unavailable. Mention once, at enrollment, that sessions are recorded — most tutoring agreements already cover this, and it's worth a line in yours if not.
2. Create one Drive folder per student, or per cohort if you teach group classes. /Students/Amara R/, or /Cohorts/SAT Prep — Summer 2026/ for a shared class. This is the structure that makes "can I get last Tuesday's session" a thirty-second lookup instead of a search through forty identically-named Zoom recordings.
3. Connect an automation that copies each session into the right folder the moment it's ready. Doing this by hand — log into Zoom, download, log into Drive, upload, repeat for every session, every day — is the step that quietly stops happening during a busy exam season. RecordFlow does this automatically once you connect Zoom and Drive.
4. Share the student or cohort folder directly, not a Zoom link. Google Drive's "anyone with the link can view" sharing opens on any device without a sign-in — the same way a parent already opens a shared photo album or a school newsletter link. No Zoom account needed on their end, ever.
5. Let Zoom's own retention policy do its job once Drive has the backup. Once you've verified a few sessions land safely in Drive, you can leave (or turn on) Zoom's auto-delete without worrying about losing anything — Drive is now the copy that doesn't expire.

What to check if a session recording goes missing

How RecordFlow fits

RecordFlow connects your Zoom account to a Google Drive folder once — about 60 seconds — and from that point on, every tutoring session lands there automatically: video, audio, a chat log, and a clean Google Doc transcript with timestamps and speaker labels, so a student can search a session instead of scrubbing through an hour of video to find the one explanation that mattered. It works the same way whether you're a solo tutor with a handful of regulars or a coordinator running an institute where each instructor needs their own folder — the same automatic-backup pattern that works for a per-cohort group program applies directly to a class or a tutoring roster. Once an instructor connects their own account, their sessions land automatically every week — no coordinator chasing anyone to download and re-upload their own recordings by hand. RecordFlow never keeps a copy of the recording on its own infrastructure; the file moves straight from Zoom to the Drive folder you already own.

If you're weighing whether Drive is even the right destination for teaching recordings versus staying on Zoom Cloud, the Google Drive vs Zoom Cloud comparison lays out the cost and retention math side-by-side — and if you're running a nonprofit tutoring program, Workspace for Nonprofits may already give you far more free Drive storage than you're using.

Your client — or a student who missed a session — is asking for last week's recording, or just its transcript, before Zoom clears it out. So you go to grab your own copy and realize you're about to do this one file, one click-through, one meeting at a time — and that's before you count how many others are already sitting behind a shrinking storage quota.

There are two ways to get your own recordings and transcripts off Zoom's servers: work through the manual download flow Zoom provides, one meeting at a time, or set up something that copies each one automatically as soon as it's ready. Here's exactly how the manual path works, where it breaks down, and what the automatic alternative looks like.

What's actually happening

A Zoom cloud recording isn't a single file sitting in a folder — it's a processed set of files (video, an audio-only track, a chat log, and a transcript when your account has it enabled) that Zoom stores in your account and lists on the Recordings & Transcripts page in the Zoom web portal. Downloading is something you have to initiate yourself, per meeting, every time.

The portal's documented download flow is one recording at a time: open the meeting's recording page, click Download, confirm the prompt. There's no checkbox-and-download-all across multiple meetings in the portal — if you need many recordings at once, the practical alternatives are exporting a CSV of recording metadata, scripting against Zoom's recordings API, or automating the pull entirely rather than clicking through the web UI a dozen times over.

A couple of settings can also stand between you and the download button — see below for the two most common causes — and some accounts require a passcode to open a shared cloud recording link before a download can even start.

If you're still deciding whether cloud recording is even the right toggle to hit before your next call, Zoom Cloud Recording vs Local Recording walks through when each makes sense.

How to download your Zoom cloud recording

1. Sign in to the Zoom web portal and open Recordings & Transcripts in the left navigation.
2. Find the meeting and click its thumbnail to open the recording's page.
3. Click Download, then confirm in the prompt that appears.
4. Repeat steps 2–3 for the audio-only file, chat log, or transcript if you want those separately — each is downloaded from the same recording page.
5. Repeat the whole process for every other meeting you need. There's no multi-select across meetings in the portal.

That's the whole workflow, and it's exactly as repetitive as it sounds once you have more than a handful of recordings to move.

When the download button is missing

A missing or disabled Download button can mean two different things, and they need different fixes.

It's your own recording. If you own the recording (or co-hosted it) and the button still isn't there, it's a setting, not a bug — and one an admin can change. The same account settings page carries two toggles that both gate this: Cloud recording downloads, which can turn downloading off account-wide, and Only the host can download cloud recordings, which — when on — restricts the button to the host account specifically, so a co-host or someone the host shared the recording with won't see it even on their own account. Ask the meeting's actual host to download and forward the file, or ask an admin to check both settings.

It's a recording someone else shared with you. Open a link someone sent — a class replay, a webinar, a colleague's meeting — and whether you can download it isn't your call. Every shared Zoom cloud recording carries its own "Viewers can download" setting, which the host sets when sharing, separate from who's allowed to view it. If the host left that off, the button won't appear for you, and there's no way around it as a viewer — you'll need to ask the host to re-share with downloads turned on, or send you the file directly. This is also the one case RecordFlow can't help with: it archives recordings you host or that your organization owns, not a recording someone else controls and has chosen not to let you download. (If you're the one sharing and want people to be able to save a copy without them wrestling with Zoom's toggle at all, sharing a Drive, OneDrive, or Dropbox link instead sidesteps the setting entirely — the file just needs "anyone with the link" viewer access.)

Downloading a Zoom recording on mobile

No download button in the app. Zoom's download flow is documented as a web-portal action — there's no separate download feature built into the Zoom mobile app for iOS or Android. The app is still the easiest way to watch a cloud recording on your phone, from its recordings list. To actually save the file, open the recording's page at zoom.us in your phone's browser — Safari or Chrome — and use the same Download button as on desktop. Where the file lands is up to your browser, not Zoom: typically the Files app on iOS, or the Downloads folder on Android.

Mobile browsers make it clumsier. They sometimes try to play a large video inline instead of offering to save it, and a multi-gigabyte gallery-view recording is slow to pull over a mobile connection. If a recording is worth keeping, downloading it from a laptop — or not needing to download it by hand at all — beats fighting a phone browser for it.

Manual download vs. automatic backup

The manual flow above works fine for one recording. It's where it stops being fine that pushes most people toward automating the pull entirely:

• Large files. An hour of gallery-view video can run into gigabytes. Browsers time out or silently fail on big downloads over a flaky connection, and you often don't notice until you go looking for the file and it isn't where you expected.
• One at a time, always. Every recording is its own click-through. There's no "select these ten meetings, download them together" option in the web portal.
• The retention clock. Cloud recordings aren't permanent. Storage quotas fill up, and some accounts run an admin-set auto-delete policy that removes recordings after a set number of days. A recording you meant to download "later" can be gone — Zoom moves deleted recordings to a 30-day trash window, and once that window closes, a permanently deleted recording can't be recovered.

None of that is a reason to avoid downloading — it's a reason not to rely on remembering to.

How RecordFlow fits

RecordFlow replaces the manual loop with an automatic one: connect Zoom to your cloud storage once — Google Drive, OneDrive, or Dropbox, about 60 seconds — and every new cloud recording (video, audio track, chat log, and transcript) copies itself into a folder you choose within minutes of Zoom marking it ready, no click-through required. Large files, password-protected recordings, and long multi-hour calls all transfer the same way a short one does; if a transfer fails, it retries automatically. Recordings move directly from Zoom to your storage — RecordFlow never stores the files themselves. Once a recording is safely off Zoom's servers, you're no longer racing a storage cap or an auto-delete policy to grab it in time.

Once a recording is safely off Zoom's servers, our guide to the files a recording actually contains covers which one to send a client.

If it's the transcript you're really after — especially to feed it into an AI tool or knowledge base — downloading the .vtt is only step one. Turning it into a Google Doc your AI tools can read covers what to do with it next.

Deleting a Zoom recording is one click — it's the "can I undo this" part that's worth knowing before you press it. Maybe a client asked you to remove their session, or you're clearing space before the next call, and now you're hovering over the delete button wondering if you're about to lose something you can't get back. Zoom makes deleting a recording easy; recovering one you deleted by mistake is a 30-day countdown you might lose.

What's actually happening

Zoom draws a hard line between two kinds of recordings, and they don't delete the same way.

Cloud recordings live in Zoom's pooled cloud storage — 10 GB shared across licensed users on Pro and Business plans, 15 GB on Business Plus. Delete one and it doesn't vanish immediately: it moves to a Trash tab first, where it sits for up to 30 days before Zoom permanently removes it.

Files sitting in Trash don't count against your storage limit, so clearing Trash is actually a separate, second step from deleting the recording itself.

Local recordings — the ones Zoom saved straight to your computer instead of the cloud — work differently. There's no Zoom-side trash for these; deleting the file removes it the same way any other file on your machine does, and it's only recoverable from your own operating system's Recycle Bin or Trash, not from Zoom. Unlike cloud recordings, local files don't get auto-deleted on any schedule — they sit on disk until you or your OS removes them.

The distinction matters because the recovery paths are different, and the 30-day cloud window is shorter than most people assume when they're not the one who deleted it. Deleting on purpose isn't the only way a recording leaves Zoom, either — cancelling or downgrading your Zoom plan starts its own 30-day countdown on your cloud recordings. If you're not sure why a recording disappeared from your account in the first place, What Disappears From Zoom Cloud, and When covers the other three ways that happens.

How to delete a Zoom recording

A single cloud recording

1. Sign in at zoom.us and open Recordings & Transcripts in the left navigation.
2. Find the recording — by topic, date, or the "search text in transcript" field if you remember something said in the meeting but not the date.
3. Click the ··· (more) menu on that recording's row or tile and choose Delete.

This deletes the entire recording set for that meeting (video, audio, transcript, chat log together). If you only want to remove one file from a meeting — say, drop the chat log but keep the video — open the meeting's detail page, hover the specific file, and use its own trash icon instead of deleting the whole meeting.

Deleting multiple Zoom recordings at once

Need to delete Zoom recordings in bulk rather than one at a time? In list view, check the boxes next to each meeting you want gone, then click Delete Selected above the list. To clear everything up to a certain date, use Advanced Search with today's date in the "To" field, select all, and Delete Selected — useful for a seasonal cleanup rather than a one-off.

A local recording

Local recordings live in your Documents/Zoom folder (or wherever you set the save location) as normal video and audio files. Delete the meeting's subfolder like you would any other files, then empty your Recycle Bin (Windows) or Trash (Mac) if you want the disk space back immediately — until you do, the files are still recoverable from there.

Recovering something you deleted

Cloud: open the Trash tab under Recordings & Transcripts within 30 days of deleting and restore it — after that window it's gone for good. (On team accounts, an admin can disable the Trash tab entirely; if yours doesn't have one, deletions there are permanent right away — ask your admin if you're not sure.) Local: right-click and Restore from your Recycle Bin (Windows) or drag back out of Trash (Mac), same as any other file, as long as you haven't emptied it.

The one rule that makes deletion safe

Zoom's Trash window is a grace period, not a backup. The only way to delete with zero risk is to make sure a durable copy exists somewhere else before you delete anything from Zoom — back up, verify the copy landed, then delete. (For the wider picture of keeping Zoom's storage under control without losing anything, the Zoom storage & retention guides collect the rest of the playbook.) That's the same sequence the safe auto-delete pattern is built around, just done by hand instead of on a schedule. Google Drive won't clear files to free up storage on its own the way Zoom's pooled cloud storage does — files you don't move to Trash yourself just stay — which is why it's a common landing spot for anyone who wants recordings to genuinely stop being at risk once they're archived.

How RecordFlow fits

If you're deleting recordings by hand to make room, that's a sign the underlying problem — Zoom's storage filling up — is still there, and it's probably costing you a few hours a week in copy-then-delete busywork. RecordFlow backs up every cloud recording to the cloud storage you own — Google Drive, OneDrive, or Dropbox — automatically, within minutes of Zoom marking it ready, so that manual pass disappears entirely. If you want Zoom cleaned up automatically too, RecordFlow's opt-in auto-delete only clears a recording from Zoom once that copy is confirmed, then waits a three-day grace period before doing it — the "back up, verify, delete" rule above, running itself. See how to set up automatic backup if you'd rather stop deleting manually altogether.

Should you record Zoom to the cloud or your computer? You're about to click Record, and Zoom asks that exact question before you're ready for it: record to the cloud, or record on this computer? It's a client session, or the first class of a new cohort, and you don't want to find out you picked wrong after everyone's already logged off. Most people click whichever one they clicked last time and hope it was right.

It's worth ten seconds, because the two options aren't a UI preference — they produce a genuinely different asset with different capabilities and different risks.

What's actually happening

Cloud recording sends the meeting to Zoom's servers. Zoom processes it there and the finished video, audio-only file, and chat transcript show up in your account's Recordings page in the web portal — usually within a few hours, though Zoom notes processing can occasionally take up to 24 hours under heavy load. Cloud recording is available on paid plans — Pro, Business, Education, or Enterprise — not on the free Basic plan, and it can be started from the desktop app, the mobile app, or a Zoom Room. Because the file lives on Zoom's infrastructure, it's the only recording type that gets a shareable link straight from the portal, and it's the only one that can optionally generate an automatic audio transcript once an admin enables the feature. The tradeoff: cloud storage is pooled and capped — most Pro and Business plans include 10 GB per licensed user — and once an account is at the cap, Zoom blocks starting a new cloud recording until space is freed or the plan is upgraded.

Local recording (Zoom calls it "computer recording") writes the file directly to your machine — by default into a zoom folder inside Documents. It's available on every Zoom account, including the free Basic plan, and it produces the same file types cloud recording does (MP4 video, M4A audio, a chat text file) — there's just no server processing step and no portal entry. It only runs from the desktop app, not mobile, and there's no storage cap other than your hard drive. The tradeoff mirrors the cloud version's advantages exactly: no sharing link, no automatic transcript, and the file goes nowhere until you manually move it. An account admin can also disable computer recording entirely at the account or group level — if the option is greyed out in your toolbar, that's why.

How to decide

Should you record to the cloud, or keep it local? Run through these in order — the first one that applies usually settles it:

1. Are you on Zoom's free Basic plan? Cloud recording isn't offered at all — local is your only option, and it's a perfectly capable one for personal notes or session review.
2. Does the person you recorded for need a link, not a file? A client re-watching a session, or a student catching up on a missed class, expects to click a link. That link only exists for cloud recordings.
3. Do you want a transcript without extra software? Cloud recording's built-in audio transcription (once enabled by an admin) saves a step local recording can't replicate on its own.
4. Do you plan to back the recording up to Google Drive automatically? Automation tools — including RecordFlow — watch for a Zoom cloud recording to finish processing and copy it into Drive within minutes. There's no equivalent hook for a file sitting on a laptop; it has to be uploaded by hand.
5. None of the above, and you just want the file fast with zero cloud dependency? Local recording is lighter-weight and available the moment the call ends, with no processing wait.

For most coaches, consultants, tutors, and course creators — the readers who end up re-sharing a session, referencing it next week, or building a library students expect to revisit — cloud recording wins on points 2 through 4. It's also the only path that plugs into an automated backup, which matters because Zoom's cloud storage fills up faster than people expect once you're recording several sessions a week. If you're still getting oriented on how Zoom recording works, the rest of the Zoom recording basics guides cover where your files live and which of them to send, and the Zoom storage & retention guides cover the quota and cleanup side once you've picked cloud.

What to check if you picked wrong

How RecordFlow fits

RecordFlow only works with Zoom cloud recordings — it watches for a cloud recording to finish processing, then copies the video, audio, transcript, and chat log into a Google Drive folder you choose, usually within minutes. RecordFlow never stores your recordings — files transfer directly from Zoom to your Drive, so sensitive session content stays between you, your client, and Google. That's the strongest reason to pick cloud recording even if you don't care about the sharing link or the transcript: once a session is a cloud recording, it can leave Zoom's storage cap entirely and land somewhere with no cap and no auto-delete — without you touching a single file. If you've already decided cloud is the right call, the step-by-step setup guide walks through connecting Zoom and Drive in about 60 seconds, and the fuller Google Drive vs Zoom Cloud comparison covers why Drive is the better long-term home once the recording is there.

Tuesday's session had a real moment in it. The client named the thing they'd been avoiding, connected it to a pattern going back years, and left the call sounding lighter than they had in weeks. By Friday, when you check in, they remember that "something clicked" — but not what, and not why. The insight was real. It just didn't survive the week.

That's not a client being careless, and it's not a sign the session didn't land. It's what memory does to everyone, on a predictable schedule, unless something intervenes.

What's actually happening

Memory fades fast, and it fades on a curve, not a cliff. In 1885, Hermann Ebbinghaus ran the original experiments on how quickly newly learned material is forgotten without any reinforcement — the "forgetting curve" that still anchors research on retention today. A 2015 peer-reviewed replication of Ebbinghaus's experiment, published in PLOS ONE, reproduced the same shape: retention drops sharply in the first day and then levels off, with the replication showing roughly a fifth of the original learning still retained after 24 hours with no review in between.

A coaching session isn't a list of nonsense syllables, and a breakthrough usually sticks better than rote memorization — emotionally significant moments tend to be stickier than neutral ones. But the underlying mechanic is the same one behind the curve: without something to bring it back, the specifics of an insight — the exact words that reframed it, the connection the client made out loud — degrade fast, while the vaguer feeling of "that was a good session" survives. That's the gap between a client who says the session helped and a client whose behavior actually changed.

The fix Ebbinghaus's own data points to isn't "remember harder." It's reinforcement, spaced out over time — going back to the material before it fully fades, which resets the curve and makes the next fade slower. For a coach, the practical version of that is simple: give the client a way to return to the exact moment, more than once, between sessions.

How the replay helps

A session recording is a low-effort way to give a client that reinforcement, because it doesn't ask them to remember anything correctly on their own:

1. Re-watch the moment, not the whole hour. Most sessions have one or two minutes that mattered most. A client who can scrub straight to that clip on Wednesday night gets the reinforcement without re-listening to an hour to find it.
2. Re-read the transcript when video is overkill. Sometimes the client doesn't need to hear your tone again — they need to see their own words. A clean, searchable transcript lets them find the exact sentence that landed, faster than scrubbing video.
3. Return between sessions, not just after them. The forgetting curve doesn't wait for your next appointment. A client who hits a wall on day four of a seven-day gap can go back to the relevant minute right then, instead of arriving at the next call having half-forgotten what you were building on.
4. Repeat it without you in the room. This is the version of spaced repetition a coach can actually deliver: the client does the reinforcing rep on their own schedule, and you didn't have to build a separate exercise to make it happen.

None of this requires a client to be diligent about it. It requires the recording to exist, be easy to find, and be theirs to open whenever the moment resurfaces for them — which is also the argument for why a prospect should expect more from recorded sessions than from ones that vanish when the call ends.

How RecordFlow fits

The reinforcement only happens if the recording is somewhere the client will actually go back to — which is the same problem covered in the companion post on giving clients their session recordings: many Zoom accounts are configured to auto-delete cloud recordings after a set number of days, and even a recording that isn't on that clock yet is easy for a client to lose track of in an app they don't otherwise use.

RecordFlow closes that gap automatically. Once you connect Zoom and Google Drive — a one-time, roughly 60-second setup — every recorded session lands in a Drive folder you own the moment Zoom finishes processing it: the video, the audio file, the chat log, and a clean, readable transcript as a native Google Doc, alongside the raw .vtt file Zoom hands you. That transcript is what makes the "re-read the exact sentence" reinforcement fast instead of a video-scrubbing chore — the same conversion covered in the post on turning a Zoom transcript into a Google Doc. Because the folder is yours, you share the replay with that one client via a Drive link, and it's there waiting on day four of the gap — not sitting in a Zoom account whose retention policy might already have cleared it out by the time they think to look. RecordFlow also never keeps a copy of the recording on its own servers, which matters given how personal a coaching session can get.

You finish a session feeling good about it — the client had a breakthrough, the flow felt natural, your questions landed. Then, months later, you happen to watch the recording back. You interrupted twice in the first ten minutes. A silence you remember as "giving space" lasted four seconds before you filled it with a suggestion. The open question you were proud of was actually two closed ones stacked together. None of this matches how the session felt while you were in it.

That gap is normal, and it's exactly why reviewing your own recordings is worth the discomfort.

Why self-assessment is so hard for coaches

Self-perception during a live coaching session is unreliable, and not because you're a bad coach — it's because you're busy doing the thing, not watching yourself do it. You're tracking the client's words, your own next question, the thread from ten minutes ago, and the clock, all at once. There's no attention left over for an accurate read on your own talk time or question style.

This isn't unique to coaching. A systematic review of video-based self-assessment interventions among physicians found that self-assessment from memory was often inaccurate — both over- and under-estimating performance depending on the specialty. Watching the recording back improved self-assessment accuracy in just over half of the studies reviewed. The pattern tracks for coaches: you can recall the feeling of a session with real clarity. You can't recall the mechanics — how often you talked over the client, how many of your "open" questions had an answer baked into them, which silences you sat with and which you rushed to rescue. Those only show up on a replay.

It's also the ICF's own frame, not just a good habit. Sub-competency 2.3 under "Embodies a Coaching Mindset" — ICF Core Competency 2 — states that a coach "develops an ongoing reflective practice to enhance one's coaching." Reviewing your own sessions is one of the most concrete ways to actually do that, separate from anything related to a credential application.

A simple self-review routine

You don't need a formal process to improve as a coach — a short, repeatable routine beats an occasional deep audit you never get around to.

1. Pick one session a quarter, not every session. Reviewing everything is how this habit dies in week two. Choose one recent session — ideally one that felt average, not your best or worst — and give it a real 20–30 minutes.
2. Watch (or skim the transcript) for talk ratio first. Roughly, who talked more? A coaching conversation should tilt heavily toward the client. If you're consistently talking as much as or more than they are, that's the single highest-leverage thing to notice.
3. Count your questions, then sort them. How many were genuinely open ("what's underneath that for you?") versus closed-with-extra-steps ("do you think that's because you're avoiding the conflict?")? A question with the answer already in it isn't really a question.
4. Time the silences you rushed. Notice every place you filled a pause with a suggestion, a reframe, or your own words within a few seconds. Some of those pauses were the client doing real thinking — and you took the room away from them before they finished.
5. Write down one pattern, not ten. The point isn't a full audit. It's noticing the one thing you keep doing without realizing it, then bringing that single pattern into your next few sessions.

The transcript is what makes this fast instead of tedious. Scrubbing back and forth through 45 minutes of video to count questions is exactly tedious enough that most coaches never do it. Skimming a readable, timestamped transcript and Ctrl-F'ing your own name to see how much of the page is you talking takes a few minutes, not a rewatch.

How RecordFlow fits

RecordFlow doesn't do the reviewing for you — it just makes sure the raw material is always sitting there, ready, instead of automatically deleted under a Zoom retention setting or buried in Zoom Cloud by the time you'd actually sit down with it. The moment a Zoom cloud recording is ready, RecordFlow copies the video, audio, chat log, and transcript into a Google Drive folder you own, one folder per session. Alongside the raw .vtt, it uploads a clean Google Doc transcript — consecutive lines from the same speaker merged into readable paragraphs, each one timestamped and labeled with the speaker's name (the mechanics are in the transcript-to-Doc post). That's the version you skim for talk ratio and question count; the raw caption file is not.

Because every session lands automatically, "pick one from this quarter" is a real choice between several saved sessions rather than a hope that you happened to keep the right one. And because it's your Drive folder, the recording you're reviewing is the same copy you might later hand to a client (see the post on giving clients their session recording) or, on a different track entirely, submit toward an ICF credential (the ICF recording and transcript requirements are a separate use case for the same archive).

The sessions that would tell you the most about your own patterns are the ones that already happened and are sitting, unwatched, in your Zoom Cloud or your Drive right now. The only real barrier is the bit of friction in actually sitting down with it — and a searchable transcript is what removes that friction.

Monday morning, after Friday's group call, your inbox has five variations on the same message: "Sorry I missed it — could I get the replay?" You dig up the recording, attach or link it, and reply to each one individually. Next week, a different five people ask. The program runs twelve weeks. You do the math and realize you've become a part-time file clerk for your own course.

That's the group-program version of a problem 1:1 coaches don't have: you can't just send the recording to the whole cohort once and be done — replay access isn't a one-time handoff, it's a recurring operational job with a growing recipient list. Run the math on the hook above: five replies a week, twelve weeks, even two minutes apiece to find the file and write the message — that's two hours spent re-sending the same recording, every time you run the cohort.

What's actually happening

A 1:1 coaching recording has one recipient. A group program or course multiplies that: every session needs to reach everyone who's paid, not just the people who showed up live, and the roster shifts as people join a cohort late, finish early, or roll off when the program ends — course replay access has to track that shifting roster, not a fixed guest list from week one. Handled by hand, that's a link re-sent to a growing list of email addresses, every week, with no single place a participant can go to catch up on a session from three weeks ago.

Zoom's own sharing model confirms this: a cloud recording gets one share link generated for a specific set of viewers, and a new link is generated whenever that set changes — there's no concept of "everyone currently enrolled" that updates itself as a roster changes. That's a job for wherever you're already keeping the files: a shared folder.

The cohort-folder model: how to share group coaching replays

The fix is to stop sharing recordings and start sharing a folder — one per cohort, set up once, not one link per session.

One folder per cohort, not per session. Create a single Drive folder for the program — Group Coaching/Spring Cohort 2026/, or however you organize it — and let each week's session land inside it as its own dated subfolder. Point participants at the parent folder once, at kickoff, and every future session is already visible to them without another email.

Access bound to the paid list, not a public link. Google Drive's sharing settings let you add a specific list of email addresses to a folder with Viewer permission — up to 600 people on one file or folder — instead of turning on "Anyone with the link can view." That distinction matters for a cohort: adding people individually means access maps to who's actually enrolled, and removing one person's access affects only them — the rest of the cohort keeps working.

Consistent naming so weeks don't get lost. Week 1 — 2026-06-01, Week 2 — 2026-06-08, and so on. A participant who missed weeks 3 and 7 should be able to find both in the time it takes to scroll, not search.

Expiry when the program closes. On most Google Workspace plans, you can set an expiration date on a person's access to the cohort folder, so it lapses automatically instead of quietly outliving the program by a year (a handful of cheaper Workspace editions and personal @gmail.com accounts don't offer this — for those, put "revoke cohort access" on your own program-close checklist next to the other wrap-up tasks).

The transcript, for people who'd rather search than watch. A 90-minute group call is a big ask to re-watch for one specific answer. A searchable transcript alongside the video lets a participant Ctrl-F for the topic they missed instead of scrubbing through the recording.

How RecordFlow fits

RecordFlow doesn't manage your roster or gate access by cohort — that access-control layer above is still yours to run in Drive, and it's genuinely worth the ten minutes it takes to set up once per program. What it removes is the manual step underneath it. Connect your Zoom account to a Drive folder once — about 60 seconds — and every group call lands there automatically the moment Zoom finishes processing: video, audio, chat log, and a clean Google Doc transcript reformatted into timestamped, speaker-labeled paragraphs instead of a raw caption file. The files move straight from Zoom to your Drive; RecordFlow never keeps a copy of the recording on its own servers, which matters when a cohort's sessions are confidential.

Point RecordFlow at your cohort's parent folder and each week's session appears inside it as a new dated subfolder (grouped under a year folder, same as any other RecordFlow archive), ready for the sharing settings you already configured at kickoff — no downloading a file from Zoom and re-uploading it to Drive between the call ending and the replay being available. The same professional handoff habits from 1:1 coaching — consistent naming, the transcript alongside the video — carry over to a cohort folder just as well as a client folder.

Replay access for a group program shouldn't cost you more admin time than the session itself took to run. Set the folder and the access list up once at kickoff, and every week after that is just RecordFlow depositing a new subfolder where your cohort already knows to look.

Cancelling Zoom — or downgrading to free — starts a countdown on your cloud recordings: Zoom gives you 30 days, then they're gone permanently. You clicked "cancel," or you're about to, and now you're wondering what happens to three years of client recordings. Here's the short answer, then the details.

The details depend on which button you pressed.

If you cancel Zoom entirely

When you cancel a paid Zoom subscription, your cloud recordings are moved to trash and remain recoverable for up to 30 days. After that window closes, they're gone permanently — no extension, no second chance.

One nuance: this trash recovery window depends on your account's trash feature being enabled. If it's been disabled by an admin, recordings deleted on cancellation may not be individually recoverable via that route.

Thirty days sounds like enough time. But "recovering" them means downloading every file individually through Zoom's web portal — there is no bulk video export. If you have months of sessions, that's hours of clicking under a deadline, done while also migrating off the platform.

If you downgrade to free: you lose cloud recordings

Downgrading means losing cloud recordings entirely. Zoom's free plan doesn't include cloud recording — local only — so the moment your paid plan lapses, you can't make new cloud recordings at all.

Your existing recordings are set to be deleted after 30 days. But the recovery path is different from cancellation: Zoom's documentation for this scenario describes getting them back as resubscribing to a paid plan within that window — not downloading them from a trash tab. You'd need to reactivate a paid plan, download what you need, and then cancel again. Another deadline, another scramble.

The grace period is not a backup

The 30-day window is a recovery mechanism — designed for "I deleted that by mistake, get it back now." It isn't a migration window or an archive suited for "I need that client session from 18 months ago."

If your recordings are client notes, course materials, or anything with long-term value, Zoom's grace period offers no real protection — and the way you recover within it depends on how the recordings left. Cancelling outright moves them to Trash, the same 30-day Trash window you get when you delete a recording on purpose; downgrading to free instead starts its own 30-day clock that you reopen by resubscribing to a paid plan, not by restoring from a Trash tab (as the downgrade section above spells out). Either way the countdown is short and the recovery is manual. (For the full picture of how recordings can quietly disappear from Zoom cloud, see What Disappears From Zoom Cloud, and When.)

Two paths after cancellation

When someone realises their recordings are at risk, they end up in one of two situations.

The scramble. Racing to download everything before the window closes. Dozens or hundreds of recordings, each downloaded individually — there's no bulk video export from Zoom. Miss the deadline and those recordings are gone.

The non-event. Your recordings were already in Google Drive, backed up automatically each time a session finished. Cancellation is a billing change, not a data crisis.

The difference isn't what you did when you decided to cancel — it's what you did months earlier. If you're reading this before cancelling, you still have time to make it a non-event.

By the time you decide to cancel, it's too late to plan

Cancellations rarely happen on a schedule. A price increase, a better alternative, a change in how you work — the decision moves fast. Backing up your Zoom recordings to Google Drive now means any future Zoom decision is a billing change, not a deadline. Drive doesn't auto-delete, doesn't expire, and the long-term math on storage strongly favours it anyway. The rest of the Zoom storage & retention guides cover the neighbouring ways recordings slip away — hitting a full storage pool, or an admin retention policy clearing them out from under you.

How RecordFlow fits

RecordFlow backs up every Zoom cloud recording to the cloud storage you own — Google Drive, OneDrive, or Dropbox — automatically; recordings transfer directly from Zoom, and RecordFlow never stores a copy on its servers. Nothing to schedule, nothing to manually export. By the time you're weighing whether to cancel Zoom, your archive is already somewhere durable.

An hour after a session ends, Coach A sends: "Here's your recording: zoom.us/rec/play/…"

Coach B sends: "Your recording and transcript from today are in your folder — link below. What I'm sitting with from our conversation: [one sentence]. See you in two weeks." The link goes to a Drive folder labeled with the client's name and the session date. Inside: the video, the audio-only file, and a Google Doc transcript the client can search.

Same session length. Same Zoom account. Only one of those coaches delivered a deliverable.

Why the packaging matters

A bare recording URL carries no signal about how you organize your practice. It says: I pressed Save, here's the file. The client has to figure out where it goes, how it relates to their other sessions, whether the link will still work in six months.

A consistent handoff — a named folder, predictable structure, the transcript already there — says something different. It says the session happened inside a system you built, that their material is organized and permanent, that you thought about what happens after the call ends. That's not cosmetic. It's the same logic that makes session recordings a credible premium deliverable: the artifact is more valuable when it's packaged like one.

The delivery moment is also the last touchpoint before the client decides whether to book the next session. A small ritual around it compounds into reputation.

How to send coaching recordings to clients: four elements

Most coaches improvise the handoff each time — which means it's inconsistent. It goes well when the week is calm and gets skipped or rushed when it isn't. The fix isn't more effort; it's a system small enough to complete in under two minutes, every session.

A per-client folder. Give each client one Drive folder that grows over the engagement — Coaching/Clients/Jane Smith/, or however your practice is organized. Every session subfolder goes inside it. When you share the link, the client sees every session in one place, in order. Google Drive's sharing model lets you give one person access to one specific folder without exposing anything else in your Drive.

Consistent session naming. Pick a pattern and keep it. 2026-06-29 — Session 4 or 2026-06-29 Jane Smith — anything with a date and a logical sequence. The format doesn't matter; the consistency does. A client who wants to find a specific session from eight months ago should be able to do it in five seconds.

The transcript Doc. Most clients won't re-watch an hour of video to find the three minutes that mattered. A searchable transcript — with timestamped paragraphs and each speaker named — means they can find the exact moment without scrubbing. Include it alongside the video file. Clients who wouldn't sit through forty minutes of video will search a Doc for "accountability" or "next steps" and find it in ten seconds. It turns the recording from proof that the session happened into a document the client can actually use.

The two-line note. Not a newsletter, not a session recap. Just: where the materials are, and the one thing you want the client to carry into the next few days. Something like: "Your recording and transcript are in the link below. What we committed to this week: [one sentence]." Under thirty words. The note is what makes the handoff feel personal rather than automated — even when the filing was automated.

How RecordFlow handles the parts you'd have to do manually

RecordFlow handles the infrastructure in 60 seconds of setup. Connect your Zoom account to a Drive folder once and every cloud recording transfers automatically the moment Zoom finishes processing: the video, the audio-only track, the chat log, and a clean Google Doc transcript — the raw caption file reformatted into timestamped paragraphs with each speaker named — deposited into a dated subfolder inside the folder you chose. The files move directly from Zoom to your Drive; RecordFlow doesn't hold a copy on its own servers, which matters when sessions are confidential. (The full setup walkthrough is in the guide on backing up Zoom recordings to Drive.)

Without automation, every step of the handoff is yours to remember and execute: download the recording from Zoom while it's still available (cloud recordings pile up against your plan's storage limit and can disappear once it fills), create the dated subfolder in the right client folder, upload the video and audio files, track down the caption file, reformat it into a readable document. That's ten to fifteen minutes per session — and it's exactly the kind of task that quietly stops happening during a busy week.

What that leaves for you: the two-line note and the share. The folder already exists. The transcript is already there. The share is three clicks: right-click the session subfolder → Share → "Anyone with the link can view" → copy URL → paste into your reply. If a client doesn't have a Zoom account and your Zoom share link asks them to sign in, a Drive link is the fix — the guide on sharing without a Zoom account covers that in full.

The folder structure, the naming, the transcript alongside the video — all of it happens automatically, every time. The polished handoff is mostly already done before you open your email.

Most coaches who want to start recording sessions can name the exact moment they decided to do it — the breakthrough a client had mid-call, the technique they watched land in real time, the first session where they thought, I want to be able to return to this. Then months pass and they still haven't asked a single client.

The reason isn't reluctance. It's the ask itself. "How do I bring this up?" feels clinical, or heavy, or like it might shift the atmosphere of the session. The conversation never happens, so the recording never starts, and the sessions keep disappearing.

The ask takes about twenty seconds. Here's how to make those twenty seconds easy.

Why recording consent feels awkward (and why it shouldn't)

The word "consent" pulls toward a medical register — forms, checkboxes, disclosures. Coaches who are wired toward warmth and informality find that register uncomfortable, which is exactly why they defer the conversation.

The reframe: the recording is for the client, not for you. You're not asking them to accept something being done to them. You're announcing something good that comes with the work — a way to revisit what happened in the session, replay the moment a reframe landed, or read back through what they committed to between calls. Most clients say yes without hesitation. The ones who say no have told you something useful about their comfort level, and that's worth knowing before you start recording rather than after. Coaches who've started routinely delivering recordings often describe the same surprise: clients don't just tolerate them; they reference them, quote them back, and thank you for them.

That's the right mental model. Giving recording consent is not something you're asking clients to accept — it's something you're offering them.

When and how to tell a client you're recording

The best moment is before the first session, not during it. Framing recording as a stated norm in your intake process — before you've ever spoken — means the client arrives expecting it, not discovering it mid-call. Consent becomes part of onboarding, not an interruption.

In your intake form or client agreement:

Sessions are recorded and shared with you via a private Google Drive link.

One sentence. Recording becomes part of the structure of the relationship before the client says hello.

At onboarding, if you're stating it verbally:

I record all our sessions so you can revisit them afterward. You'll have the video, audio, and a searchable transcript in a private folder that's yours to keep. Is that alright?

Most clients say yes without a follow-up question. The ones who pause usually want to know who else can see the recording — and "just you, in a Drive folder I share only with you" closes it.

If a new client joins a group or program mid-series:

Quick heads-up before we start — I record every session and send you a link right after. You'll have a video and transcript of everything we cover today.

Ten seconds. It doesn't break the flow; it signals care. The client who hears this knows the session is worth capturing.

The order matters more than the words. Once the recording consent conversation happens at intake — in writing, before you've ever spoken — you never have to revisit it in a session again. It becomes part of what working with you means, not something you negotiate one client at a time.

How RecordFlow fits

The ask is the easy part. What slips for most coaches is the manual download-and-share loop afterward — the session ends, the recording sits in Zoom, and the "send the client their link" task drifts off the to-do list for two days. That's where the promise made at intake quietly stops being kept.

RecordFlow closes that gap automatically. Connect Zoom to a Drive folder once, and once Zoom finishes processing the recording, RecordFlow moves everything there — video, audio, the chat log, and a clean transcript Doc when Zoom generated one. When the client asks for their replay, sharing it from Drive takes three clicks: open the session folder, share it to the client's email, done — no download, no reupload, no separate login required on their end.

The promise you made at onboarding — "you'll always be able to revisit what we covered" — then takes care of itself.

The coaches who record every session aren't bolder or more forward than the ones who don't. They just had the twenty-second conversation once — in an intake form, or at the start of the first call — and then stopped having to think about it. The awkward moment becomes a non-moment. The client arrives expecting the recording.

A client emails: "Could I get a recording of last month's session? There was something you said I want to listen to again." You go looking — into Zoom's Recordings page, into your Drive, through your downloads folder. And it's not there. Expired under a retention window you configured months ago, or cleared when the storage cap filled, or just never backed up during that particular stretch of twelve-sessions-and-a-client-emergency.

That recording is gone. The client paid for that session. There is no recovering it.

What's actually happening to Zoom cloud recordings

Zoom cloud storage is not a permanent archive. Zoom Pro plans include 10 GB per licensed user, pooled at the account level. A solo coach recording fifteen sessions a week fills that space in two to three months. When the cap fills, you may not be able to start a new cloud recording at all — Zoom shows an error at the moment you try to record rather than any advance warning. (The blocked-from-recording guide covers exactly what to do if that happens mid-session.)

Even if you stay under the cap, Zoom gives account owners the option to automatically delete recordings after a configurable number of days. If a past account owner turned on that setting and you inherited the account, recordings may be expiring quietly without you knowing it.

Every recording you don't move somewhere else is on a clock.

Why the manual backup always breaks

The obvious fix is to go into Zoom after each session, download the video file, and upload it to Google Drive. It works — when you do it. The problem is the "when you do it."

Manual backup is a task that lives in the gap between sessions. It requires you to remember, to have a free moment, and to actually execute a handful of steps that add nothing to the session itself. During a slow week, it happens. During the weeks where you have twelve sessions, a rescheduled client, and a late invoice — the weeks that are also your most valuable, the ones with sessions worth keeping — it quietly doesn't.

This isn't a discipline problem. It's a systems problem. Any critical step that depends on the busiest person remembering to do it during their busiest time will eventually get skipped. The clients who emailed asking for a recording they can't get are not the first, and they won't be the last.

How to save Zoom recordings automatically

The only backup that doesn't break is one that runs itself.

When a Zoom session ends and Zoom finishes processing the recording, a reliable backup service can catch the recording the moment it's ready — within minutes of the call ending — and copy it to a Google Drive folder you own, before you've even sent the follow-up email.

Once that's true, you never have to think about it. Every session is in Drive. The client from eight months ago who asks for their recording? It's there. The session where something important came up that you want to revisit? It's there. You didn't have to do anything differently — you just had to record, same as always.

This is the case Google Drive vs Zoom Cloud: Where Your Meeting Recordings Should Live makes in full: Drive doesn't auto-delete, it's searchable across years of sessions, and it's shareable with a standard Drive link that clients already know how to open.

How RecordFlow fits

RecordFlow does this one thing: the moment Zoom marks a cloud recording ready, it copies every file — video, audio, transcript, chat log — to a Google Drive folder you choose. Your recordings go directly from Zoom to your Drive; RecordFlow copies them in transit and never stores them on its own servers, which matters when the sessions are confidential.

Setup is sign in with Zoom, connect Google Drive, pick a destination folder — about 60 seconds. After that, it runs on its own. Passcode-protected sessions and multi-hour calls work the same way. If a transfer fails for any reason, it retries automatically, and a safety check runs hourly to catch anything a notification missed. The full walkthrough for setting this up covers each step and what to check if a recording doesn't arrive.

Once the backup is automatic, you stop managing recordings and start using them. And handing the recording to the client becomes a Drive share link — no Zoom account needed, nothing to download, works the same as any file you'd send.

Your client is waiting for the recording. You open the Zoom folder and find: shared_screen_with_speaker_view.mp4, audio_only.m4a, audio_transcript.vtt, meeting_saved_chat.txt. Four files with names that don't tell you which one to send. Most coaches forward the MP4 by instinct — but the MP4 isn't always what your client needs, and some of those other files are more useful than they look.

Here's what each file is for and a simple cheat sheet for which one to share.

What each Zoom recording file does

Zoom can create several different file types for a single cloud recording. The exact set depends on your account settings, but a typical coaching or consulting session produces most of these:

The video file (.mp4)

The main recording — you, your client, and anything shared on screen, all captured together. Zoom identifies it by the layout active when you hit Record — shared screen with speaker view, gallery view, and so on — and that label appears in your portal and in the filename when the recording is synced to Drive. This is the file clients want when they want to rewatch the session.

The audio-only file (.m4a)

The same conversation, without video — just the audio track. Zoom records this alongside the video when your account has it enabled. It's lighter to share than the MP4 and works on any phone or podcast app. A client who commutes or walks while replaying sessions often prefers it.

The transcript file (.vtt)

A WebVTT caption file — the spoken audio transcribed as timestamped utterance segments. It's the format that drives closed captions in video players, not the format humans read comfortably. A single thought can be split across multiple cue blocks, each with its own timestamp. Most clients won't know what to do with a .vtt file, and most can't open it cleanly without a specific video player. You'll almost never send this to a client directly.

The chat log (.txt)

Everything anyone typed in the Zoom chat window during the call, saved as plain text with timestamps and names. Useful if the chat contained links, resources, or notes that someone wrote rather than said. Short or quiet sessions often produce an empty log.

The readable transcript document (when RecordFlow archives your recordings)

This is the .vtt converted into a document a person can actually read — speaker-per-paragraph layout, rounded timestamps, speaker names bolded, without the cue-block clutter. RecordFlow renders it as a Google Doc on Google Drive, or a Word .docx on OneDrive and Dropbox (on YouTube, only the video is archived — there's no file store to put a document in). It's what you share with a client who wants to find the three minutes that mattered without scrubbing through an hour of video. On Drive, it's also what you'd add to Gemini Notebook (formerly NotebookLM) or Gemini to ask questions across a quarter of client calls — the AI workflows post goes into detail on how that works.

Which file to send your client

The main difference between the three common formats: .mp4 carries video and audio together, .m4a is audio-only, and .vtt is a raw caption text file — not a readable document. Here's the decision at a glance:

For most one-on-one coaching or consulting sessions, the video plus the readable transcript document covers it: the MP4 for replay, the document for finding the exact moment they want to revisit without watching the whole thing again.

You don't have to explain any of this to your client. You just send the right file.

How RecordFlow fits

When RecordFlow transfers a recording from Zoom into your cloud storage, the session's files land together — video, audio track (when your Zoom account records it separately), chat log, raw .vtt, and a readable transcript document (a Google Doc on Drive, a Word document on OneDrive and Dropbox) — in one dated subfolder per session. On YouTube, it's the video alone — a channel has nowhere to put the rest.

By the time you think to share something, the recording is already in a folder you own. You open your cloud storage, find the session folder, and share from there. No download from Zoom, no re-upload, no wait. The setup guide walks through the one-time connection; the short version is 60 seconds and an account with your storage provider.

Sharing from your own cloud storage also removes a frustration that catches clients off guard: Zoom share links sometimes demand a Zoom login before the replay will open. A Drive or OneDrive link set to "Anyone with the link can view" opens directly in a browser, no Zoom account required on their end.

You're three minutes into a session when your client pauses mid-sentence, and something shifts in their expression — a flicker of recognition, or resistance, or grief. You almost missed it because you were transcribing their previous sentence.

That's the cost of live note-taking. Not the time it wastes. The moments it hides.

Should coaches take notes during sessions?

The question comes up constantly, and the answer has changed — not because recording is new, but because automated backup now makes it reliably available after every session. Once the recording is guaranteed, notes stop being the memory, and you're free to be somewhere better.

A coaching session asks a lot of a coach: listen for what's said, what's avoided, what's underneath the words. Do that at full attention and most sessions have a moment that changes something. Do it while writing, and you're running two cognitive tasks at once — and attention isn't infinitely divisible.

The ICF's core coaching competencies put Active Listening at the center of effective coaching — not active listening between paragraphs, but full, focused listening that tracks the whole person, not just their words. Live note-taking works against this. The coach is partially elsewhere; the notes are the record.

The client feels it too. When they sense the coach is writing, they start narrating — shaping their words for the document instead of for the work. What should be a real-time conversation becomes a deposition. They're telling you what happened, rather than experiencing it.

Notes taken under those conditions tend to capture the content of the conversation — what was said — but miss the texture: the hesitation, the energy shift, the moment when a client stopped performing insight and actually had one.

That texture is often more useful to you between sessions than the bullet points you typed while half-listening.

What the recording carries instead

A Zoom recording captures everything. Every pause. Every question you asked and the way the client's answer wandered before it landed. Every moment you'd want to revisit before next session.

The transcript captures the words with timestamps — not because you need exact timestamps, but because a searchable, readable document means "what did they say about their co-founder?" takes three seconds to answer instead of a scan through handwritten notes. Here's what a clean transcript looks like once it's in Drive, and what you can do with it.

Between sessions, instead of a sparse notes file with things you half-remember, you have a complete record of the hour — accurate, yours, retrievable. You can skim fifteen minutes before the next call and walk in prepared in a way manual notes rarely produce.

And you can give that same full record to the client. A client who gets the recording can replay the moment the insight landed. They can search the transcript for the commitment they made. They can hear the session again on the night they're stuck — clients often go back to the last ten minutes, not the hour, which is exactly the part the transcript makes easy to find. The recording isn't overhead — it's the client's most underused asset from the work they already paid for. More on that in the companion post on giving clients their recording.

What the session looks like when you stop taking notes

The first few sessions without a notepad feel unmooring. You may reach for your keyboard out of habit. Then, usually within the hour, something loosens: you're tracking the client instead of the transcript, and the session goes somewhere it might not have.

Coaches who make this switch often report the same two things: they're more present during the session, and their clients are too. When a client knows the recording is coming, they put their own notepad down. They stop performing memory retention and start doing the actual work of the session.

The post-session habit changes slightly. Instead of reviewing notes you wrote during the session when your attention was split, you spend ten minutes with the transcript: read the last third, mark the two or three things you want to open with next time, done. That's a better prep artifact than anything you'd have typed while listening.

How RecordFlow fits

"Record instead of note-take" only works reliably if the recording actually shows up somewhere you control, every time.

Zoom Cloud isn't that place on its own. It has a storage quota that fills faster than expected on active accounts, and many organizations configure recordings to auto-delete on a 30, 60, or 90-day schedule — which creates "did it actually save long enough?" anxiety you don't need. Backing up every recording automatically to Google Drive removes it: sign into RecordFlow, connect Drive, pick a folder. After that, every file Zoom generates — video, audio recording, chat log, and a clean transcript Google Doc when Zoom's audio transcription is enabled — lands in Drive within minutes of the session ending. RecordFlow never stores the recording on its own servers; it moves the files directly from Zoom to the folder you own.

That means when the call ends, you're not thinking about whether the recording saved. You know it's in Drive, the transcript Doc is there, and you know exactly where to find both. "I'll capture it" is no longer a worry you carry into the room.

The note-taking habit persists in coaching partly because recording wasn't convenient enough to replace it. When backing up a session meant a manual, multi-step process that sometimes failed on large files, notes were the reliable fallback. Automation removes that excuse. The recording is there, the transcript is there, and you have more attention left for the room.

If you're not yet recording your sessions, the step-by-step setup guide is the place to start — this post picks up from there.

You search Zoom's Recordings page for the client session you ran three months ago. Nothing. No error, no notification — just gone. Zoom cloud storage is temporary by design, not an unlimited archive — and there are four distinct mechanisms that can quietly delete recordings you assumed were safe.

Zoom cloud storage is pooled and capped. Pro and Business plans include 10 GB of cloud storage per licensed user in a shared account pool; Business Plus includes 15 GB per seat. On a solo account that's still a modest total — a single hour of HD video runs several hundred megabytes once Zoom compresses it, and ten to fifteen sessions a week fills 10 GB in two to three months. On a team account every host draws from the same pooled total, so one heavy week from one user can tip it for everyone.

The storage cap is the most visible problem. But there are three other mechanisms that delete recordings even when storage isn't the issue.

The four ways recordings disappear

1. Storage cap

When the shared pool fills, Zoom blocks any new cloud recordings from starting — a recording already in progress can still finish, but nothing new can begin. If you've hit the red "Cannot start cloud recording" banner mid-session, here's what to do right then — and once the session is over, the safe sequence for freeing space without losing a recording is the right next step.

The cap alone doesn't delete recordings you've already made. But it creates pressure to delete manually, and that's where recordings get lost. Under time pressure, a quick pass through the Recordings page — "delete the old ones to make room" — is exactly how a session that was never backed up disappears for good. The permanent fix is moving recordings out of Zoom cloud as they're made, so the pool never accumulates toward the cap in the first place.

How to detect it: Zoom sends an email when storage is almost full. Log in to the Zoom web portal → My Profile → Recording → Cloud Recordings to see current usage.

2. Admin-set retention policies

Account owners and admins can configure a Zoom retention policy that automatically deletes cloud recordings after a set number of days of their choosing. Licensed individual users can also set their own auto-delete interval for their own recordings. This setting, at any level, runs on schedule regardless of whether you've backed up.

When it's on, recordings are deleted on schedule. The recording doesn't go to Trash for recovery; it's removed. As an end user on a team account, you may not be able to see whether an account-level policy is in effect — that setting lives in the admin console, not the user settings panel.

If your recordings started disappearing on a roughly predictable schedule and you didn't delete them, this is the most likely explanation. Ask your Zoom admin.

If you're the account owner: check your own settings. If the Zoom retention policy auto-delete is on and you haven't been backing up to Drive, you may have already lost recordings you assumed were permanent.

How to detect it: Admins can check Account Management → Account Settings → Recording & Transcript → "Automatic recording deletion." Licensed users can check their own interval under Settings → Recording. Users on team accounts who can't see these settings: ask your admin.

3. License reassignment

Zoom licenses are attached to individual users, not to recordings. The risk to your recordings depends on what the admin actually does:

• License removed or reassigned: Your access to cloud recordings disappears, but the recordings themselves typically stay in the system — an admin can still see them in Recording Management and restore your access by reassigning the license.
• User account deleted without a data transfer: This is when recordings are permanently lost. If an admin deletes your Zoom user account without first transferring your recording data, there is no recovery path.

The distinction matters: losing license access is reversible; losing the user account record isn't. For solo practitioners who own their Zoom account outright, this scenario doesn't apply. But on team accounts, any admin-initiated account deletion is the real risk event for Zoom license reassignment recordings — not a mere license swap.

How to detect it: If your Recordings page goes empty after an admin action, contact your Zoom admin immediately. If the account still exists, access may still be restorable. If the user record was deleted, act before the Trash window closes.

4. Account cancellation or downgrade

If you cancel your Zoom paid plan or downgrade to the free tier, cloud recordings become inaccessible — cloud recording is not available on Zoom Free plans. The recordings in your cloud library don't automatically transfer anywhere when the plan changes. Re-upgrading within approximately 30 days may restore access; beyond that window, recordings are typically deleted permanently.

Zoom's cancellation flow doesn't prompt you to download or back up your recording library first. If you cancel without backing up and don't plan to re-upgrade, the recordings are gone.

How to detect it: There's no warning here — this is triggered by an intentional account action. Back up your full recording library before you cancel or downgrade, not after.

Can You Recover a Deleted Zoom Recording?

When a cloud recording is deleted — by you, by Zoom, or by an admin policy — it goes to Trash rather than disappearing instantly. Zoom keeps deleted recordings in Trash for up to 30 days, and they're recoverable from there during that window.

One important caveat: recordings removed by admin retention policies or user-account deletions may not pass through Trash the same way a manually deleted recording does. For those scenarios, the Trash window offers no safety net. Once a recording is gone through one of those paths, it's gone for good.

Trash is a last resort, not a plan.

What a Drive backup changes

Google Drive doesn't auto-delete files. Once a recording lands in your Drive, it's outside Zoom's storage lifecycle entirely. Storage caps can't reach it. Retention policies don't apply to it. License reassignments don't touch it. Account cancellations don't take it with them.

That's the structural shift: from "my recording exists in Zoom's temporary storage" to "my recording exists in a place I own and control." The full setup guide walks through connecting Zoom to Drive in about 60 seconds.

How RecordFlow fits

If a recording is already gone, RecordFlow can't retrieve it — it's a backup service, not a recovery tool. But every recording that arrives in Drive before a storage cap, a retention policy, or an account change removes it from Zoom is a recording you keep.

RecordFlow backs up every cloud recording to your Google Drive within minutes of Zoom marking it ready — triggered by Zoom's webhook, with an hourly sweep as a fallback — automatically, without a manual download loop. Recordings stream directly from Zoom to your Drive; they don't touch RecordFlow's servers. Once the Drive copy is confirmed, RecordFlow's optional auto-delete waits a three-day grace period before clearing anything from Zoom Trash.

The four mechanisms above still run. They just no longer have anything to take from you.

You send the recording link. An hour later, the message arrives: "It's asking me to sign into Zoom — I don't have an account. Can you resend it?" That's the Zoom share-link wall, and it doesn't announce itself when you hit Send. Your client clicks the URL and lands on a login prompt instead of the replay they were looking forward to. The simplest fix is to share the recording from the cloud storage you already archive to — Google Drive, OneDrive, or Dropbox — instead, no Zoom account required on their end.

Why Zoom share links block clients who don't have a Zoom account

When you click "Share" on a cloud recording in the Zoom portal, Zoom generates a hosted playback page under zoom.us. Whether that page opens freely or demands authentication depends on a setting in your account's admin panel: "Require authentication to view cloud recordings." It's off on a fresh Zoom account, but admins frequently turn it on — and Zoom doesn't warn you when you copy the link. The result: the same URL that works fine for a client who happens to have a Zoom login will silently block one who doesn't.

There's a second problem that hits later. Zoom doesn't auto-delete cloud recordings by default, which means they pile up against your plan's cloud storage quota — and once that quota is full or the bill gets uncomfortable, admins start setting retention policies. When they do, recordings disappear on a schedule your clients never hear about. The link they saved stops working, and you find out when they email you asking for a session from eight months ago that no longer exists. The Google Drive vs Zoom Cloud comparison covers the full picture on storage and retention.

Why a cloud storage link works when a Zoom link doesn't

Google Drive sharing — like OneDrive's and Dropbox's — is the same workflow your clients use every week: to open a proposal, review a contract, look at an invoice. Click Share, set the permission to "Anyone with the link can view" (OneDrive and Dropbox offer the equivalent "anyone with the link" option), and copy the URL. The client opens it in a browser. No Zoom account, no app, no sign-up, no learning curve.

Three things make a link from your own cloud storage more reliable for this job:

1. The file doesn't disappear. Once a recording is archived, it stays until you delete it. There's no storage clock ticking, no admin-triggered retention policy, no "this recording has expired" message arriving six months later when a client wants to revisit something you covered together.

2. Anyone-with-the-link viewer access opens the file without authentication. Google Drive's sharing model is designed for exactly this — handing a file to someone who isn't in your organization. The link opens and the recording plays, regardless of whether your client has a Google account, a Zoom account, or neither.

3. You control access individually. You can give one client's email address access to one session folder, keep everything else private, and revoke that access later if the relationship ends. If you want a link to stop working after a fixed window, Google Workspace accounts can set an expiry on shared links. No equivalent per-client control exists on a Zoom share link.

What makes sharing from your own cloud storage actually easy

Fixing the link your client just messaged you about is a one-time workaround. Here's how to make sure it never happens again.

The reason most coaches use Zoom links anyway isn't that they prefer them — it's that the recording is already there, and copying it elsewhere means logging into the Zoom portal, downloading the file, opening your cloud storage, finding the right folder, uploading, waiting. That's the kind of step that quietly doesn't happen during a busy week.

RecordFlow removes that detour. Once you connect Zoom to a folder you choose — on Google Drive, OneDrive, or Dropbox — every cloud recording is copied there automatically — the video, the audio-only track, the transcript, and the chat log — into its own dated subfolder, within minutes of Zoom finishing processing. The setup guide walks through the full process, but the short version is: sign in with Zoom, connect Drive, pick a folder, done. From that point on, the recording is in Drive before you think to share it.

When a client asks for their session replay, the workflow becomes: right-click the session folder → Share → "Anyone with the link can view" → Copy → paste into your reply. A few clicks from a file you already own, with no download-and-reupload in between.

Because you're sharing from your own storage, you're also sharing the transcript that arrives alongside the video — a clean, readable document (a Google Doc on Drive, a Word document on OneDrive or Dropbox) with timestamped paragraphs and each speaker named, so clients can search instead of scrubbing through an hour of video to find the five minutes that mattered. That's part of what turns the recording into a real deliverable, not just a link that may or may not open. The recording-as-deliverable post goes deeper on how clients actually use it.

The "I can't open the recording" email is a solvable problem. A client who can replay the session is more likely to sit with the breakthrough that happened in it, follow through on what they committed to, and come back for the next one. The barrier is almost always one wrong link — and a Drive folder that already has the file makes the right link the easy one.

You're two minutes into a paid session — or a class is about to start — when Zoom shows the red banner: "Cannot start cloud recording. Cloud storage is full." The client is on screen. You freeze.

Here's what to do — starting right now, with the call still running.

Zoom storage full mid-session? Switch to local recording right now

Zoom has a fallback when cloud storage is full: local recording. It writes the video directly to your hard drive, bypassing the cloud entirely.

In the meeting:

1. Click Record in the toolbar (or press Alt+R on Windows, Cmd+Shift+R on Mac).
2. When Zoom asks where to record, choose Record on this Computer — not "Record to the Cloud."
3. Zoom starts capturing locally. The session is saved. (If "Record on this Computer" is greyed out, check that local recording is enabled in your Zoom account settings under Recording — it's on by default for most paid plans but can be disabled by an admin.)

Finish the call normally. The recording lands on your hard drive when the meeting ends — Zoom shows you the file path once it finishes processing.

After the call, copy the local recording to Google Drive before your next session. A file sitting only on your laptop isn't a backup.

Local recording requires that you're the host on your own machine. If you're on a tablet, a borrowed device, or co-hosting, it may not be available — but for most solo practitioners it's always there as the emergency fallback.

What's actually happening

Zoom cloud recording storage is pooled and strictly capped. Most paid plans include 10 GB shared across all Licensed Users on the account — not per person. A single hour of HD video runs a few hundred megabytes after Zoom compresses it, which means a coach or trainer recording ten to fifteen sessions a week fills the shared pool in two to three months. On a team account it fills faster still: everyone draws from the same shared pool, so one heavy week from one host can tip the cap for the whole account.

When the pool is full, Zoom blocks new cloud recordings. There's no warning before the meeting — just the red error when you try to start. If you caught the "storage almost full" email beforehand, you have a short window to act. If not, you get the banner mid-session.

Either way, the root cause is the same: recordings are accumulating in Zoom cloud faster than they're being cleared. The cap isn't a one-time accident — it'll happen again unless something in that pattern changes.

"Storage full" during a live lecture, even though you have space?

This is the version of the confusion instructors hit most: you're mid-lecture, or about to start the next class, and Zoom throws the same "cloud storage is full" error — except your own recording habit is light. A few sessions a week, most cleared out months ago. It doesn't add up until you remember whose storage this actually is.

On a school, department, or training-program Zoom account, cloud recording storage isn't allocated to you individually — it's a single pool shared across every licensed user on the account. Dozens of instructors recording lectures all draw from that same shared allowance, and education-tier plans start from a smaller per-license pool than a standard business plan's 10 GB — some as low as 0.5 GB per licensed user, which fills across a whole faculty even faster. Your own footprint can be a few gigabytes and still get blocked, because everyone else's semester of lecture video is sitting in the same pool.

Two things happen once that pool hits the cap. A lecture already recording to the cloud when the account crosses it keeps recording until the meeting ends — Zoom doesn't cut off a session in progress. What it blocks is the next one: once that class ends, no new cloud recording can start — yours or a colleague's — until the account frees space or buys more.

If you don't manage the Zoom account yourself, this isn't something your own recording settings can fix — flag it to whoever administers the account, since both the cap and the cleanup live at the account level, not the host level. In the meantime, the fallback is the one covered above: switch to local recording for the class that's blocked, then move the file to Drive once it's over.

The durable fix scales the same way regardless of who owns the account: get recordings out of the shared pool automatically instead of leaving them to pile up until the next cap. Doing that for your own recordings shrinks how much of the shared pool you personally hold onto — and if a whole department is hitting this, the same principle applies at account scale. Buying more storage just delays the next cap; moving recordings out of Zoom is what stops it recurring.

How to free Zoom cloud storage so recordings work again

Once the session is over, you need to clear headroom so the next call records to the cloud normally. The safe sequence:

1. Open Zoom's Recordings page and look for recordings you can clear — ones you know are already backed up to Drive, or older sessions you've finished with.
2. Confirm the Drive copy before you delete. Open the Drive folder and check that the files are there — all of them (video, audio, transcript). Don't delete anything from Zoom until the copy is verified.
3. Move cleared recordings to Zoom Trash to reclaim the space. Zoom keeps trashed recordings for up to 30 days, though your account settings can shorten that window. After it closes, they're gone for good — so treat it as a grace period, not a second backup.

A handful of older recordings usually frees enough headroom for your next several sessions. You don't have to clear the whole library in one pass.

The permanent fix: stop letting recordings accumulate

Manual cleanup is a treadmill. Clear enough space to record, record a few more sessions, hit the cap again, clear again. The cap never solves itself — it just resets you back to the same loop.

The permanent fix is to move every recording out of Zoom automatically, so cloud storage never builds toward the cap in the first place. Every recording that lands in Google Drive is headroom Zoom doesn't have to hold. If that transfer happens within minutes of each session's recording being ready, your cloud storage level stays low as a steady baseline — not something you periodically race to fix. Google Drive doesn't auto-delete files, so the archive grows without the clock running out.

RecordFlow is built for this job. Connect it once — sign in with Zoom, connect Google Drive, pick a destination folder — and every cloud recording copies to Drive automatically within minutes of Zoom marking it ready. RecordFlow never stores your recordings — files transfer directly from Zoom to your Drive, so sensitive session content stays between you, your client, and Google. The full how-to on backing up Zoom recordings to Drive covers setup and troubleshooting. Once the backup is confirmed in Drive, you can safely clear the Zoom copy on your schedule — the safe sequence for doing that without losing a recording you meant to keep is worth reading before you start deleting.

The end state: a growing library in a place you control, and a Zoom cloud storage level that never again interrupts a session.

If you keep landing back here

Some accounts hit this wall not because cleanup slipped but because the archive genuinely outgrew the plan. If your library is measured in hundreds of gigabytes, "buy more Zoom storage" and "buy a bigger Drive plan" are the same answer twice, and neither gets cheaper as the archive grows. There is a third option — object storage you own, billed per gigabyte with no tier to move up to — and the arithmetic against Zoom's own published add-on rates is stark enough to be worth ten minutes: what Zoom recording storage actually costs, and what the alternatives cost.

The "Zoom storage full" email always lands at the worst moment — usually right before your next session — and the first thing you do is Google what to do about it. There's a safe way to free up Zoom cloud storage fast, without paying for an add-on and without the gamble of deleting a client recording you can't get back. The whole trick is the order you do things in.

Why Zoom fills up so fast

Zoom Cloud storage is small and shared. Most paid tiers include 10 GB pooled across all Licensed Users on the account — not per person — and a single hour of HD recording runs a few hundred megabytes once Zoom finishes compressing it. A coach running a dozen sessions a week burns through the included pool in a couple of months. On a team account it's faster still: every host draws from the same shared pool, so one heavy week from one person can wall off everyone.

When the pool fills, Zoom can block new cloud recordings until you free space or buy more. So the cap becomes a recurring chore: delete to make room, record, hit the cap again, delete again. The treadmill.

Manual cleanup is where recordings get lost. The Zoom recording list shows topics and dates and not much else; under time pressure it's genuinely easy to trash a client session you meant to keep. And Zoom's trash is not a backup — deleted cloud recordings are typically recoverable for 30 days, and once that window closes the recording is gone for good. (For a full breakdown of all the ways recordings can disappear from Zoom — not just manual deletion — see What Disappears From Zoom Cloud, and When.)

The safe order: back up, verify, then delete

The fix isn't "stop deleting." It's "never delete a recording that doesn't already live somewhere else." Three steps, always in this order:

1. Back up. Copy the recording — video, audio, transcript, chat — to a place you control, like a Google Drive folder.
2. Verify. Confirm the copy actually landed. A backup you haven't checked is a hope, not a backup.
3. Delete. Only now delete the cloud recordings from Zoom and reclaim the space.

Reorder or skip a step and you're gambling again. The reason this works is that the durable copy lives somewhere that doesn't delete itself: Google Drive doesn't auto-delete files, and even an explicit delete sits in Drive's own trash for 30 days first. Your recordings only leave Zoom — they never leave your hands. (For the full case on why Drive is the better long-term home, see Google Drive vs Zoom Cloud.)

How RecordFlow automates it safely

Doing back-up-then-verify-then-delete by hand every week is exactly the kind of chore that falls apart on a busy week. RecordFlow runs the whole sequence for you — and the safe order is built into how it works, not bolted on after.

First, set up the backup — about 60 seconds: sign in with Zoom, connect the cloud storage you use — Google Drive, OneDrive, Dropbox, or YouTube — and pick a folder or channel. From then on, every cloud recording lands there within minutes of Zoom marking it ready (the companion how-to walks through the Drive setup). That part is read-only — RecordFlow never asks for permission to delete anything.

Auto-delete is a separate, opt-in switch in Settings. It's off by default, and turning it on is the only time RecordFlow asks Zoom for the delete permission — if you never enable it, that permission is never requested, and read-only users are never prompted for it. Once it's on, RecordFlow waits until every file from that meeting has been archived to your destination and the upload confirmed — on YouTube, that means waiting for YouTube to finish processing the video and confirming it stored the size RecordFlow uploaded — then holds for a three-day grace period before moving the recording to Zoom Trash. Nothing is removed that wasn't safely copied first, and Zoom's 30-day Trash window stays available as a final safety net. You can switch it back off at any time.

If you already use Zoom's own auto-delete

If you've turned on Zoom's own recording auto-delete — the configurable-day retention policy in your recording settings — let RecordFlow handle the cleanup instead. Zoom's setting runs on a fixed schedule and doesn't check whether your copy is safely in Drive yet, so it can delete a recording before it's ever been archived. RecordFlow only trashes a recording once it's verified in your destination storage — and then waits three days as a buffer — so you get the same storage savings without risking a recording that was never backed up.

A prospect is deciding between two coaches. Same niche, similar experience, prices within a few hundred dollars of each other. One sells "twelve sessions of one-to-one coaching." The other sells "twelve sessions — each one recorded, transcribed, and delivered to a private folder that's yours to keep." Which one feels like more?

The work might be identical. But one offer is a promise, and the other comes with something the buyer can picture holding. That difference is worth money — it's how the second coach charges more for the same hours — and it costs almost nothing to provide.

Why intangible work is hard to price

Coaching is intangible. You sell a transformation that happens in conversation, and the buyer can't inspect it before they pay — they're buying a promise. In a classic Harvard Business Review essay, marketing professor Theodore Levitt argued that when you ask customers to buy promises, you have to give them tangible reassurances of quality — the cues people reach for when they can't hold the thing itself. It's why service businesses lean so hard on the physical signals around the work: the bound report, the welcome kit, the polished follow-up.

A session recording is the most natural tangible cue a coach has, because it isn't a prop bolted onto the offer — it is the work, captured. An hour of focused, one-to-one attention, preserved in a form the client can replay, search, and return to. When you hand that over, the intangible suddenly has an artifact attached to it. The buyer stops trying to value thin air and starts valuing something they can see — which is exactly the shift that lets you name your rate with confidence.

This is the pricing-and-positioning side of a reframe we make in detail elsewhere: that the recording is the client's asset, not your filing problem. That post is about what clients do with a replay. This one is about what the artifact does to your offer.

Use the deliverable to charge more for coaching

Vague value is hard to charge for; named inclusions are easy. "You'll get coaching" is a promise. "Every session recorded, transcribed, and delivered to a private folder you keep" is a line item — concrete, easy to picture, and not something a prospect can get from a coach who hasn't set this up. You don't need every client to replay every session for this to pay off — on a sales call, the named inclusion does the work whether or not the buyer ever opens the folder. It's a small, specific addition to your value proposition.

A few ways coaches put it to work:

• As a headline inclusion in the offer. List it next to the sessions themselves: the calls, plus the recording and a searchable transcript of each. It reads as thoroughness — you're the coach who makes sure nothing from the work gets lost between sessions.
• As the line between tiers. If you sell more than one coaching package, recordings-plus-transcripts is a clean differentiator for the higher tier. The entry package gets the sessions; the premium package gets the sessions and a permanent, searchable library of them. You're charging more for genuinely more, not for an arbitrary gate.
• As a reason to raise — or hold — your rate. Concrete added value works in both directions: it gives you something to point to when you set a higher number, and something to defend when a prospect pushes back. The move that quietly erodes a coaching business is discounting — a recorded, transcribed, well-organized session archive lets you do the opposite: raise your rate because you're genuinely offering more, instead of knocking a few hundred dollars off to close.

What makes this a margin decision and not just a marketing one is that the cost of delivering it approaches zero — once it's automatic. If recording and filing every session is a manual chore (download the file before it expires, rename it, move it to the right client folder, share it), then your "premium inclusion" is really unpaid admin you've promised to do every week, and it's the first thing to slip during a busy stretch. A deliverable you have to remember isn't a deliverable; it's a liability. The economics only work when the artifact produces itself.

How RecordFlow fits

That's the gap RecordFlow closes. Setup is a one-time, roughly 60-second connection — sign in with Zoom, connect Google Drive, choose a folder. After that, the moment a Zoom cloud recording is ready, RecordFlow copies the files — the video, the audio-only file, the chat log, and the transcript — into a Google Drive folder you own: one folder per meeting, named with the date and the meeting topic, grouped by year. The files move straight from Zoom to your Drive; RecordFlow never keeps a copy on its own servers, which matters when the session was confidential. (The full mechanics are in the pillar guide on backing up Zoom recordings to Drive.)

Two details make the deliverable feel premium rather than like a raw file dump. Alongside the recording, RecordFlow uploads a clean Google Doc transcript — the raw caption file reformatted into readable, timestamped paragraphs with each speaker named — so the client receives a searchable document, not a wall of caption fragments. And because the folder is yours, you share it on your terms with a Drive link the client already knows how to open; Drive's per-recipient sharing keeps each client's library private to that client. The premium inclusion you named on your sales page then gets delivered every session, without you touching it.

The work you do in a coaching session is the same whether or not it's recorded. What changes is what the client walks away holding — and what you can credibly put on the page when you name your price. The artifact was there in the call all along. You were just letting it evaporate the moment the call ended.

Three days after a session, a client emails: "Could I get a recording of our coaching session? There was something you said about boundaries I want to listen to again." And you go looking. Maybe it's in Zoom Cloud, maybe it expired under a retention setting you configured months ago, maybe you never recorded it at all. Either way, you're now spending twenty minutes hunting for — or apologizing for not having — something the client experienced as the most valuable part of working with you.

That email is a signal, and most coaches misread it. It feels like an admin request. It's actually a client telling you the recording is part of what they bought.

Should you record coaching sessions?

Yes — with consent, and as long as you actually hand the recording over. The hesitation is rarely about value; it's about storage and effort, the worry that a recording is one more file to babysit. But the session is something the client already paid for, and the only real prerequisites are clear permission up front (a relationship matter, and depending on where you both practice, a legal one) and a reliable place to put it. Get those two right and recording is pure upside — which is what the rest of this post is about.

The reframe: the recording is the client's asset

We tend to think of a session recording as the coach's problem — a file that eats Zoom storage, triggers the "your cloud is full" email, and has to be managed. So the default is to not record, or to record and quietly let it expire.

Flip it. The recording isn't overhead you store for yourself. It's a deliverable the client already paid for, sitting unused. An hour of focused, one-to-one work — the kind a client replays, references, and learns from between sessions — and in most coaching relationships it evaporates the moment the call ends. The reframe is simple: stop treating the recording as your filing problem and start treating it as the client's asset. Everything else follows from that.

What clients actually do with a session recording

When you ask coaches why they don't send recordings, the honest answer is usually "I'm not sure anyone watches them." Here's what the clients who do get them actually do:

1. They stop frantically note-taking and stay present. A client scribbling notes is half-listening. When they know the recording is coming, they can put the pen down, look at you, and do the actual work of the session. The replay becomes their notes — better notes than they'd have taken, because they were paying attention instead of transcribing.

2. They re-watch the breakthrough moment. Most sessions have one — the reframe, the question that landed, the thing they didn't want to admit out loud. In the room it goes by in seconds. On a replay they can sit with it, rewind it, and let it actually change something.

3. They revisit what they committed to. Coaching works between sessions, not just in them. The ICF's core competencies frame a coach's job as partnering with clients to integrate new learning and build accountability — turning insight into action after the call ends. A client who can replay the moment they committed to a next step is far more likely to follow through than one relying on a fading memory of "I think I said I'd do something."

4. They re-listen when they're stuck. The gap between sessions is where the hard part happens. A client who hits a wall on Wednesday doesn't have to wait until next week — they can go back to the relevant ten minutes and hear, in your voice, the thing that helps. The recording extends your support into the days you're not there.

5. They search the transcript. "What did my coach say about X?" is a real question clients ask themselves — and a recording answers it slowly (scrub through an hour of video) while a clean transcript answers it in seconds. When the session also lands as a readable, searchable document, the replay stops being a linear video and becomes something they can search by keyword — Ctrl-F to the exact moment they're looking for.

None of these require the client to be diligent. They require the recording to exist and be easy to open. And it doesn't matter whether every client watches the whole hour: the one who re-watches the breakthrough, or searches the transcript at 11pm before a hard conversation, got more from you than a dozen who never opened it. Most coaches never find out, because most never send one — which is exactly the gap that makes sending one a differentiator.

How RecordFlow fits

The reason coaches don't send recordings is rarely philosophical — it's friction. Recording, finding the file before it expires, downloading a multi-gigabyte video, and getting it to the client is a handful of manual steps that quietly don't happen during a busy week.

RecordFlow removes the steps. Setup is a one-time, roughly 60-second connection — sign in with Zoom, connect Google Drive, pick a folder. After that, the moment a Zoom cloud recording is ready, it copies the files — video, the audio-only file, the chat log, and the transcript — into a Google Drive folder you own: one folder per meeting, named with the date and the meeting topic, grouped by year. (The full mechanics are in the pillar guide on backing up Zoom recordings to Drive.) The files move straight from Zoom to your Drive — RecordFlow never keeps a copy of the recording on its own servers, which matters when the session was confidential. Nothing to remember, nothing to download. The recording is simply there, in a folder you control, ready to hand to the client with a Drive share link they already know how to open.

Two things make that handoff better than a raw video link. First, alongside the recording RecordFlow uploads a clean Google Doc transcript — the raw caption file reformatted into readable, timestamped paragraphs with each speaker named. That's the searchable "what did my coach say about X?" artifact, and because it's a native Google Doc it also opens in the Drive-native AI tools your clients may already use (here's the transcript-to-Doc workflow). Second, because the folder is yours, you decide what to share and with whom — Drive's per-recipient sharing keeps each client's replay private to that client, without ever handing out a Zoom account or a raw cloud link.

The shift here costs you almost nothing once recordings save themselves: you record (with consent), and you send the link. What the client gets is the difference between a session that ended and a session they can return to. That's the most underused asset in coaching — the replay you never sent.

You've finished your coaching hours, your education is done, and you sit down to assemble your ICF credential application. Then you hit the one item that isn't a number on a form: the recorded session. You scroll back through months of calls looking for one that runs the right length, with a client who consented, where the coaching was genuinely some of your best — and you realize the session you're picturing was never saved, or you can't tell which file it is anymore. The work was real. The evidence of it wasn't kept.

This post is about the half of that problem you can actually engineer away: making sure a qualifying session — and a usable transcript — is always there when it's time to submit. We'll cover what ICF asks for, why coaches get caught out, and where a reliable archive fits. (We'll also be clear about what an archive doesn't do: meeting ICF's criteria is on you, not your storage.)

What ICF actually asks for

For some credential paths, ICF's performance evaluation requires you to submit recorded coaching session(s) and a written transcript of each. The specifics depend on your credential and your application path, and they're set by ICF — so treat the summary below as orientation and confirm the current rules against ICF's own documentation before you rely on them.

As of this writing, ICF's performance evaluation requirements work roughly like this:

• How many recordings. The ACC Portfolio path calls for one recorded session with a transcript. The PCC Portfolio path and the MCC paths call for two. If your ICF-accredited education program already included a performance evaluation in its curriculum — the Level 1 and Level 2 program paths for ACC, and the Level 2 path for PCC — you may not need to submit one separately at all. Know which path you're on before you assume you need a recording.
• Session length. The recording must be a full, unedited session running between 20 and 60 minutes. A session longer than 60 minutes won't be scored, so a sprawling call doesn't count — you need one that lands inside the window from start to finish.
• The audio file. ICF accepts common audio/video formats (MP3, WMA, MP4, or M4A) as a single file, and caps the upload size (95 MB at the time of writing). A 20–60 minute audio-only export comfortably fits that budget; a full-resolution video usually doesn't, which is why the audio file is the one you want.
• The transcript. This is the part coaches underestimate. ICF asks for a verbatim (word-for-word) transcript, with the coach and client identified and placed on separate lines, timestamps at every change of speaker, in the same language as the session, submitted as a Word document (.doc or .docx). A rough auto-summary doesn't satisfy this; it has to be the real exchange, formatted ICF's way.

The headline: the requirement isn't just "have a recording." It's "have a specific kind of recording, with a specifically formatted transcript, for the right session." Which is exactly why finding it after the fact is so painful.

The practical problem: you don't know in advance which session counts

Here's the trap. You can't reliably pick your qualifying session ahead of time. The call where the coaching really sings — clean agreement, a real shift, the kind of session an assessor wants to see — isn't something you schedule. It happens, and you notice afterward. By then, if you weren't recording, it's gone.

So the only safe posture is to capture consistently: record the sessions you have consent to record, keep them all, and choose the best one when it's time to apply. That turns "did I happen to save the right call?" into "which of these saved calls is strongest?" — a much better problem to have.

The second half is retrieval. Cloud recordings are easy to lose track of. They expire under retention policies you set months ago and forgot, they get bumped when storage fills, and a folder of meetings named only by date tells you nothing about which one had the breakthrough. Doing the save-and-organize step by hand is the part that quietly breaks during a busy stretch — and a busy stretch is exactly when your best sessions tend to happen.

If you're weighing where recordings should live long-term, the comparison of Drive vs. cloud-recording storage covers the retention and cost side in detail.

How RecordFlow fits

RecordFlow does one narrow thing: the moment a Zoom cloud recording is ready, it copies the files — video, the audio-only file, the chat log, and the transcript — into a Google Drive folder you own, in a per-meeting folder named with the date and the meeting topic. Every session you record is archived automatically and stays findable, so when application time comes you're choosing from a complete set rather than hoping the right call survived. If you haven't set the backup up yet, the companion how-to on backing up Zoom recordings to Google Drive automatically walks through the one-time setup.

Two pieces map directly onto the ICF requirements, with one honest caveat. The audio-only file Zoom produces is already in an accepted format and small enough to fit the upload cap, so it's the file you'd submit. Alongside the raw .vtt, RecordFlow also uploads a clean Google Doc transcript — consecutive lines from the same speaker merged into paragraphs, each prefixed with a timestamp, the speaker's name in bold (the full mechanics are in the transcript-to-Doc post). That Doc is a strong starting point: you'd open it, export to Word, and format it to ICF's exact spec — verbatim, coach and client on separate lines, a timestamp at every speaker change.

What RecordFlow does not do is hand you a finished, ICF-compliant submission. It is not affiliated with or endorsed by ICF, and it doesn't certify that a recording or transcript meets the evaluation criteria. It stores and retrieves your sessions reliably; verifying length, audio quality, verbatim accuracy, and transcript formatting — and meeting every current ICF rule — is your job as the coach.

The archive you build for credentialing does double duty. Those same saved sessions are what let you give clients the recording as a deliverable, make session replays a premium part of your offer, and deliver those recordings professionally — the credentialing archive and the client-facing one are the same folder. The full set of client & class recording workflows covers the rest of what that archive unlocks once your sessions are safely in a folder you own.

The goal is simple: never let "I didn't keep it" be the thing standing between you and a credential you earned. Record consistently, keep every session somewhere you control, and the one you need will be there when you reach for it.

You want to ask Gemini Notebook (formerly NotebookLM — Google renamed it in July 2026; same product, same URL, new name) "what did all my coaching clients ask about this month?" The answer is in your Zoom recordings — except those recordings live in Zoom Cloud, the transcripts are .vtt files no AI tool can read cleanly, and the only way to get them into Gemini Notebook today is to download each one and paste it in by hand. The unlock is moving the recordings — and a readable transcript — into Google Drive, where every AI tool you already use can reach them.

To convert a Zoom transcript into something those tools can actually read, you need it in Drive as a clean Google Doc — not the raw .vtt Zoom hands you. This post is the workflow: what Zoom actually gives you, why the raw .vtt is a dead end for AI tools, and how to turn each transcript into a readable Google Doc (which also downloads to a Word file in two clicks) once it's in Drive. If you haven't set up the backup itself yet, the companion how-to on backing up Zoom recordings to Google Drive automatically covers the 60-second setup.

If you've already read the companion post on where Zoom recordings should live, this is the next layer — what becomes possible once they're in Drive.

What Zoom actually gives you

Zoom Cloud can generate two .vtt artifacts for a recorded meeting: an audio transcript (recording type audio_transcript — the post-meeting transcription of the spoken audio) and, when live captions were enabled during the meeting, a closed-caption file (recording type closed_caption). The Zoom documentation on audio transcripts walks through enabling the feature on your account. The audio transcript is the one most coaches want — it covers the whole meeting whether or not anyone turned captions on.

The format itself is WebVTT, a W3C caption standard built for video players, not for reading. A real Zoom .vtt looks like this:

WEBVTT

1
00:00:03.120 --> 00:00:06.480
Sarah Chen: So the thing I keep coming back to is

2
00:00:06.480 --> 00:00:09.760
Sarah Chen: that I can't tell if I'm building the right thing.

3
00:00:09.760 --> 00:00:11.200
Marcus Webb: Yeah. Say more about that.

It's parseable by code, but it's not readable as a document. Every three-second caption is its own cue. The same speaker's thought gets fragmented across five or six cues. Paste that into Gemini Notebook or a chat-based LLM and you've handed it a stack of timestamps and noise to work around before it can read the content.

Why Zoom Cloud is a dead end for AI tools

Zoom Cloud stores the recording where Zoom can find it. The problem is that nothing else can. Gemini Notebook accepts Google Docs and Slides from Drive, PDFs and text files, web URLs, YouTube videos, audio uploads, and pasted text — not Zoom Cloud URLs. Gemini in Workspace reads files and folders from your Drive. The transcript, note-taking, and knowledge-base tools coaches and consultants stack on top of meetings almost always integrate with Drive; almost none integrate with Zoom Cloud as an archive destination.

Drive is the integration point. Once a recording and its transcript live in a Drive folder you own, every AI tool you already pay for can reach them. That's the unlock; the rest of this post is what to do with it.

Convert the Zoom VTT into a Google Doc

The transcripts arrive in Drive in two forms. The raw .vtt is always there — that's the source file, untouched. Alongside it, RecordFlow uploads the same transcript as a native Google Doc: cue numbers and end-times dropped, consecutive lines from the same speaker merged into paragraphs, each paragraph prefixed with a rounded [HH:MM:SS] start, and the speaker's name bolded. The same exchange above lands as:

[00:00:03] Sarah Chen: So the thing I keep coming back to is that I can't tell if I'm building the right thing.

[00:00:09] Marcus Webb: Yeah. Say more about that.

It's the same content. It now reads like a transcript instead of a caption file. That single change is what makes the downstream workflows work — a native Google Doc previews in Drive, opens cleanly in Gemini Notebook, and pastes into Gemini or any other AI chat without timestamp clutter. And because it's a real Google Doc, you can download it straight to a Microsoft Word (.docx) file — File → Download → Microsoft Word — if you'd rather convert the Zoom transcript to Word for editing or sharing, without hand-stripping cue numbers out of the .vtt first.

The conversion is lossy on purpose — end-times and per-line cue boundaries go away. That's why the raw .vtt stays in the folder alongside it. If you ever need the original, it's still there. If you ever need to import the same transcript into a video player, the .vtt is what you use. The Google Doc is the version you hand to an AI.

Both files land automatically every time RecordFlow syncs a new recording — no setting to flip, no separate enable step. Older meetings synced before the Doc upload shipped were backfilled, so the Google Doc is sitting next to the existing .vtt in your archive too.

Once your transcripts are readable Google Docs, the rest of the Zoom recordings & AI guides cover what else opens up. Here are four workflows to start with.

Four workflows once your transcripts are in Drive

1. Gemini Notebook — ask questions across a quarter of client calls

Gemini Notebook accepts Google Drive Docs as sources (check the current per-notebook source cap on your tier). Create a notebook per client (or per quarter, or per program cohort), add the Google Doc transcripts as sources, and ask the questions you can't search for: What themes came up across these eight coaching calls? Which commitments did this client make and never revisit? When did we first talk about the co-founder conflict? Gemini Notebook cites the source document for every claim, so you can jump from an answer back to the exact transcript.

2. Gemini in Workspace — summarize one recording at a time

Gemini in the Workspace side panel opens directly on a Google Doc and can summarize, extract action items, pull decisions, or answer a question grounded in just that one transcript. This is the right tool for "give me the action items from yesterday's strategy session" — single document, fast answer, no notebook setup. The Drive-native Doc is what makes this work; Gemini won't process a raw .vtt the same way. For the wider set of things the rest of Google Workspace can do with your Zoom recordings once they're in Drive, that companion post walks through Docs, Vids, and search.

3. Transcript and meeting tools — point them at the Drive folder

If you use a meeting-intelligence or note-taking tool that reads Drive, point it at the folder your RecordFlow transcripts land in. It can index, tag, and search across the archive the same way it does for documents you author yourself. The "where are my old meeting notes?" search problem stops being a Zoom-specific problem and becomes a normal Drive search.

4. Group programs and cohorts — share the transcript, not the recording link

For group programs, retreat replays, or cohort-based courses, the transcript Doc is often what participants actually want to revisit — searchable, skimmable, copy-pasteable. Drive's sharing controls let you restrict access by email so a cohort's transcripts follow the same paid-access rule as the rest of the program, without ever handing out a raw Zoom share link.

If it's a recurring class rather than a one-off cohort call, naming the Zoom meeting with a slash — Cohort 3/Week 6 — lets RecordFlow collect every week's session and transcript into one shared class folder instead of a new one each time, so a Gemini Notebook you point at the folder picks up the whole series without re-adding sources every week. It's off by default — the linked docs below cover how to turn it on. It applies to future syncs only. Full mechanics.

Setup notes that pay off later

Two small choices make the AI workflows above much smoother:

• You don't have to reorganize first. RecordFlow groups recordings into year folders by default. Gemini Notebook lets you cherry-pick individual Google Docs as sources from anywhere in Drive, so you can build a per-client (or per-cohort) notebook without moving any files. If you'd later prefer client folders for general Drive search, you can reorganize whenever you want.
• Don't rename the meeting folders. RecordFlow creates one folder per meeting and names it with the start date and the meeting topic (e.g. 2026-06-03-Quarterly review). That folder name is what disambiguates "which session?" when you pick the transcript Doc as a Gemini Notebook source or grep through Drive search — the files inside express the artifact type (audio_transcript, shared_screen_with_speaker_view, etc.), not the meeting.

What this is not

RecordFlow is not an AI tool. It doesn't summarize your meetings, doesn't answer questions about them, doesn't sit between you and your transcripts. It moves your Zoom recordings and a clean transcript Doc into a Google Drive folder you own, and from that point on the AI tools you already use can reach them. The intelligence — what to ask, what to do with the answer — stays with you and the tools you chose.

If you want a single backup tool whose job is to put recordings and readable transcripts where Drive-native AI can find them, that's the job RecordFlow does.

How RecordFlow fits

Sign in with Zoom, connect Drive, pick a folder. The moment Zoom marks a recording ready, RecordFlow copies the video, audio, chat log, and .vtt transcript into that folder — and uploads a readable, AI-ingestible Google Doc version of the transcript alongside the raw .vtt. From there, the rest of your stack — Gemini Notebook, Gemini, whatever you reach for next — can read your meetings without a download step.

If the previous post argued that recordings belong on Google Drive, there's an obvious follow-up: why not just hold the meeting on Google Meet, where the recording already lands in Drive natively? It's a fair question, and the honest answer isn't "Zoom is better." It's that the meeting tool and the storage layer are two separate decisions, and consolidating them costs more than it saves for most solo coaches, consultants, and therapists.

This post is the companion to Google Drive vs Zoom Cloud: Where Your Meeting Recordings Should Live. If you've already decided Drive is the right destination, here's why the upstream question — meet on Zoom or Meet? — usually doesn't have to be a switch.

What Google Meet recording does well

Credit where it's due. Meet's recording story has real advantages when it fits your stack:

• Native Drive landing. Recordings save to the host's "Meet Recordings" folder in My Drive automatically — no transfer step, no third-party tool. Google documents the destination path explicitly.
• Single sign-on. One Google account covers the meeting, the storage, the calendar invite, and the docs you share during the call. Fewer integrations to fail.
• Built-in AI notes. "Take notes for me" (Gemini) generates a meeting summary alongside the recording on supported Workspace tiers.
• No third-party tooling to maintain. Anything Workspace already owns is one fewer vendor to evaluate, pay, and remember the password for.

If your clients are already in Workspace, your meetings are routine 1:1s, and you don't lean on features Meet doesn't have, that's a real reduction in moving parts.

Where Zoom still has the edge

For practitioners whose work depends on the meeting itself, three categories matter:

• Third-party guests. Zoom join links work for anyone with a browser. Meet links can prompt non-Google participants to sign in or be admitted from a lobby depending on host settings — friction you don't want with a first-session client.
• Breakouts and larger groups. Zoom's breakout-room UX is more mature, participant caps at the entry-level paid tier are higher, and call quality on weaker connections is well-earned. For cohort programs and workshops, it matters.
• Ecosystem familiarity. Many clients already have Zoom installed and know how to use it. Switching that habit is a tax paid in tiny moments of confusion on every new engagement.

Meet recording isn't actually free

The "Drive is free, so Meet must be free" framing skips a step. Recording in Meet requires a Workspace tier that includes the feature — typically Business Standard ($14/user/month) and up at current pricing. It is not available on personal Google accounts, on the lowest-cost Workspace tier, or on the Workspace for Nonprofits free tier.

So if you're a solo coach on a personal Google account paying for Zoom Pro and Google One, switching to Meet recording is not a downgrade-Zoom-to-zero move. It's a "drop Zoom Pro, add Workspace Business Standard" move, and the math usually doesn't favor it — especially once you factor in seat counts for VAs or partners.

The hybrid most solo practitioners settle on

The pattern that consistently works for practitioners I talk to is the simplest one: meet on whichever tool fits the call, store on Drive either way.

• Client-facing work. 1:1 sessions, group programs, workshops, and anything where the participant experience matters — Zoom.
• Internal collaboration. Team standups, async loom-style recordings, calls with collaborators already in your Workspace — Meet, if it's easier.
• Long-term storage. Google Drive, in folders organized by client or program.

The benefit of decoupling meeting from storage is that you stop having to pick a side. A client who hates installing apps gets a Zoom link in the browser; a colleague already in Workspace gets a Meet link; both recordings end up in Drive, where you can organize them under whatever folder structure you already use — alongside the contract, the invoice, and the session notes.

How RecordFlow fits

RecordFlow exists for the hybrid. If you keep meeting on Zoom — because your clients expect it, because breakouts matter, because the link just works — RecordFlow puts every cloud recording into a Drive folder you choose, within minutes of the meeting ending. Passcode-protected sessions and multi-hour calls go through the same path. You get Drive as the storage layer without having to change a thing about how meetings actually happen.

An NGO board meeting recording vanishes a month after the AGM — the executive director changed roles, the license rotated to someone else, and the cloud copy is now gated behind an admin screen no one on the new team can reach. The recording was the only contemporaneous record of a vote that's now being asked about. This is the version of "Zoom storage almost full" that nonprofits hit, and it's avoidable.

RecordFlow exists because I watched this happen at a Polish watchdog NGO I work with — a recording of a board vote went missing exactly when someone asked to see it, and there was no good answer. The fix isn't a bigger Zoom plan. It's the 100 TB of Google Drive storage your nonprofit may already have, sitting unused.

Google Workspace for Nonprofits and Zoom: the 100 TB no one talks about

Workspace for Nonprofits is Google's free tier for eligible organisations: $0 per user, 100 TB of pooled storage across the org, Gmail with your domain, Drive, Calendar, and Meet. Eligibility runs through Goodstack verification (Google's global validation partner, formerly Percent) — usually a few business days to a couple of weeks once your paperwork is in.

100 TB is enough headroom that most small and mid-sized nonprofits will never touch it. A team of 15 recording every board meeting, every training session, and every community call in HD won't fill 5 TB in a decade. And yet the same organisations routinely pay Zoom for add-on storage — $10/month for 30 GB, up to $500/month for 5 TB — because the 10 GB per licensed user that Zoom Pro and Business pool at the account level runs out faster than you'd think (a four-person nonprofit on Pro shares a 40 GB pool — one long quarterly AGM and a few training sessions get you most of the way there). It's the budget equivalent of renting a storage unit while the basement sits empty. For the broader cost/retention math, the Zoom Cloud vs Google Drive comparison lays it out side-by-side.

Why nonprofits especially need a recording archive

For an accountability-minded NGO the recording isn't a souvenir, it's evidence:

• Board meetings and AGMs. Members and regulators occasionally ask to see how a decision was made. The minutes are the formal record; the recording is the unambiguous one.
• Training and onboarding. Staff turnover at small NGOs is higher than at most for-profits. The two-hour onboarding call you ran in March is the cheapest way to onboard the person who joins in September — if you can still find it.
• Community calls and consultations. Funders increasingly want to see participation evidence. A recording disappearing six months after the call closes a door you'd want open.
• Reach beyond the live call. The people who watch the recording a week or a year later aren't competitors — they're often the supporters you most wanted to reach. A file in Drive can be embedded on the website, linked from a newsletter, or shared with a partner org; a Zoom share link with "require authentication to view" quietly cannot. Well-organised archives are how a single hour of staff time keeps compounding into impact.
• Transparency obligations. Watchdog organisations, public-interest groups, and grant-funded projects often have explicit retention obligations. "We had it but Zoom auto-deleted it after 120 days" is not an answer that satisfies an auditor.

Zoom Cloud is built around the meeting that produced the file. Once the meeting ends, the recording is, in product terms, a notification you've already acted on. When the storage cap fills, new cloud recordings simply stop being saved; existing files aren't auto-purged to make room. Auto-delete policies tidy things up on a schedule (deletions land in Trash for 30 days before permanent removal, so a recent misfire is recoverable). Licenses rotate between users when a team is small. None of that is malicious; all of it loses recordings.

What Workspace for Nonprofits won't do: record Meet calls

The free Workspace for Nonprofits tier doesn't include cloud recording in Google Meet. You'd need the Business Standard upgrade (heavily discounted for nonprofits — around $3.50/user/month on an annual commitment — but not zero) to record natively in Meet. Zoom itself also offers a nonprofit discount via Zoom Cares — up to 50% off paid plans for eligible organisations — but storage add-ons aren't free at that tier either, so the underlying math doesn't change.

The obvious follow-up question is can we upgrade only the two or three people who actually need to record? For a small association with low membership fees, or an org built around volunteers who bring their own Google accounts, paying for the whole roster to scratch the recording itch of a few staff makes no sense. Unfortunately, Google's own upgrade documentation is explicit on this point: "When you upgrade, everyone in your Google Workspace account gets the same subscription". Partial-domain or per-user licensing for Workspace for Nonprofits isn't supported through the standard self-serve upgrade path. A Google Cloud reseller can sometimes provision mixed editions, but that moves billing and admin out of the self-serve console — rarely worth the overhead for an NGO that needs two or three recording seats.

So for most NGOs the calculation lands here: Zoom is already the meeting tool the board, the donors, and the community use; switching the meeting platform to chase free recording is not the win it sounds like, and partially upgrading Workspace to get Meet recording for the handful of users who need it isn't actually on the menu.

The cheaper move is to keep Zoom as the meeting tool, and let Drive be the archive. Record in Zoom, store in Drive automatically, retire the Zoom storage add-on. You get the platform everyone already knows, the free archive you're already entitled to, and one fewer line item on the operating budget.

The simplest workflow

1. Apply for Workspace for Nonprofits if you haven't already, via Google's nonprofit application — Google routes verification through Goodstack globally. Approval typically takes a few business days to a couple of weeks; nothing else on this list needs to wait.
2. Turn on cloud recording in Zoom. Zoom Settings → Recording → Cloud recording must be on. Without it, recordings only save to whichever laptop hosted the meeting.
3. Create a dedicated Drive folder. /Board Meetings/ or /Recordings/2026/ — a shared drive is ideal for nonprofits because it survives staff turnover (files in a shared drive don't disappear when the original owner leaves).
4. Connect an automation that copies Zoom recordings into that folder. RecordFlow is built for exactly this; the companion how-to walks through the setup.
5. Let Zoom's auto-delete do its job. Once you've watched a few backups land safely in Drive, turn on Zoom's retention policy at 30 or 60 days. The Zoom add-on storage becomes unnecessary.

What to check before you turn off the Zoom add-on

How RecordFlow fits

RecordFlow does one thing: the moment Zoom marks a cloud recording ready, RecordFlow copies it — video, audio, transcript, chat log — into a Google Drive folder you choose. Setup is sign in with Zoom, connect Drive, pick a folder; about 60 seconds. Passcode-protected board meetings, multi-hour AGMs, and large files all work the same way. A webhook plus an hourly sweep catches anything Zoom's notification didn't deliver. RecordFlow is free during beta.

The "Zoom storage almost full" email is the moment most coaches realize their client recordings — the actual deliverable, the thing they re-watch before next week's session — have been sitting in a place that was never designed to keep them long-term. The real Zoom Cloud vs Google Drive question isn't should I clean up Zoom storage. It's where should these recordings live in the first place?

This post is the honest comparison for solo coaches, consultants, online educators, and small teams already on a paid Zoom plan and a Google account. Four things consistently make Google Drive the better long-term home for your recordings, and we'll also flag the cases where Zoom Cloud is the right call.

If you're already convinced and just want the workflow, the companion guide on backing up Zoom recordings to Google Drive automatically walks through the setup.

Why this question matters

Zoom Cloud is built around a meeting. Once the meeting ends, the recording is, in Zoom's product terms, a notification artifact: it tells you it's ready, points you at it, and assumes you've moved on. For a coach, a therapist, or a tutor, that recording isn't an artifact. It's work product. It's the thing the client paid for, the reference for next session, the piece of evidence you might need 18 months from now if a relationship goes sideways.

Storing work product in a tool optimized for "archive and forget" is the source of most missing-recording stories. The fix is to treat the recording like a document and put it where you keep documents.

How much does Zoom cloud storage actually cost?

Zoom's add-on cloud storage is priced per gigabyte. The cheapest published Zoom storage add-on is roughly $10 a month for 30 GB. Higher tiers exist; the per-GB rate doesn't get dramatically better.

Google's storage is priced per terabyte. Google One Premium is $99.99 a year for 2 TB, which works out to under $0.005 per GB per month. Workspace plans bundle even more: 30 GB on Starter, 2 TB pooled per user on Standard, 5 TB on Plus.

Three concrete scenarios make the gap concrete:

• Solo coach, Zoom Pro, 15 sessions a week. A typical hour of HD recording is a few hundred megabytes once Zoom's compression finishes, so 60 sessions a month adds up fast and the 10 GB pool included with Zoom Pro and Business is gone before quarter-end. Buying the cheapest add-on costs another $10 a month. The same coach's Google One 100 GB plan is around $2 a month, and a 2 TB plan would be enough recordings for years.
• Ten-person consultancy on Workspace Standard. Already paying for ~20 TB of pooled Drive storage that's mostly empty. Recording every client call into Zoom Cloud and paying for an add-on is asking the business to pay for storage twice.
• Nonprofit on Workspace for Nonprofits. The base tier is free and the Standard upgrade is heavily discounted; the marginal cost of storing recordings on Drive is effectively zero.

For most readers, the right comparison isn't "Zoom add-on vs Google One." It's "Zoom add-on vs storage we already pay for and don't use." That's not a fair fight.

Does Google Drive auto-delete recordings?

No. Google Drive doesn't auto-delete files. Anything you put in Drive stays until you (or someone with access) explicitly deletes it, and even then Trash retains deleted items for 30 days before final removal. That's the right default for work product.

Zoom Cloud has a few ways recordings disappear that surprise people. When the storage cap fills, Zoom blocks new cloud recordings until space is freed or the plan is upgraded. Account owners can also turn on auto-delete after a configurable number of days — useful for hygiene, painful when you forget the policy is on. License rotations between users in a small team can leave recordings stranded under an admin-only view that the original host can no longer reach.

What about sharing recordings with clients?

Zoom share links can be public-with-passcode, but in many account configurations the host has toggled on "require authentication to view," which locks out clients who don't have a Zoom account. The link UI is built around the meeting it came from, not the long-running asset it produced.

Drive sharing is the same workflow your clients already use for proposals, contracts, and invoices: link or email, viewer or commenter, optional expiry, revoke any time. No new account, no learning curve, no "I can't get into the recording from last week." If you charge for content (recorded courses, group programs, replay-only sessions), Drive's permission model also lets you bind access to a paying email list rather than a static link.

Where do your recordings need to be reachable?

The most underrated benefit. Once a recording lives in Drive, it shows up in Drive search, sits next to the client's other files, and is reachable by every transcript, search, and editing tool that integrates with Drive. Want to find that one session from eight months ago where the client mentioned their co-founder? You can grep Drive across a year of transcripts and find it in a second. Recordings stuck in Zoom Cloud are reachable by Zoom-aware tools and almost nothing else.

If you ever migrate off Zoom — to Meet, to Teams, to a webinar platform, to in-person — the archive stays put.

When Zoom Cloud is the right answer

Three situations where keeping recordings in Zoom Cloud is the right call:

• You need the share link 30 seconds after the meeting ends. Zoom Cloud is faster to a shareable URL than any pipeline that copies the file somewhere else.
• Your compliance posture is built around a vendor-specific BAA or contract that doesn't extend to your Drive setup. Don't break a working compliance story to save $10 a month.
• You're a solo user, very low volume, comfortably under any cap, and you don't share recordings. The convenience of "it's just there" is real, and there's no problem to solve.

If none of those apply, the rest of this post applies.

What changes when you move to Drive

The mechanics of recording don't change. Zoom keeps recording to its cloud, processes the file, and notifies. What changes is that as soon as the recording is ready, it's copied into a Drive folder you control, and from that point on Drive is the source of truth. You can let Zoom's own auto-delete policy remove the Zoom copy on whatever schedule you prefer, knowing Drive has it — the safe order is back up, verify, then delete.

Doing the copy by hand is the most fragile part of this. It's the step that breaks when you have a busy week. The companion how-to post walks through automating it.

How RecordFlow fits

RecordFlow does one thing: the moment Zoom marks a cloud recording ready, RecordFlow copies it (along with the audio file, transcript, and chat log Zoom generates) into a Google Drive folder you choose. Setup is sign in with Zoom, connect Drive, pick a folder — about 60 seconds. Passcode-protected sessions, multi-hour calls, and large files all work the same way. Once you've watched a few backups land safely, you can let Zoom's auto-delete remove its copy on schedule and stop paying for storage you don't need.

What if neither is the right home?

This post frames the choice as Zoom Cloud versus Google Drive because for most people it is. But both are storage with a plan attached — a ceiling you periodically pay a vendor to raise — and if your archive is measured in hundreds of gigabytes rather than tens, there is a third shape worth knowing about: object storage you own, priced per gigabyte all the way up with no tier to graduate to. Amazon S3 Standard is $0.023 per GB per month and cold tiers are a fraction of that. We work the whole thing through — Zoom's own add-on table against S3, R2 and B2, with the catch that matters — in what Zoom recording storage actually costs.

If you just opened a "Zoom storage almost full" email, the fix isn't to pay Zoom more for cloud space. The cheaper, more permanent move is to back up Zoom recordings to Google Drive automatically, using a folder you already own.

Still weighing whether Drive is the right destination at all? The companion post Google Drive vs Zoom Cloud: Where Your Meeting Recordings Should Live makes the case side-by-side. This post is the how.

Zoom cloud recordings stay in your account until your storage quota fills up — or until an admin-set auto-delete policy removes them. The 10 GB included with Zoom Pro and Business plans sounds like a lot, but a coach recording 15 sessions a week still fills it in a few months. Zoom's escape hatch is paid storage add-ons — 30 GB for $10/mo, 200 GB for $40/mo, 1 TB for $100/mo, 5 TB for $500/mo — and that's wasteful spend when your Google Workspace already comes with Drive storage you aren't using. Some organizations also turn on a 30, 60, 90, or 120-day auto-delete for storage hygiene, which tightens the window further. Either way, recordings aren't something you can count on finding a year from now.

The good news: you don't have to copy them manually. Here's the path solo professionals, consultants, and small teams use to put Zoom recordings into Google Drive automatically, within minutes of a meeting ending.

What you need

1. A paid Zoom plan (Pro, Business, Business Plus, or Enterprise) — cloud recording is disabled on free plans.
2. Cloud recording turned on in your Zoom account settings.
3. A Google Drive (personal or shared) with enough free space.
4. An automation service that runs reliably on large recordings and password-protected calls — RecordFlow is built for exactly this workflow.

Step 1 — Verify cloud recording is on

In Zoom Settings → Recording → Cloud recording should be toggled on. Without this, Zoom saves recordings to your local machine instead, and no cloud-based automation can see them.

Step 2 — Connect the automation to Zoom

Install the automation's Zoom App (for RecordFlow, this is a one-click install from the Zoom App Marketplace). Zoom will ask you to authorize read access to your cloud recordings. This uses Zoom's OAuth flow — you're not sharing your password.

Step 3 — Connect Google Drive

The same tool asks you to sign into Google and choose which Drive folder to target. Pick a dedicated folder (/Zoom Recordings/, say) so backups don't mingle with other files.

Step 4 — Record your next meeting to the cloud

When the meeting ends, Zoom processes the recording. For a typical one-hour call this takes a few minutes; multi-hour sessions can take longer. Once Zoom marks the recording ready, the automation kicks in, copies each file to your Drive, and the files appear in the folder you selected.

Expect the video, audio-only file, and any transcript or chat log Zoom generates to land in Drive within minutes of the recording being ready.

What to check when a backup goes missing

How RecordFlow fits

RecordFlow is purpose-built for this one job: back up Zoom recordings to Google Drive. Setup is sign in with Zoom, connect Drive, pick a folder — about 60 seconds. After that, every cloud recording lands in Drive within minutes of Zoom marking it ready, including passcode-protected sessions and multi-hour calls. If a transfer fails it retries automatically, and an hourly safety check sweeps up anything Zoom's notification didn't reach us about. Once you trust the backup, you can let Zoom delete its copy on schedule and stop paying for storage you don't need.