Others say you freeze
Your upload path is the first suspect. Pause backups, CCTV and file sync, then check Zoom send statistics.
Fix freezing, robotic audio and screen-share lag by checking upload headroom, Wi-Fi, loaded latency, Zoom Statistics, VPN routing and device load.
Video-call troubleshooting guide
Separate upload saturation, Wi-Fi jitter, router queueing, device load, VPN routing and Zoom service problems using the same practical flow as the Teams call guide.
Start here
Zoom problems usually reveal their cause through direction, connection type and device comparison. Use these checks before changing provider or router.
Your upload path is the first suspect. Pause backups, CCTV and file sync, then check Zoom send statistics.
Wi-Fi signal, interference, roaming or mesh backhaul is adding jitter before traffic reaches the router.
The original laptop, browser, Zoom app, VPN, security software or CPU/GPU load is the likely bottleneck.
Quick reference
This combined symptom-and-action section replaces separate issue, cause and triage blocks.
Your outgoing camera, microphone or screen-share traffic is struggling while incoming media remains usable.
Next: pause uploads and inspect Zoom send packet loss, jitter and latency.Download instability, Wi-Fi retransmissions or packet loss may be affecting the receive path.
Next: compare Ethernet and Wi-Fi, then inspect Zoom receive statistics.Screen capture adds upload and device encoding load. CPU, GPU, browser or upstream pressure may be exposed.
Next: check CPU usage, try the desktop app and pause background uploads.Jitter, packet loss or high latency is delaying or discarding real-time audio packets.
Next: read the Audio tab in Zoom Statistics and run the ping/packet-loss tests.The media path may be detouring through a corporate gateway, proxy or security inspection service.
Next: compare without VPN only where policy allows, then ask IT about media routing.A wider Wi-Fi, upload, router, line or provider problem is more likely than Zoom alone.
Next: use Ethernet and collect loaded-latency and packet-loss evidence.Zoom's own evidence
In the desktop app, open the arrow beside Start/Stop Video, choose Video Settings, then Statistics. You can also open your profile picture, Settings and Statistics from the main app window.
| Zoom statistic | Zoom recommendation | What a poor result suggests |
|---|---|---|
| Latency | 150 ms or less | Higher values create noticeable delay between speech, audio and video. |
| Jitter | 40 ms or less | Variable packet timing can produce robotic audio, freezes and uneven playback. |
| Packet loss | 2% or less | Missing audio, video or screen-share data; even lower loss may be noticeable during a real call. |
| Frame rate | Close to 30 fps where the device and meeting support it. | Low frame rate with normal network figures points more towards camera, CPU, GPU or app load. |
| Send versus receive | Compare Audio, Video and Screen Share tabs separately. | Send-only trouble points to upload; receive-only trouble points to download or the incoming route. |
Interactive check
Enter the latency, jitter and packet-loss values shown while the call is failing. This does not replace the Ethernet and loaded-latency tests; it tells you which route to follow next.
Source: Zoom's current meeting-statistics guidance. Orange means possible quality issues; red means likely quality issues. Open Zoom's official Statistics guide.
Bandwidth reference
Zoom adapts quality to the connection. These current official recommendations help separate a genuinely undersized upload from jitter, loss or queueing.
| Zoom use | Recommended upload | Recommended download | Practical note |
|---|---|---|---|
| 1:1 high-quality video | About 600 kbps | About 600 kbps | Allow extra headroom for other household traffic. |
| 1:1 720p HD | About 1.2 Mbps | About 1.2 Mbps | A line that only just meets the figure can still fail when uploads start. |
| Group 720p HD | About 2.6 Mbps | About 1.8 Mbps | Gallery view and multiple household calls increase demand. |
| Group 1080p HD | About 3.8 Mbps | About 3.0 Mbps | Device capability and account settings can also limit resolution. |
| Audio VoIP | About 60–80 kbps | About 60–80 kbps | Audio uses little bandwidth but is highly sensitive to jitter and loss. |
Do not reserve exactly the minimum. Cloud backup, CCTV, photo sync and another call share the same upstream capacity. Open Zoom's official system and bandwidth requirements.
Test in order
Keep the same room and device while changing one factor at a time.
Record send and receive latency, jitter, packet loss, bandwidth, frame rate, network type, data centre and proxy status.
If Zoom becomes stable when wired, fix room coverage, interference, mesh backhaul or the device wireless adapter.
Stop OneDrive, iCloud, Google Photos, CCTV, console updates and large transfers. Immediate improvement confirms upload contention.
If ping rises sharply during upload or download load, router queueing will damage Zoom whenever the connection is busy.
Compare desktop app and browser, update Zoom, close heavy apps and check CPU, memory and GPU use during screen share.
Test without VPN only where policy permits, compare another call service and check Zoom status before escalating.
Apply the result
Zoom usually improves fastest by protecting upload headroom and reducing jitter.
Do: pause or schedule cloud backup, CCTV and large file uploads. Limit the trigger device where possible.
Retest: Zoom send statistics and the loaded upload phase.
Do: move closer to the router, improve placement, reduce mesh hops or use a wired access point.
Retest: same meeting and room after each change.
Do: use the bufferbloat fix guide to configure effective SQM or QoS and prevent one device filling the line.
Retest: Zoom while a controlled upload runs.
Do: update Zoom and drivers, compare browser and desktop app, close heavy processes and test hardware acceleration.
Retest: another device in the same room.
Do: ask IT whether Zoom media can use approved split tunnelling or a nearer gateway. Do not bypass policy.
Retest: with IT-approved routing changes.
Do: check Zoom status, update the client, compare another meeting and note the connected data centre.
Retest: a second real-time app before blaming broadband.
Work and managed networks
These checks matter when Zoom works on a personal connection but fails on a managed laptop or corporate route.
A corporate VPN can send Zoom media through a distant security gateway, increasing latency and jitter. Test without VPN only where organisational policy permits. Otherwise ask IT whether approved split tunnelling or a nearer gateway is available for Zoom media.
Zoom Statistics shows whether a proxy is in use. Aggressive proxying or inspection can add delay or force a less efficient route. Give IT the timestamp, proxy state, Zoom data centre and send/receive statistics.
Zoom publishes current firewall, destination and port requirements and can fall back to TCP when preferred UDP paths are unavailable. Do not copy an old static firewall list into a managed network. Ask IT to compare the current official requirements with the live policy.
Screen capture, background replacement, HD video and security tools can raise CPU, GPU and memory use. If Zoom network statistics are healthy but frame rate falls, reduce visual effects, close heavy apps and compare the desktop app with the browser.
Escalate with evidence
Strong evidence identifies whether the fault is the home network, broadband path, managed device or Zoom route.
Ethernet result, upload speed, loaded latency, packet loss, router gateway stability, timestamps and whether Teams or another real-time app also failed.
Zoom send/receive statistics, data centre, proxy status, VPN gateway, app version, device CPU/memory and whether the problem disappears outside the managed route.
Best evidence: a screenshot of Zoom Statistics during the fault plus a repeatable Ethernet test. “The call was bad” is difficult to route; send/receive figures show which direction failed.
Focused answers
These answers match the FAQ structured data in the page head.
A normal speed test can show enough throughput while Zoom still suffers from upload saturation, high jitter, packet loss, Wi-Fi retransmissions or loaded latency. Live calls need consistency, not just peak download speed.
That usually points to your outgoing path. Your device may receive the meeting normally but struggle to send camera, microphone or screen-share packets because upload capacity, Wi-Fi or router queues are under pressure.
Zoom currently recommends latency of 150 ms or less, jitter of 40 ms or less and packet loss of 2 percent or less. Orange or red indicators in Zoom Statistics show that quality may be affected.
Ethernet removes most wireless interference, weak-signal retransmissions and mesh roaming. It is the best comparison test when Zoom audio, video or screen sharing becomes unstable.
Yes. A VPN, proxy, SSL inspection or blocked UDP media path can add latency, jitter or fallback routing. Test without VPN only where policy allows and ask the IT team to verify the current official Zoom network requirements.
The requirement depends on call type and resolution. Zoom currently lists about 1.2 Mbps up and down for 720p one-to-one HD video and higher rates for 720p or 1080p group video. Stable upload headroom is more important than barely meeting the minimum.