Video Call Settings And Their Data Price Tag

The Short Answer

Your call settings cost more than your call platform. I measured the same recurring team call on Zoom, Google Meet and Microsoft Teams across one week at my agency, and the three platforms landed within 0.2 GB an hour of each other: 1.6, 1.4 and 1.5 GB per hour at the router, cameras on, HD on. The toggles inside each app were worth far more than the gap between the apps.

Turning HD off cut the hour to about 1.0 GB. Turning cameras off for a screen sharing call cut it to about 0.1 GB. When my team adopted one default, cameras off for standups and on for everything else, it returned 16.5 GB a month to every person on the team. If your staff or students are on metered connections, standardize the settings first and argue about platforms later.

The Test: One Call, Three Platforms

The test call was my agency's real internal review meeting: six people, 45 minutes, cameras on, one screen share in the middle while the team walked through designs. It runs every week, which made it a fair test bed.

Across one week I ran it on Zoom on Monday, Google Meet on Wednesday and Microsoft Teams on Friday, same people, same agenda shape, and read the hour off my router's traffic page, the counter that sits closest to what a provider bills.

I have measured calls by counters before, in One Hour On Zoom, Measured Three Ways, and the lesson from that exercise applies here too: these are measured examples from one office connection, and call rates are adaptive estimates everywhere. A struggling line will measure lower and look worse. A clean line measures near the published ceiling.

The conversion behind the right hand column is the one piece of unit math worth memorizing: 1 Mbps held for an hour moves 0.45 GB, so add a platform's published up and down figures together and multiply by 0.45. Zoom publishes 2.6 Mbps up and 1.8 Mbps down for a 720p group call, a ceiling of 1.98 GB an hour; my meeting settled at 1.6 because calls adapt below their ceiling when not every tile is moving.

Microsoft's recommended figures for Teams meetings run higher, 2.5 up and 4.0 down, because the recommendation targets 1080p, and the same page notes Teams can hold HD quality under 1.5 Mbps, which is why my measured 1.5 sits so far below the converted ceiling.

Google publishes its Meet guidance for Workspace admins rather than as one clean per hour figure I could verify, so I am leaving that cell honest: Meet was the lightest in my test by a small margin, and I am not going to invent a published number to complete the pattern. A 0.2 GB spread across three platforms, against savings of 1.5 GB from one toggle, tells you where a metered team's attention belongs.

The Toggle Price List

Here is every switch I priced, in gigabytes per hour, with the data usage calculator rates as the baseline. The group call rate of 1.6 and the one-to-one rate of 0.8 are the calculator's own presets. The toggle figures are my router measurements from the same week, and they will wobble on your connection; the gaps between them will not.

Two rows deserve a footnote. Screen sharing on its own is startlingly cheap: Zoom publishes sharing without video at 50 to 75 kbps, roughly 0.02 to 0.03 GB an hour, so the 0.1 I measured for a cameras off sharing call is mostly the six voices plus overhead. The expensive part of a video call is the grid of faces, not the document.

And audio only, at about 0.05 GB an hour, follows from published audio bitrates near 58 kbps each way; it is the setting that makes a call affordable on almost any bundle on earth, at the price of every visual cue a meeting exists for. Use it as the emergency gear, not the default.

The View You Choose Is Also A Setting

One more variable hides in plain sight: how many faces your screen is showing you. In gallery view your machine pulls a separate stream for every tile on the grid, and the app blends them into the picture you see. In speaker view it pulls one main stream and treats the rest as thumbnails.

On the same Zoom call, same people, same hour, my router read 1.6 GB in gallery view and about 1.3 GB when I switched to speaker view and stayed there. A fifth of the call's price was the layout. Nobody thinks of the layout button as a data setting, because it sits with the view controls instead of the network controls, but the meter does not care which menu a choice lives in.

The effect grows with the size of the meeting. A six person call has five incoming faces to feed; a thirty person class has twenty nine, and while the apps cap how many tiles they send at full quality, a teacher in gallery view on a big class is paying for a wall of faces she mostly is not looking at.

This is also why the published group figures climb with resolution rather than headcount: the platforms assume a grid, and price the grid. If you run large meetings on metered connections, speaker view plus a shared document is the closest thing to a free discount in this entire article. It asks nobody to turn anything off. It only asks the host to stop displaying everyone at once.

The Monthly Bill For One Teammate

Per hour figures stay abstract until they are multiplied by a real month, so here is one teammate's month the old way, with every call at full group HD: daily standups of 30 minutes across 22 working days make 11 hours, the weekly all-hands makes 4 hours, and client one-to-one calls make about 8 hours.

The standups and all-hands at 1.6 GB an hour cost 24 GB; the one-to-one calls at 0.8 cost 6.4. Total: 30.4 GB a month of meetings, before a single file syncs. That is the same order of money as a streaming habit, and it sits inside the wider working month I budgeted in My Work From Home Data Budget, where calls were the line that ambushed the package.

Now price the same month under one changed habit: standups run cameras off with a shared board, at 0.1 GB an hour. Standups fall from 17.6 GB to 1.1. The all-hands keeps its cameras, because faces are the point of that meeting, at 6.4.

Client calls stay as they were, 6.4. Total: 13.9 GB. The difference is 16.5 GB per person per month, and across my six person team the same habit change returned 99 GB of traffic a month, on connections several people on the team pay for by the gigabyte. Nobody's standup got worse. A standup is a list of updates read aloud next to a board; the board is the meeting, and the board costs 0.03 GB an hour to share.

My team spent a month choosing a platform and an afternoon choosing settings. The afternoon was worth fifty times the month.

The Standard My Team Adopted

My team's default now fits in one paragraph: cameras off for standups, cameras on for the all-hands and client calls, HD off unless you are the one presenting. That one paragraph of settings returned 16.5 GB a month to each person on the team. The use case for all of this is any small team, school or coaching setup where the people on the call pay for their own data.

Pick the platform your clients already have, since the platforms are within 0.2 GB of each other. Then write one paragraph of settings defaults, the way my team did, matched to meeting types: what needs faces, what needs only a shared screen, what can be audio. Put the paragraph wherever your team keeps its working agreements, and revisit it when someone's package changes. Standardizing settings is unglamorous and entirely free, and on a metered connection it is worth more than a bigger bundle, because it shrinks every month, not just the month you remember to buy more data.

Translated for a school, the same paragraph reads harsher and saves more. A teacher running four one hour classes a day across 22 school days spends 88 hours a month on group calls. At the full group rate of 1.6 GB an hour, that is 140.8 GB a month of teaching alone, more than many home packages hold in total.

Run those classes as a shared document with student cameras off and the teacher presenting, at the 0.1 GB rate from the price list, and the same 88 hours cost 8.8 GB. No teacher should have to choose between seeing her class and affording her connection, and for discussion lessons she should not. But for the lecture hours, the settings paragraph is the difference between a bundle that survives the term and one that dies in the second week of every month.