Zoom bandwidth requirements table
Zoom publishes specific bandwidth figures for each call type. These are the upstream requirements from Zoom's own documentation:
| Call Type | Download | Upload | Notes |
|---|---|---|---|
| Audio only | 60 kbps | 60–80 kbps | Works on virtually any connection |
| 1:1 video call, 720p | 1.2 Mbps | 1.2 Mbps | Per-direction; requires both |
| 1:1 video call, 1080p | 1.8 Mbps | 1.8 Mbps | Requires HD enabled in Zoom settings |
| Group video, 720p | 1.5 Mbps | 1.5 Mbps | Per active video stream received |
| Group video, 1080p | 2.5 Mbps | 2.5 Mbps | Multiply by streams; 5 people = 12.5 Mbps down |
| Screen sharing only (no video) | 50–75 kbps | 50–75 kbps | Rises sharply with motion or video content |
| Screen sharing + video | adds 50 kbps–1 Mbps | adds 50 kbps–1 Mbps | Depends on screen content complexity |
Zoom's adaptive bitrate algorithm
Zoom continuously monitors network quality during calls using RTCP (Real-time Transport Control Protocol) feedback. When the algorithm detects packet loss above ~1% or RTT spikes, it reduces video bitrate in steps: first frame rate drops (30 fps → 15 fps → 7.5 fps), then resolution drops (1080p → 720p → 360p), and finally video is suspended entirely while audio continues. This means Zoom can maintain a functional audio call even on a severely degraded connection — but your video will look increasingly blurry or freeze-frame as conditions worsen. Robotic or choppy audio typically indicates packet loss above 5% or jitter above 30 ms, which is beyond what Zoom's buffering can compensate for.
Zoom in-meeting connection quality indicators
During any Zoom meeting you can monitor your live connection quality. Click the signal bars icon (or shield icon depending on version) in the top-left corner of the meeting window to open the Statistics panel. It shows real-time figures for: latency (round-trip time to Zoom's server), packet loss percentage (upstream and downstream separately), jitter, and current bitrate for audio and video. Green indicates good; yellow indicates marginal; red indicates poor. If you see packet loss above 2% or latency above 150 ms in the Statistics panel during a problem call, those numbers confirm the network is the issue rather than Zoom's servers or your device.
Zoom network test tool
Zoom provides a pre-meeting network test at zoom.us/test — it opens a Zoom test session that checks your connection to Zoom's infrastructure specifically, rather than a generic speed test server. It verifies that UDP traffic can reach Zoom's media servers (some firewalls block UDP), measures round-trip latency to Zoom's nearest relay, and checks microphone and camera functionality. Run this test from the same device and network you use for calls, at the time of day you normally have meetings. A failed UDP test explains why Zoom falls back to TCP, which adds latency and reduces quality.
Zoom QoS and DSCP marking
Zoom marks outgoing media packets with DSCP values to enable quality-of-service prioritization on enterprise networks. Audio packets use DSCP 46 (EF — Expedited Forwarding), the highest-priority class, ensuring audio packets jump ahead of bulk traffic in router queues. Video packets use DSCP 34 (AF41 — Assured Forwarding class 4). On a home router without QoS configured, these markings are ignored. On a corporate network or a home router with DSCP-aware QoS rules (such as OpenWrt with cake-qos), Zoom's audio traffic is automatically prioritized over file downloads, cloud sync, and other background traffic — reducing call degradation during household congestion.
Zoom over VPN
Routing Zoom through a full-tunnel VPN adds the VPN server as an additional hop for all media packets, increasing RTT and introducing jitter from the VPN tunnel overhead. Zoom recommends split tunneling: configure the VPN to send Zoom media traffic directly to the internet while routing other corporate traffic through the tunnel. Zoom publishes its IP ranges and port requirements (UDP 8801–8802, TCP 443) that should be excluded from VPN tunneling. For organizations with compliance requirements that mandate all traffic through the VPN, Zoom Phone (the VoIP service) can be configured to route through the VPN while Zoom Meetings media bypasses it — or dedicated hardware phones can handle compliant audio while the computer handles video.
Reducing bandwidth on poor connections
When your upload or download is constrained, Zoom provides several settings that reduce bandwidth consumption with minimal impact on call usefulness:
- Disable HD video: In Zoom Settings → Video, uncheck "HD." This caps your outgoing video at 360p, cutting upload from ~1.8 Mbps to ~0.6 Mbps while keeping audio and screen sharing fully functional.
- Stop video entirely: Press Alt+V (or click Stop Video) during a call. Audio uses only 60–80 kbps; removing video is the single largest bandwidth reduction available.
- Disable virtual background: Virtual backgrounds require GPU processing and add encoding complexity. On slower hardware or poor networks, disabling them reduces CPU load and can stabilize video quality.
- Turn off "Original Sound": Zoom's Original Sound mode disables audio compression for music quality — it uses significantly more upload than the default voice-optimized mode. Disable it for standard calls.
Zoom Phone vs Zoom Meetings bandwidth
Zoom Phone (the enterprise VoIP service) uses substantially less bandwidth than Zoom Meetings video calls. A Zoom Phone audio call uses 60–100 kbps — comparable to any VoIP service. Zoom Meetings adds video on top of audio, multiplying bandwidth by 15–25x for HD calls. Organizations replacing traditional desk phones with Zoom Phone for audio calls and reserving Zoom Meetings for video conferencing can significantly reduce bandwidth requirements per user, which matters when planning office network capacity for large call centers or open-plan offices.
Zoom Performance Table
| Meeting Situation | Suggested Download | Suggested Upload | Latency Goal |
|---|---|---|---|
| Single-user video call | 5–10 Mbps | 3–5 Mbps | <50 ms |
| HD group meetings | 10–25 Mbps | 5–10 Mbps | <40 ms |
| Meeting + background traffic | 25+ Mbps | 10+ Mbps | <35 ms |
| Business-critical calls | 50+ Mbps | 15+ Mbps | <30 ms |
Frequently Asked Questions
What internet speed is good for Zoom meetings?
For HD reliability, target around 10 Mbps download and 5 Mbps upload per active Zoom user, then validate latency and loss under load.
Why does Zoom freeze even when speed test results look good?
Because call quality depends on latency stability and packet loss. High bandwidth does not guarantee stable real-time performance.
Is upload speed more important than download for Zoom?
Upload is often the hidden bottleneck in two-way video calls, especially when backups or sync jobs run in parallel.
How can I improve Zoom call quality fast?
Use Ethernet or strong 5 GHz, pause background uploads, and retest metrics during your typical meeting schedule.
Should I upgrade my internet plan for Zoom issues?
Only after local Wi-Fi and device causes are ruled out with repeatable tests.