One person on video calls needs about 4 Mbps up and 4 Mbps down. Microsoft Teams recommends 2.5 Mbps up and 4 Mbps down for meetings, and a 1080p Zoom group call uses 3.8 up and 3.0 down. The catch is that upload, steady latency and everyone else in the house matter more than the headline download speed. As a rule of thumb, a home with one remote worker is comfortable on a plan with 100 Mbps down and at least 10–20 Mbps up.
What the meeting apps actually use
These are the official per-person figures for a video meeting:
| App | Upload | Download | Source |
|---|---|---|---|
| Zoom, group call, 1080p | 3.8 Mbps | 3.0 Mbps | Zoom system requirements |
| Zoom, group call, 720p | 2.6 Mbps | 1.8 Mbps | Zoom |
| Teams meeting, recommended | 2.5 Mbps | 4.0 Mbps | Microsoft Teams network guide |
| Teams, best performance | 4.0 Mbps | 4.0 Mbps | Microsoft |
| Google Meet, 1080p | up to 3.6 Mbps | up to 3.6 Mbps | Google Workspace network guide |
Every app scales down when bandwidth is short, so a slower line usually gets you a softer picture rather than a dropped call. Teams, for example, protects audio before video when bandwidth runs out. For app-by-app detail, see Zoom's speed requirements and Teams' speed requirements.
These numbers are small next to most plans. Calls go wrong because the upload is shared with something else, or because the connection is unstable. The download figure is rarely the problem.
Upload is the number to check
Most cable and DSL plans give you only a small fraction of the download as upload, so a plan that looks fast can still have a modest upload. Even the FCC's broadband benchmark is just 20 Mbps up, against 100 Mbps down. That's plenty for one call, but it fills quickly when you add:
- Your camera on a call.
- Cloud sync uploading files you just saved: OneDrive, Google Drive, Dropbox.
- Someone else in the house on a call, or a phone backing up photos.
- Screen sharing, and recording to the cloud.
A full upload doesn't just slow uploads. It raises ping for everything else, which is when your voice starts to break up. If your test shows a low upload, why upload speed is slow explains how to tell a plan limit from a fixable problem.
Large files and cloud sync
File transfers are where upload speed turns into waiting time. The math is simple: multiply the size in megabytes by 8 to get megabits, then divide by your upload speed.
- A 2 GB video export at 10 Mbps up: 2,000 MB × 8 = 16,000 megabits ÷ 10 = 1,600 seconds, about 27 minutes.
- The same file at 40 Mbps up: 16,000 ÷ 40 = 400 seconds, about 7 minutes.
These are best-case figures, since real transfers carry some overhead. If your job involves video, design files or large datasets, upload speed is worth paying for. If it's mostly email and documents, it barely matters, except that sync shouldn't run during calls. Most sync apps let you pause them or cap their upload rate.
VPNs and remote desktops
A work VPN encrypts everything and routes it through your company's network, which usually costs some speed and adds ping. That matters most for calls. Microsoft recommends a split-tunnel VPN so Teams traffic skips the VPN. Its reasons are that VPNs aren't designed for real-time media and can add latency and jitter. Google's guidance for Meet is to avoid the VPN for meeting traffic altogether.
You can't change your company's VPN setup, but you can ask IT whether meeting traffic is split-tunneled. Whether a VPN slows your internet covers how to measure the difference yourself.
Remote desktop tools usually need modest bandwidth but react badly to high or jumpy ping. If the remote screen feels sticky, look at ping and jitter, not Mbps.
Sizing it for the whole household
Add up what might happen at the same moment on a busy weekday. Here's an example household, with the streaming figure taken from the 4K streaming requirements:
| Activity | Upload | Download |
|---|---|---|
| Two people on video calls (about 4 each) | 8 Mbps | 8 Mbps |
| One 4K TV stream | — | 25 Mbps |
| Cloud sync and phones in the background | a few Mbps | a few Mbps |
| Rough total (estimate) | about 10–12 Mbps | about 35–40 Mbps |
On paper, a 50/10 plan covers that. In practice, leave headroom, because a single game download or photo backup can take everything that's spare. That's why 100 Mbps down and 10–20 Mbps up is a sensible floor for a home with remote workers, and why more upload helps more than more download once you're past that.
Stable beats fast
A connection that holds a steady 50 Mbps is better for work than one that bursts to 500 and stalls. To keep calls steady:
- Use Ethernet at your desk if you can. Wi-Fi adds jitter, especially through walls.
- Put your desk on 5 GHz if you stay on Wi-Fi, and keep the router in the same room or use a mesh node.
- Schedule big transfers like backups, game updates and large syncs for outside working hours.
Before an important call, run a speed test from your desk. It shows download, upload, idle ping and jitter. It doesn't measure ping under load or packet loss, so if calls still break up while your numbers look fine, test with a real call while someone else uploads. That's when those problems show.
Common questions
Is mobile hotspot internet good enough to work from home?
For calls and email it often is, if the signal is strong and your data allowance is large. Mobile speeds and latency vary much more through the day than a fixed line does, so run a speed test at the times you usually have meetings before you rely on it.
Does my employer's VPN need extra speed?
It adds encryption overhead and often a longer route, so expect somewhat lower speeds and higher ping while it's on. The bigger risk is call quality, which is why Microsoft and Google both recommend keeping meeting traffic off the VPN where possible.