Zoom Storage Management for Admins: Stop the Account-Wide Storage Crisis

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 at all. 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.

How RecordFlow fits

RecordFlow's admin-managed app does the one thing Zoom's own tools don't: it moves recordings out to Drive automatically, the moment each one finishes, so nothing needs a manual export. Install it once as the account admin and connect a Google Drive folder you control — 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 Drive — we never store the bytes on our infrastructure in between.

Archiving on its own doesn't shrink Zoom's storage pool — the copy in Drive 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 Drive 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 your Drive, 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.