How to Fix Video Call Lag and Poor Quality — A Complete Troubleshooting Guide
Video call freezing, blurry, or cutting out? Here are the actual fixes that work — from bandwidth checks to browser settings — explained step by step.
You're mid-sentence and the video freezes. Or the other person looks like a blurry watercolor painting. Or everything sounds like it's coming through a broken radio. You've been there.
Video call lag and poor quality are frustrating, but most causes are fixable — often in under two minutes. This guide covers why it happens, how to diagnose the actual problem, and what to do about it.
Why Video Calls Get Laggy
Understanding the cause saves you from trying the wrong fix first.
Bandwidth
Video calling uses a lot of data, continuously. A 720p call needs roughly 1.5–2.5 Mbps upload and download. A 1080p call pushes that to 3–5 Mbps each way. If your connection is saturated — other devices streaming, downloading, or uploading in the background — your call gets whatever's left over.
The catch: it's not just your connection. If the other person has a weak connection, you'll see it in their video even if your side is fine.Latency
Latency is the round-trip time for data between you and the other caller. Under 150ms is fine for conversation. Above 300ms and you start talking over each other. Above 500ms and the call feels broken even when the video looks okay.
High latency often comes from routing — your data taking a long, winding path through servers instead of a direct route. WebRTC is designed to minimize this with peer-to-peer connections, but infrastructure can still introduce delays.
Jitter
Jitter is inconsistent latency — packets arriving in uneven bursts rather than steady flow. A video call can handle some latency as long as it's stable. Jitter is harder to recover from because the receiving end can't predict when data will arrive, causing stuttering and audio dropouts.
Home Wi-Fi is a common jitter source. Distance from the router, interference from other devices, and congested channels all contribute.
Quick Fixes to Try First
Before going deeper, try these. They solve the problem more often than you'd expect.
Check Your Internet Connection
Run a speed test at fast.com or speedtest.net before troubleshooting further. You need to know what you're actually working with.
Minimum speeds for video calling
| Quality | Download needed | Upload needed |
|---|---|---|
| Audio only | 0.1 Mbps | 0.1 Mbps |
| 360p video | 0.5 Mbps | 0.5 Mbps |
| 720p video | 1.5 Mbps | 1.5 Mbps |
| 1080p video | 3.0 Mbps | 3.0 Mbps |
| 1080p + screen share | 4.0+ Mbps | 4.0+ Mbps |
If your speed test shows the numbers above but calls still lag, the problem is likely latency or jitter rather than raw bandwidth. Check the ping and jitter figures in the speed test results — ping above 100ms or jitter above 30ms is worth investigating.
Test your connection during the call window
Internet speeds vary by time of day. If your calls happen at 9am or in the evening when your ISP's network is congested, run the speed test at that same time. Numbers that look fine at noon may tell a different story at 8pm.
Browser-Specific Fixes
The browser you use matters, and browser settings can quietly throttle video call performance.
Chrome
Hardware acceleration should be enabled. It offloads video decoding to your GPU, which is much more efficient than software decoding on your CPU.To check: go to chrome://settings/system and make sure "Use graphics acceleration when available" is turned on. After toggling it, restart Chrome completely.
Also try a clean Chrome profile. Extensions like ad blockers, VPN add-ons, and screen capture tools can interfere with WebRTC. Launch Chrome with no extensions (chrome://extensions) and test a call.
Firefox
Firefox handles WebRTC reliably but can sometimes throttle media when it thinks a tab is in the background. Make sure the call tab is your active, focused tab.
In Firefox, check about:config and search for media.navigator.video.enabled — it should be true. While you're there, media.peerconnection.enabled should also be true (this is WebRTC itself).
If you're on Firefox and calls are consistently worse than on Chrome for the same service, try Chrome as a baseline to see if it's a browser-specific issue.
Edge
Edge is Chromium-based, so Chrome fixes mostly apply. Hardware acceleration is at edge://settings/system. Extensions can interfere the same way.
When Camera or Mic Is the Problem
Not all "quality" issues are network related. Sometimes the problem is the hardware itself.
Blurry video that isn't connection-related often comes from a dirty camera lens (wipe it), poor lighting (face a window or add a lamp in front of you), or a camera that's auto-focusing on the wrong thing. Choppy audio that doesn't match the video lag pattern is often a microphone driver issue or a sample rate mismatch. On Windows, right-click the speaker icon, go to Sound settings, find your microphone, and check the sample rate under Advanced. Setting it to 48000Hz (16-bit) works well for most call software. Echo during calls is almost always your microphone picking up speaker output. Use headphones to eliminate it entirely. Camera dropping in and out is often a USB power issue on laptops. Go to Device Manager on Windows, find your camera under Imaging Devices, right-click > Properties > Power Management, and uncheck "Allow the computer to turn off this device to save power."Network-Level Fixes
If you've tried everything above and calls are still poor, the issue may be at the network level.
QoS (Quality of Service) settings
Many home routers support QoS, which lets you prioritize traffic types. Setting video calling or real-time communication as high priority means your call gets bandwidth before a background download does. Log into your router admin panel (usually 192.168.1.1 or 192.168.0.1) and look for QoS settings. The exact location varies by router manufacturer.
VPN impact
VPNs are a common hidden cause of video call lag. A VPN routes your traffic through an additional server, adding latency and sometimes reducing bandwidth. If you're using a VPN, try temporarily disabling it for a test call.
Split tunneling is the cleaner solution — it lets you route video call traffic outside the VPN while keeping other traffic protected. Most desktop VPN clients support this. Add your browser or the video call app to the split tunnel exclusion list.DNS
Slow DNS can add latency to connection setup. Switching to a faster DNS resolver (Cloudflare's 1.1.1.1 or Google's 8.8.8.8) is a free change that occasionally makes a difference. It's in your router's DNS settings or your device's network adapter settings.
Use a Lightweight Browser-Based Tool
Sometimes the platform itself is the overhead. Apps like Teams and Zoom are powerful but they're also heavy — running in the background, consuming memory, and sometimes updating in the middle of your call.
Browser-based video calling with WebRTC tends to be leaner. The browser handles the encoding, and there's no persistent process running outside of the tab.
If you regularly deal with lag on a full-featured platform and your calls are small (two to four people), a lightweight browser-based tool like videocalling.app can be worth comparing. No installation, no background processes — just a browser tab. It won't replace enterprise software for large meetings, but for smaller calls where you want low overhead, it removes several variables from the quality equation.
Summary: Work Through It in Order
Video call quality issues almost always have a cause. The troubleshooting order that works best:
Most people find the fix within the first three steps. The deeper you go, the more specific the issue — but there's always an answer somewhere in that list.