Zoom Is Killing Your Battery Faster Than Doom Ever Could

Here's a scenario that probably sounds familiar. You sit down for a three-hour stretch of back-to-back video calls, fully expecting your laptop to coast through on a decent charge. By the time the last meeting wraps up, you're scrambling for an outlet. Then, later that weekend, you fire up a visually demanding game for a couple of hours and somehow still have 30% battery left when you're done.

What is going on?

This isn't a fluke, and it's not your imagination. Video conferencing genuinely hammers your battery harder than many gaming sessions, and the reasons why are buried deep in how modern meeting software is actually built. Let's break it down.

The Myth of the "Light" Task

When most people think about power-hungry computing, they picture the obvious stuff — rendering 3D environments, crunching massive datasets, running machine learning models. Video calls feel passive by comparison. You're just... talking into a camera. How bad could it be?

Pretty bad, as it turns out.

The core problem is that video conferencing software is doing an enormous number of things simultaneously, and it's doing them in ways that are particularly unfriendly to battery life. Gaming, by contrast, tends to be a sustained, predictable workload — and modern hardware is surprisingly good at handling those efficiently.

What's Actually Happening During a Video Call

When you join a Zoom, Teams, or Google Meet session, your laptop isn't just pushing pixels around. It's running a complex stack of real-time processes that touch almost every major component in your system.

WebRTC encoding is the big one. The protocol that powers most browser-based and app-based video conferencing — WebRTC — requires your CPU to continuously encode your outgoing video stream and decode incoming streams from other participants. Unlike gaming, which often offloads graphics work to your dedicated GPU (which is purpose-built for that kind of throughput), video encoding in meeting apps frequently lands on your CPU instead. Some apps have improved GPU acceleration over time, but implementation is inconsistent, and plenty of calls still default to CPU-heavy encoding paths.

Constant CPU polling keeps your processor awake. Meeting software is designed to be hyper-responsive. It's perpetually checking for new audio packets, monitoring your microphone input, watching for network changes, and managing connection quality in real time. This creates a pattern of rapid, repeated CPU wake-ups — sometimes hundreds of times per second. That polling behavior prevents your processor from dropping into low-power sleep states, which is where modern chips save a significant chunk of energy. A game running at a locked frame rate actually gives your CPU more predictable work, which modern power management handles far more gracefully.

Background sync is piling on. While you're on that call, your meeting app is almost certainly not the only thing running. Slack is syncing. Outlook is checking for new mail. Chrome has seventeen tabs doing who-knows-what. These background processes wouldn't matter much if your system were otherwise idle, but layered on top of an already demanding video session, they push your overall power draw into territory that gaming rarely reaches during normal play.

Your display is working overtime too. During video calls, your screen brightness is typically cranked up so you can see participants clearly. Screen brightness is one of the single largest contributors to battery drain on any laptop. Gaming doesn't necessarily require the same sustained brightness levels, especially if you're playing in a dimmer environment.

Why Gaming Handles Power Better Than You'd Expect

Modern game engines and graphics drivers are engineered to work with your hardware's power management features, not against them. When a game is running at a steady frame rate, your GPU gets into a rhythm. Power delivery becomes predictable. The system can allocate resources efficiently without constantly spinning up and winding down.

There's also the GPU offloading factor. Visually intensive games push the heavy lifting to your dedicated graphics card, which — despite being powerful — is optimized for exactly this kind of sustained parallel workload. Your CPU gets to focus on game logic rather than also serving as a makeshift video encoder.

The result is that a demanding game can actually produce a more efficient power profile than a patchwork of meeting software, browser tabs, and background sync processes all fighting over your CPU at once.

Practical Ways to Stop the Bleed

None of this means you're stuck watching your battery percentage nosedive every Monday morning. There are real things you can do to claw back some runtime.

Check your app's hardware acceleration settings. Zoom, Teams, and Google Meet all have options buried in their settings menus to enable or disable GPU acceleration for video processing. If you have a discrete GPU, enabling hardware acceleration can dramatically reduce the CPU burden during calls. It's worth testing — results vary depending on your specific hardware.

Kill the background noise. Before your next big call block, close anything that doesn't need to be open. Seriously. Email clients, extra browser tabs, cloud sync apps — pause or close them. You'd be surprised how much headroom this frees up.

Dial back your video quality. Most meeting platforms let you cap your outgoing video at 720p instead of 1080p. Halving your resolution doesn't make you look dramatically worse on a call, but it can meaningfully reduce the encoding load on your CPU.

Turn off your video when you don't need it. This one's obvious but worth saying. If you're in a meeting where you're mostly listening, going camera-off removes the encoding workload entirely. Your battery will thank you.

Plug in when you can, but be strategic about it. If you're at a desk, just plug in during call-heavy work blocks. Save battery mode for when you're actually mobile. It sounds simple because it is.

Look at your power plan settings. On Windows, switching to a Balanced or Power Saver plan during calls (rather than High Performance) can reduce how aggressively your CPU runs during those polling-heavy workloads. On a Mac, Low Power Mode does similar work.

The Bigger Picture

This whole situation is a pretty good illustration of how misleading our intuitions about computing can be. "Heavy" tasks aren't always the ones that drain your battery fastest. It's the chaotic, interrupt-driven, multi-process workloads — the kind that modern remote work generates constantly — that tend to be the real power vampires.

As more of us build our work lives around portable setups, understanding these patterns matters. Your laptop isn't misbehaving when it dies during a call marathon. It's just doing exactly what you asked it to do, in a way that happens to be genuinely hard on a battery.

Knowing that is half the battle. The other half is adjusting your habits and settings to work with your hardware instead of unknowingly working against it.