How Big Is A One Hour Zoom Or Teams Recording

The Warning On Tuesday

The warning arrived as a plain storage email on a Tuesday morning: the account's cloud recording pool was nearly full. I record a client's weekly training session, one hour every Thursday, and I had assumed the recordings were a minor line in the storage budget. The pilot week had produced a tidy file, a little over 700 MB. What I had not noticed was the settings change the client asked for in week two. They wanted to see the whole team's faces during the discussion part, so I switched the recording to gallery view and turned on the HD option, and every file after that landed at nearly twice the pilot's size. By week five the series had taken about 6.4 GB of a pooled 10 GB allowance that two other people also record into.

Here is the short answer, before the working. A one hour meeting recording has no fixed size. It lands anywhere from about 58 MB for audio only to about 2.3 GB for gallery view with a shared screen, because each recording mode writes a different bitrate. The mode is the decision. Once I priced each mode per hour, the monthly bill stopped being a surprise and became a choice I make before the call starts.

One Hour, Five Recording Modes

Meeting recorders do not publish a bitrate on the box, but the files obey the same rule as every other video: total bitrate times seconds, divided by eight. I measured the modes from my own recordings and matched each one to the bitrate its files actually carry. The audio track is counted at 128 kbps in each row, a typical voice rate for meeting audio.

My measurements sit inside the ranges Zoom's own community reports for group meetings, 810 MB to 2.4 GB per hour, which is a useful sanity check: if your hour lands far outside that band, a setting deserves a look. Every figure in the table came out of the video file size calculator, fed with the mode's bitrate and a one hour duration. The use case behind this table is the one I now plan for every term: a trainer, teacher or team lead archiving a weekly session needs the per-hour figure for the mode they actually record, multiplied by the number of sessions, before the term starts. Four gallery view hours a month come to 5,630 MB, about 5.6 GB. Four speaker view hours come to 2,930 MB. Same meetings, same trainer, half the storage.

Why Gallery View Costs So Much More

Speaker view writes one main video tile at a time, the person talking, with the rest of the call carried as audio and tiny thumbnails. Gallery view writes a grid of live tiles at once, and a grid holds far more changing pixels per second, so the recorder feeds it a higher bitrate to keep faces readable. Add an HD setting and the rate climbs again. Add a shared screen beside the grid and the recorder is writing two video streams into one file.

Nobody chose the expensive setting. It was simply the default nobody had ever questioned.

Teams follows the same shape, with a different filing cabinet: recordings land in OneDrive or SharePoint rather than Zoom's cloud, but a gallery hour still outweighs a speaker hour by the same logic. The audio track, for contrast, barely moves the total. Even at the full 128 kbps counted above, one hour of sound weighs 57.6 MB, less than 8 percent of a speaker view file. I work through exactly how little audio adds to any video in The Audio Track Article, because my first guess in that Tuesday panic was to blame the sound, and the sound was innocent.

Price Your Own Month In Four Steps

Step 1: record one real session and read its size. Open the file's properties and note the megabytes for one full hour in the mode you use. That single measurement beats any table, including mine, because it carries your settings.

Step 2: find the bitrate behind it. Divide the size in megabytes by 450. An hour holds 3,600 seconds, and bitrate times 3,600 divided by eight is bitrate times 450, so the division hands you the total bitrate in Mbps. My gallery files divide out to about 3.13 Mbps.

Step 3: price the month, not the meeting. Multiply the per-hour size by the sessions you record in a month, then compare it with your pool. Zoom's support pages list 10 GB of cloud recording storage per licensed user on Pro and Business plans, pooled across the account. The same pooled-quota thinking applies to any shared allowance, and I plan internet data the same way with the data usage calculator.

Step 4: pick the mode on purpose. If the month does not fit, the fix is a recording decision, not a storage purchase: speaker view for teaching sessions, gallery only for the meetings where faces are the point.

The same four steps scale past one weekly call. A school recording twelve hours of classes a week in speaker view fills about 8,791 MB a week, manageable inside one pooled allowance for a while. The same timetable in gallery view fills about 16.9 GB a week, which exhausts a 10 GB per-user pool before the second Friday and turns recording off mid-lesson for whoever shares the account. Nobody at that school needs more storage. They need the mode decided at the timetable level, once, instead of rediscovered at every warning email. A busier recording calendar runs the same four steps at a larger scale, priced out in How Much Storage A Wedding Videographer Needs For One Season.

How I Record Now

The training series now records in speaker view by default, because the client replays it for the slides and the trainer's voice, not for a grid of nodding tiles. Gallery view comes on for the monthly review meeting only, and I budget that one hour at 1,407.6 MB when I plan the term. I also download each recording at the end of the month and keep a local archive copy, so the cloud pool holds only the current term.

• Default recording mode: speaker view, HD off, at about 733 MB an hour
• Gallery view: review meetings only, budgeted at about 1.41 GB an hour
• Audio only copy: kept for search and notes, at 57.6 MB an hour
• Archive habit: download and clear the cloud pool monthly

The habit underneath all of this is the one the Tuesday warning taught me: a recording mode is a bitrate, a bitrate is a size, and a size times a schedule is a storage bill I can read before it arrives. The calculator on this page does the multiplication in seconds. The only input it really needs from you is the honest one: which mode will the recording actually run in?