Audio-Visual Latency & Sync
Why does video delay increase over long Zoom meetings?
Quick answer: Delay that creeps up over an hour is your system's resources being progressively consumed, not Zoom degrading. Thermal throttling is the usual cause, with background process buildup and shifting network conditions behind it. Cooling and closing apps beforehand prevent most of it.
Delay creeping up over a long call is almost always a sign of your system's resources being progressively consumed, not something wrong with Zoom itself mid-call.
The tell is the pattern: a call that starts clean and degrades steadily points at heat or resource accumulation, whereas a call that is bad from the start points at configuration.
Try It Yourself
Test whether your machine degrades under sustained load
Runs your camera and processor under continuous load and reports whether performance falls away over time, which reproduces the failure outside a real meeting.
Run the Hardware Stress & Headroom TestThermal throttling is a common and real cause
Sustained video encoding, especially with effects such as background blur running for an hour or more, keeps your processor working hard continuously.
Many laptops reduce their clock speed as they heat up to avoid overheating, which directly slows real-time video and audio processing and increases lag as the meeting goes on.
Memory and background process buildup
The longer a machine runs without a restart, the more background processes and memory fragmentation accumulate, competing with your call software for the same limited resources.
Restarting before a long scheduled call is a genuinely effective preventive step, not superstition.
Reproduce the degradation outside a real meeting with the Hardware Stress & Headroom Test.
Check for other apps quietly consuming resources over time
Browser tabs, cloud sync tools and auto-updating applications can ramp up activity partway through a long call without any obvious trigger.
Scheduled tasks are the worst offenders, because they fire on a timer rather than in response to anything you did — which is exactly why the problem seems to appear from nowhere mid-meeting.
Network conditions change over an hour too
Other devices on your network joining or starting large downloads, or your provider's own congestion patterns, can shift during a long call in ways they would not during a short one.
This is worth ruling out before blaming the machine, especially on a shared household connection in the evening.
If the drift shows up as lip-sync error, quantify it with the Audio/Video Sync Test.
What actually helps
Closing unnecessary background applications before a long call, ensuring good airflow and cooling for your laptop, and disabling non-essential video effects for calls you expect to run long are the most effective preventive steps.
- Restart the machine before a long scheduled call.
- Raise the laptop on a stand so air can reach the underside.
- Turn off background blur and filters for calls over an hour.
- Pause cloud sync clients and close unused browser tabs.
What to check afterwards
If this is a recurring pattern specifically on long calls, run a sustained-load stress test separately rather than during a real meeting.
That reveals whether your system's performance genuinely degrades under extended load, which points toward a hardware or cooling issue rather than a Zoom-specific one.
To check whether the network rather than the machine is shifting, run the Packet Loss & Jitter Simulator.
Effects and quality settings worth disabling for long calls
Every per-frame effect adds sustained processor load, which is what brings on throttling sooner.
Zoom
Settings → Background & Effects, and Settings → Video → Enable HD
Turning both off for long calls measurably reduces heat output on laptops without hardware encoding.
Microsoft Teams
Effects and avatars → Background effects
Teams also offers no quality control, so effects are the main load you can remove.
Google Meet
Effects (✨) → Backgrounds, and Settings → Video
Because Meet runs in the browser, its effects are usually more expensive than the equivalent native ones.
OBS Studio
Settings → Output → Encoder
Switching to a hardware encoder moves the work off the CPU, which reduces heat and delays throttling considerably.
The table below shows how much sustained processing load each tool's effects add and what control you have to reduce it:
| App | Practical ceiling | Manual control |
|---|---|---|
| Zoom | Effects and HD both add sustained load | Disable effects, disable HD |
| Microsoft Teams | Background effects add per-frame cost | Disable background effects |
| Google Meet | Browser-based effects cost extra CPU | Disable effects, lower resolutions |
| OBS Studio | Encoder choice dominates sustained load | Hardware or software encoder |
Troubleshooting checklist: delay growing through a long call
Prevention beats mid-call correction here, since throttling does not recover until the machine cools.
- Restart the machine before any call you expect to run over an hour.
- Close unused browser tabs and quit applications you will not need.
- Pause cloud sync clients such as Dropbox, OneDrive and iCloud.
- Raise the laptop on a stand so air can reach the underside.
- Move it off soft surfaces such as beds and cushions, which block the intake.
- Turn off background blur, virtual backgrounds and appearance filters.
- Disable HD video for calls where picture quality is not the priority.
- Run a sustained-load stress test outside a real meeting to confirm the pattern.