How to fix webcam lag
Webcam lag — where your video feed arrives delayed, choppy, or stuttering to everyone on the call — almost never means the camera itself is broken. In the vast majority of reported cases, the root cause is somewhere between the camera's USB connector and your encoder settings. The most important thing to understand up front: your webcam is competing for resources it needs to share, and knowing which resource is the bottleneck tells you exactly which fix to apply.
Why webcam lag happens: the mechanism
Your webcam captures raw or compressed video, hands it to USB, which passes it to a host controller, which queues it for your CPU or GPU to encode and deliver to the call application. There are at least four places that pipeline can choke:
1. USB bandwidth congestion USB 2.0 maxes out at 480 Mbps — but that's shared across every device on the same controller. A webcam streaming uncompressed 1080p at 30fps needs roughly 1.5 Gbps of raw throughput, which is why cameras compress internally (MJPEG or H.264). Even so, plug in a USB hub with a keyboard, mouse, audio interface, and webcam on a single USB 2.0 controller, and you're asking for frame drops. USB 3.x controllers have more headroom, but many laptops still route multiple USB-A ports through a single controller.
2. CPU encoding overhead If your webcam outputs MJPEG or YUY2 and the driver or call app is re-encoding on the fly, a loaded CPU will drop frames before it drops anything else. This gets worse when you're screen-sharing simultaneously — the encoder is now handling two streams.
3. Driver staleness or conflict Webcam drivers interact closely with the DirectShow or Video4Linux (V4L2) stack. A driver that hasn't been updated can present the wrong capabilities to the OS, causing the application to request a format the camera can't actually deliver cleanly, or to fall back to an uncompressed format it wasn't designed for at high resolutions.
4. Application-level constraints Zoom, Teams, Google Meet, and OBS each have their own video pipeline. Some cap inbound resolution by default, others apply software processing (virtual backgrounds, noise suppression) that multiplies CPU load. A camera that performs fine in one app can appear to lag heavily in another because of how the app requests and processes the feed.
The fix sequence — work through it in order
1. Move the webcam to a direct USB port
This fixes USB congestion — the most common culprit across owner reports — and costs you nothing.
Unplug the webcam from any hub and connect it directly to a port on your machine. On a laptop, use a port on the chassis rather than one on a connected dock, if possible. On a desktop, prefer a rear panel port (these connect directly to the motherboard controller) over front panel ports, which often share bandwidth.
If you're running Windows, open Device Manager → Universal Serial Bus controllers and look at how many host controllers are listed. Devices grouped under the same controller share its bandwidth. Your goal is to give the webcam a controller with nothing else on it, or at minimum, nothing else that's data-heavy.
On macOS, System Information → USB shows you the full tree — which devices are hanging off which host controller.
2. Update or reinstall the driver
Don't trust auto-update. Go to the manufacturer's support page for your exact model and download the latest driver directly. Uninstall the existing driver first (Windows: Device Manager → right-click → Uninstall device → check "Delete the driver software"), reboot, then install the fresh download.
On Windows, also check Windows Update → Advanced options → Optional updates — webcam driver updates sometimes land there rather than through manufacturer sites.
On Linux, V4L2 driver issues are common with branded webcams that ship Windows-only firmware. The v4l2-ctl --list-formats-ext command will show you what formats the OS is actually seeing from the camera — if it's missing MJPEG and only showing YUYV, you're pushing uncompressed data across USB, which will absolutely lag at 1080p.
3. Lower the resolution or frame rate in the application
This is the fastest triage step if you're mid-call and need an immediate fix. Most webcams that advertise "1080p 30fps" do so only under ideal conditions — direct USB 3.0, fresh driver, no competing USB devices, light CPU load. Drop to 720p 30fps and the bandwidth and encoding demands fall dramatically.
Where to find it:
- Zoom: Settings → Video → Camera → HD (toggle off)
- Teams: Settings → Devices → Camera — Teams auto-negotiates; closing background effects processing helps more than the resolution toggle
- OBS: Sources → Video Capture Device → Configure Video → Resolution and FPS dropdowns
- Google Meet: Three-dot menu → Settings → Video → Send resolution
If reducing resolution eliminates the lag, work back up one step at a time to find the actual ceiling your setup can sustain.
4. Kill competing USB bandwidth hogs
Owner reports consistently flag this: a USB audio interface, an external SSD, or a USB dock doing DisplayLink all sitting on the same controller as the webcam. DisplayLink in particular — the technology used by many USB-C docks to drive external monitors — is notorious for consuming large chunks of USB bandwidth.
Disconnect devices one at a time, check if lag improves after each removal. If unplugging a specific device fixes the lag, you've found the conflict. The solution is either a separate USB controller (PCIe USB expansion cards are inexpensive for desktops) or reorganizing devices across available ports.
5. Check for thermal throttling
Less common but documented: laptops under sustained load throttle CPU performance, which reduces available encoding headroom. If your lag gets worse the longer a call runs — rather than being present from the start — thermal throttling is worth checking. On Windows, Task Manager → Performance → CPU will show whether clock speeds are dropping under load. Improving ventilation, cleaning dust from vents, or using a laptop cooling pad addresses this without touching the webcam at all.
6. Check the call application's video processing pipeline
Virtual backgrounds and AI-based noise suppression are GPU- or CPU-intensive. On hardware that's already stressed:
- Disable virtual backgrounds or blur effects
- Turn off AI noise suppression in Zoom (Settings → Audio → Suppress background noise → set to Auto or Off)
- In Teams, disable "Video effects" under Settings → Video Effects
Each of these processes the video stream frame-by-frame before encoding it for transmission, which multiplies your frame pipeline latency.
Cause → symptom → fix at a glance
| What you observe | Most likely cause | First thing to try |
|---|---|---|
| Lag in every app, all the time | USB congestion or driver issue | Move to direct port; reinstall driver |
| Lag only in one app (e.g. Zoom, not OBS) | App-level encoding or effects | Disable virtual background / noise suppression |
| Lag that gets worse over a call | Thermal throttling or memory pressure | Check CPU clocks; close background apps |
| Lag at 1080p, fine at 720p | USB bandwidth or encoder ceiling | Stay at 720p; check USB controller sharing |
| Lag when other USB devices are active | USB controller congestion | Unplug competing devices; reorganize ports |
| Choppy video, no audio lag | Camera dropping frames at source | Check frame rate setting; update firmware |
| Lag introduced after a software update | Driver or app conflict | Roll back driver; check app changelog |
FAQ
Why does my webcam lag only on video calls, not in the camera preview app? Preview apps typically request a simple, low-demand feed directly from the camera driver. Call applications layer on encoding, network transmission, and often video processing (blur, noise suppression) that preview apps skip entirely. The call app is doing significantly more work with the same camera input, so the lag appears there first.
Does USB-C fix webcam lag compared to USB-A? The connector shape doesn't determine bandwidth — the underlying protocol does. A USB-C port running USB 2.0 gives you the same 480 Mbps ceiling as a USB-A 2.0 port. What matters is whether the port is USB 3.x and whether it has a dedicated controller. Check your machine's specs rather than assuming USB-C means faster.
Will a powered USB hub fix my webcam lag? Powered hubs solve the power-delivery problem (some devices misbehave when starved of current) but they do not add bandwidth. All devices on a hub still share the upstream controller's bandwidth. If congestion is the problem, a hub — powered or not — won't help. Moving to a dedicated port on a separate controller will.
My webcam says 60fps but looks like 15fps on calls. Why? 60fps requires roughly double the bandwidth of 30fps. At 1080p 60fps with MJPEG compression, you're pushing a lot of data across USB. If the controller or driver can't sustain it, the camera silently drops to a lower effective frame rate. Try explicitly setting the frame rate to 30fps in the app — you'll get a more consistent result than an unstable 60fps.
Can a bad USB cable cause webcam lag? Yes, particularly with webcams that use detachable cables. USB signal integrity degrades with cable length and quality, causing retransmissions that show up as frame drops. Keep webcam cables under 3 meters (roughly 10 feet) and avoid cheap extension cables. If you're using a cable longer than the one that shipped with the camera, try the original.
Should I update my webcam's firmware separately from the driver? They're different things. The driver is OS-side software; firmware lives on the camera itself. Some manufacturers release firmware updates that fix encoding bugs, improve low-light performance, or change how the camera negotiates with USB. Check the manufacturer's support page for a firmware updater utility — it's separate from the driver download and often overlooked.
Bottom line
Most webcam lag traces back to three things: USB congestion (fix it by moving to a direct port on its own controller), a stale or conflicted driver (fix it by downloading fresh from the manufacturer), or application-level processing overhead (fix it by disabling virtual backgrounds and AI effects). Work through those three before assuming the hardware is at fault. If you've addressed all three and the camera still can't sustain the resolution you want, that's a real hardware ceiling — and at that point, the honest answer is that the camera's encoder isn't fast enough for your use case, not that something is broken.