How much upload speed do video calls need? Zoom, Teams and Meet figures

Published figures for one participant

These are vendor figures read on 13 October 2026. They are the platforms' own planning numbers, not measurements by this publication. Each vendor defines its tiers differently, so compare within a column rather than across rows.

What the numbers mean, and what they do not

Zoom's figures are listed as recommended bandwidth for meeting and webinar panelists. Zoom separates one-to-one from group calls and gives gallery-view receive rates. [1]

Microsoft gives three tiers per endpoint: minimum, recommended and best performance. It says Teams can deliver HD video in under 1.5 Mbps. Usage rises when more bandwidth is available, up to 1080p video and up to 30 fps for video and content. When bandwidth is short, Teams prioritizes audio over video. One user joining on both a laptop and a phone counts as two endpoints. [2]

Google's network guidance gives one set of figures for small organizations or individuals and a lower average for large organizations planning many users. The 720p and 1080p figures above come from the small-organization table. Google also says a still screen share stops using extra bandwidth once it loads. [3]

None of the three pages sets a household latency or jitter target. Microsoft links choppy or robotic audio to jitter and packet loss, and recommends prioritizing media over Wi-Fi and keeping Teams traffic out of a VPN tunnel where possible. Bandwidth figures are necessary, but they do not explain every bad call. [2]

Size a household by overlap, not by headcount

List the calls that actually overlap on a busy day: who, which platform, camera on or off, and whether they present. Use the platform's figure for each, then add up upload and download separately. A person who always shares slides on Zoom needs less upload than one who runs 1080p camera video all day.

Next, add the uploads that run in the background. Cloud photo backup, laptop backup, large file sync and security cameras that upload to a cloud service all compete with call video. None of the vendors above publish a figure for those; you will need your own device settings or provider documentation. Where you cannot pin a number down, schedule the job outside working hours instead of guessing.

Then compare the total with your plan's upload rate, and check your real throughput at a quiet time. If the overlap total sits close to your measured upload, upgrading the plan or moving backups off-hours is the honest fix. If it is far below and calls still fail, look at loaded latency and Wi-Fi.

Worked example: a fictional three-person household

Fictional household: Jun uses Teams for group meetings most of the morning. Sara presents on Zoom at 1080p twice a day. Their teenager joins a Google Meet class at 720p. The three overlap from 10:00 to 11:00.

Using the vendor figures: Teams recommended for meetings is 2.5 Mbps up and 4.0 Mbps down. Zoom group 1080p is 3.8 Mbps up and 3.0 Mbps down. Meet 720p is up to 1.7 Mbps each way. That adds up to about 8.0 Mbps up and 8.7 Mbps down for the overlapping hour. [1][2][3]

Their plan lists 20 Mbps up. On paper that leaves room. But a laptop backup that runs at 10:00 could take a large share of the remaining upload. The household's own planning rule, not a vendor figure, is to keep scheduled backups out of the 9:00 to 17:00 window and to check loaded latency once with the backup running. If calls still break up during that hour, the next step is the bufferbloat guide, not a faster plan. These numbers are a planning exercise, not a measurement.

Measure upload the way calls experience it

A speed test gives you a throughput number. Cloudflare's speed test also records idle latency as soon as the page loads, then sends small requests during the download and upload transfers to measure loaded latency. It also reports jitter and packet loss. Run it from the computer used for calls, once over Wi-Fi and once wired if you can. Run it again while the household's normal uploads are active. [4]

If wired results look fine and Wi-Fi results do not, the bottleneck is inside the home. If both look fine at a quiet time but loaded latency jumps when someone uploads, the line is queueing and shaping may help. Record the time, the device and the connection each time. A single test is not evidence of a pattern.

Pitfalls and who can skip this exercise

Keep the overlap table with your router notes. When a new person starts working from home, or a camera starts uploading to the cloud, update the table before deciding anything else.

• Skip the arithmetic if calls are already clear during your busiest overlap; the published figures are planning guides, not targets to chase.
• Do not compare download speed with call requirements and ignore upload.
• Do not mix vendor tiers: Teams' minimum is far below its recommended figure, and Meet's large-organization average is lower than its small-organization HD figure. [2][3]
• Count a second device joining the same meeting as another endpoint. [2]
• Check whether a work VPN carries call traffic; Microsoft recommends a split-tunnel path for Teams. [2]
• Do not buy a faster plan before checking Wi-Fi and loaded latency.

Sources & verification

Product details and prices can change. Check the linked provider before buying.

1. Zoom: system requirements for Windows, macOS and Linux (bandwidth) Accessed 13 Oct 2026
2. Microsoft Learn: Prepare your organization's network for Teams Accessed 13 Oct 2026
3. Google Workspace: Prepare your network for Meet meetings and live streams Accessed 13 Oct 2026
4. Cloudflare blog: How does Cloudflare's speed test really work? Accessed 13 Oct 2026