Analysis • Power Consumption

What Drains a Laptop Battery, Ranked

Not all battery vampires are created equal. We ranked every major component and software behaviour by measured energy impact so you know exactly where your hours are going.

By Daniel Orthé, Technology Correspondent — • 7 min read

Battery life anxiety is endemic among laptop users. We watch the percentage tick down, instinctively reach for a charger, and wonder whether it's the browser or some background process to blame. The answer is almost always: both, plus seven other things you hadn't considered.

To cut through the guesswork, we instrumented a 14-inch laptop across two weeks of real workloads, correlating inline power-meter readings with component-level performance counters. The result is the most comprehensive laptop battery drain breakdown we have published to date.

The Ranked Table

The table below shows each drain source, its typical sustained power draw during moderate use, and its relative share of total laptop power at a typical 12W average draw. Numbers are hardware-averaged; your figures will vary.

# Component / Behaviour Peak Draw Idle Draw % of Budget Notes
1 Display (max brightness) 9.5 W 3.0 W 25–35% OLED at full white; IPS backlight is constant
2 Video decode (YouTube 1080p) 8.2 W — 20–28% Hardware codec lowers this ~60%; browser decode is worst case
3 Heavy JS execution 7.8 W — 18–24% Burst during parse + JIT; sustained by timer-heavy pages
4 GPU compositing / rendering 4.5 W 0.8 W 12–18% CSS animations, WebGL, complex layouts
5 Wi-Fi radio (active transfer) 3.8 W 0.25 W 8–14% Idle PSM draws much less; background beacons prevent PSM
6 CPU idle / background processes 3.2 W 1.5 W 8–12% Includes kernel, Spotlight, iCloud sync, Gatekeeper
7 Keyboard backlight (max) 1.2 W 0 W 2–6% Off = zero; easily recoverable 30–90 min of battery life
8 Active cooling (fan) 0.8 W 0 W 2–5% Indirect savings from throttling prevention are larger
9 Storage (NVMe active reads) 0.7 W 0.05 W 1–4% Surprisingly small; NVMe sleeps aggressively
10 Bluetooth (connected, idle) 0.35 W 0.1 W 1–2% Headphones connected vs off: ~20-min runtime difference/day
11 USB-C peripherals (bus power) 0.3 W 0.05 W <1% Per device; thunderbolt dock can add several watts
12 Memory (LPDDR5 active) 0.25 W 0.08 W <1% Unified memory on Apple Silicon; slightly different on Intel

The Display Problem

It is not a coincidence that the display tops the list. Most users leave brightness at 100% — or let Auto Brightness push it there whenever a window catches sunlight. At maximum brightness on an OLED panel, the display alone can consume nearly half the laptop's entire power budget for a typical reading workload. Dropping brightness from 100% to 50% typically saves 3–5 W continuously, which translates to 40–70 additional minutes on a 60 Wh battery.

The dark mode effect deserves special mention here. On OLED hardware, a fully dark-themed interface at 50% brightness draws comparable power to the same UI in light mode at 35% brightness. If you're serious about battery life on OLED, dark mode isn't aesthetic — it's engineering.

Video's Hidden Complexity

Streaming video ranks second, but the range is enormous. A browser decoding H.264 in software draws 7–9W from the CPU alone. The same stream decoded via the dedicated hardware video engine (H.264 or HEVC, present on every modern laptop) draws under 2W for the decode step. Chrome and Firefox both use hardware decode when available, but HEVC support on Windows varies by driver; on macOS it is consistently enabled.

The remaining power goes to the display (white player controls on dark video background draws surprisingly little on OLED), network radio, and the browser compositor running at 60 fps. VP9 and AV1 streams from YouTube use hardware decode on supported platforms — a significant win for battery life that most users are unaware of.

  1. Enable hardware decode in browser settings where it isn't automatic
  2. Prefer 720p over 1080p when quality doesn't matter — lower bitrate, less decode work
  3. Use Picture-in-Picture and minimise the browser window — the compositor runs faster
  4. Mute tab audio when you only need video — the audio subsystem adds ~150 mW

The JavaScript Sawtooth Revisited

Our longer feature The Hidden Cost of a Browser Tab goes deep on the JavaScript problem, but a brief summary is warranted here. The issue is not just peak power — it is sustained elevated power from timer-driven background activity. Every open tab is, by default, a small power consumer even when you aren't looking at it, because browser background tabs are throttled but not fully silenced. Ten open tabs, each polling an analytics beacon every 500 ms, collectively produce a power floor that prevents the CPU from reaching its deepest idle states.

One-click browser extensions that enforce aggressive tab sleeping (like Great Suspender alternatives, or Chrome's built-in Memory Saver) can meaningfully reduce this floor. In our tests, enabling tab sleeping on a 12-tab browser session reduced idle-mode power draw by 18–26%.

The Bright Side: Quick Wins

Not all battery improvements require understanding V8's JIT compiler. Some are immediately actionable:

  1. Reduce brightness by 30% — saves 1.5–3 W immediately
  2. Turn off keyboard backlight — saves 0.8–1.2 W when typing in a lit room
  3. Use content blockers — removes 4–14 background scripts per page, 20–35% JS power reduction
  4. Close unused tabs — each tab has a CPU wake budget; closing 5 open tabs can save 0.4–1 W continuously
  5. Enable Battery Saver / Low Power Mode — modern OSes throttle less-critical background work significantly, often adding 20–30% runtime
  6. Disconnect Bluetooth when not in use — small but free

Battery technology has improved dramatically, but the power demands of modern software have grown in parallel. The gap between what hardware can deliver and what software demands has, if anything, widened. Understanding that gap — and the specific components responsible — is the first step toward closing it.

Analysis Power Laptops Performance