Updated May 2026

Internet Speed for Video Calls: Zoom, Teams and Meet

Video calls are uniquely demanding. They need both download and upload at the same time, in real time. Unlike video streaming — which only needs steady download — a video call sends your camera feed out while receiving everyone else's feeds. It needs minimal delay and minimal variation in that delay. That's why video calls are so sensitive to connection quality.

Here's a real example. A 50 Mbps plan with 150ms ping and 40ms jitter will produce broken audio and frozen video on Zoom. A 25 Mbps plan with 20ms ping and 5ms jitter will look and sound perfect. Speed matters far less than stability. Your connection being steady is more important than it being fast.

Bandwidth Requirements by Platform

Platform Download (HD 1080p) Upload (HD 1080p) Group call (5+ people) Screen sharing (added)
Zoom 2.5 Mbps 3.0 Mbps 4.0 Mbps down/up +1.0–2.5 Mbps upload
Microsoft Teams 1.5 Mbps 1.5 Mbps 4.0–5.0 Mbps for large meetings +1.0–4.0 Mbps upload
Google Meet 2.6 Mbps 3.2 Mbps 3.5 Mbps for multi-person +0.5–1.5 Mbps upload
FaceTime 1.5 Mbps 1.5 Mbps 8.0+ Mbps for Group FaceTime Not supported
Discord (video) 1.0 Mbps 1.0 Mbps Varies (server-limited) +0.5–2.0 Mbps upload
Webex 2.0 Mbps 2.0 Mbps 4.0 Mbps for panels +1.0–4.0 Mbps upload

Why Upload Is the Critical Variable

Most home internet plans give you way more download than upload. A plan that says "100 Mbps / 10 Mbps" has 10 times the download capacity. For streaming, browsing, and downloads, that's fine. For video calls, it's your main failure point.

Your camera feed — the video of you — travels outbound. If your upload is too low or gets overloaded, everyone else on the call sees you as blurry, pixelated, or frozen. Your own view of them might look fine. The upload channel is what carries your presence on the call.

As a practical minimum, keep 3 Mbps of upload free for your video call, on top of everything else uploading. Cloud sync apps like Dropbox, iCloud, and Google Drive are the most common silent upload consumers. They compete with your call without any visible warning.

How Ping and Jitter Break Calls

Bandwidth is necessary but not enough for good call quality. Even with 100 Mbps upload available, high latency (delay) and high jitter cause the audio and video problems that make remote meetings miserable.

Metric Acceptable Problem threshold What happens when exceeded
Ping (latency) <100ms >150ms Unnatural pauses in conversation; people keep talking over each other
Jitter <10ms >30ms Robotic audio, garbled words, choppy video as packets arrive bunched or out of order
Packet loss 0% >1% Missing audio, video freezes, call drops at higher rates

Of the three, jitter is the one most people overlook. A connection with 60ms ping but 5ms jitter will sound clean. A connection with 30ms ping but 45ms jitter will sound choppy and robotic. That's because jitter disrupts the smoothing buffer that call platforms use to iron out uneven packet arrival. When jitter overwhelms that buffer, your voice sounds like a robot.

Video Codecs and Bandwidth

Video call platforms compress your camera feed using something called a codec. The codec affects how much upload bandwidth each quality level needs:

  • H.264: The most widely supported baseline codec. Needs the most bandwidth for a given quality level. Used on older systems and as a fallback.
  • VP8/VP9: Google's codecs used in Meet and other WebRTC apps. VP9 is about 50% more efficient than H.264 at the same quality. Used when both sides support it.
  • AV1: The newest codec. Even more efficient than VP9. Available in recent Zoom and Teams versions. Cuts bandwidth needs by up to 30% compared to VP9.

You don't choose your codec directly — it depends on both devices and the platform's server. But newer software and modern hardware tend to use more efficient codecs. Your bandwidth requirements may improve over time just by keeping your apps updated.

Virtual Backgrounds and Their Overhead

Virtual backgrounds and background blur require your computer to process video in real time before uploading it. This adds CPU load but doesn't directly increase your network usage. However, on older hardware, the CPU load from background processing can slow down video encoding. Your camera feed drops frames — and that looks like poor call quality, even though your network is fine.

If you use a virtual background and your video looks choppy to others on an otherwise good connection, try turning it off. Background blur uses significantly more CPU than a simple image background on most systems.

Screen Sharing: The Hidden Upload Consumer

Screen sharing adds a second video stream to your upload — your screen content alongside your camera. A screen with lots of movement (playing a video, scrolling through code) needs 2–4 Mbps extra upload. A mostly still screen (a document, a presentation) needs closer to 0.5–1.0 Mbps extra.

If you share your screen in important meetings, make sure you have at least 5–6 Mbps of upload headroom. Not just the 1.5–3 Mbps minimum for camera-only calls.

Diagnosing Video Call Problems

You look blurry to others but they look fine to you

This is an upload problem. Run a speed test and check your upload. You need at least 1.5 Mbps for basic HD. You need 3+ Mbps for consistent quality. Check for cloud sync apps competing for upload. Switch to Ethernet if you're on Wi-Fi — wireless adds upload instability and jitter.

Audio cuts out or sounds robotic

This is almost always a jitter or packet loss issue. Run a speed test and look at your jitter value. Above 30ms, audio quality suffers. Above 50ms, you'll sound like a robot because the platform's smoothing buffer can't keep up. Ethernet almost always fixes Wi-Fi-induced jitter.

Everyone freezes and then jumps forward

This is packet loss followed by a buffer flush. The platform held on as long as it could, then skipped ahead to catch up. Check your connection for packet loss — even 0.5% over a one-minute call is hundreds of dropped packets and produces exactly this symptom.

Your call works fine for a few minutes then degrades

This suggests bufferbloat triggered by the call itself. As your buffers fill, latency rises and jitter increases. The call starts clean because buffers are empty, then degrades as they fill. Test for bufferbloat using DSL Reports or Waveform's bufferbloat test.

Call quality degrades after 7 PM

This is peak hour congestion on your ISP's network. Evening calls are harder than morning calls for this reason. If important calls consistently fail in the evening, schedule them earlier or consider switching to fiber, which handles congestion better.

Call Quality Checklist

  1. Connect via Ethernet rather than Wi-Fi for important calls
  2. Close cloud sync apps (Dropbox, iCloud, Google Drive) before the call starts
  3. Ask others in your home to pause large downloads and 4K streaming during calls
  4. Use the 5 GHz Wi-Fi band if Ethernet isn't possible (less interference than 2.4 GHz)
  5. Enable QoS on your router to prioritize video call traffic if you share a connection
  6. Restart your router if call quality has been gradually getting worse over days
  7. Test your connection before important calls — check upload, jitter, and ping
  8. Keep your video call app updated — newer versions use more efficient codecs

How Much Upload Speed Do You Actually Need?

Scenario Recommended Upload
One-on-one calls (HD video) 3 Mbps minimum
Group calls with 5+ participants (HD) 5 Mbps recommended
Group call + screen sharing 8 Mbps recommended
Multiple people on calls at home at once 5 Mbps per caller
Live streaming via Zoom/YouTube at the same time 8–15 Mbps for 1080p30
Related: Working from home internet guide — covers how to balance video call bandwidth with VPN overhead, cloud apps, and a shared household connection.