Does a VPN Drain Your Phone's Battery? The Real Numbers
A 2026 measurement by West Coast Labs found that a well-configured VPN adds just 1.6–2.1% to real power draw during an hour of video streaming, with idle background overhead below 0.5% per hour. That’s nowhere near the 15–20% hit some people report after a night with the VPN running — and the gap between those two numbers comes down to one thing: which protocol is doing the work.
What actually eats the battery
Three things determine the real cost. The CPU has to encrypt and decrypt every packet that leaves and enters the phone. Some protocols send keepalive packets on a fixed schedule, which briefly wakes the radio even when no data is moving. And the phone’s own battery-usage screen tends to overstate the VPN’s share, because it typically ranks apps by data volume rather than actual energy spent.
Your phone’s battery menu blames apps by data volume, not real power draw — a VPN that moves a lot of traffic can look like the top battery hog even when its actual CPU cost is minimal.
Legacy protocols vs modern ones: the real gap
| Legacy protocols (OpenVPN-style) | Modern protocols (WireGuard-based) | |
|---|---|---|
| Where encryption runs | Userspace | Kernel |
| Keepalive traffic | Every ~10 seconds | Silent between packets |
| Handshake | Multi-step, repeated | Single round trip |
| Typical 8-hour overnight drain | ~20% just staying connected | ~5–10% |
| CPU overhead at idle | Noticeable | Close to zero |
Independent battery benchmarks across iPhone 15/16 and current-generation Android flagships put WireGuard-based connections at roughly a third of the battery cost of OpenVPN for the same amount of data — the difference is architecture, not brand. RunVPN runs on AmneziaWG by default, with VLESS-Reality available under the hood for a stable connection.
Where the difference actually happens
The top row is what makes older protocols expensive: encryption running as a regular app process, plus a steady drip of keepalive packets keeping the radio half-awake. The bottom row is why kernel-level protocols cost so little — one handshake, then silence until there’s actually data to move.
Why your phone’s age matters too
- 2022-and-newer flagships ship with dedicated crypto hardware, so a VPN adds roughly 1–3% to battery use even during heavy sessions.
- Phones from before 2020 lack that hardware and lean on the main CPU for every encrypted byte, which can push the drain to 5–10%.
- Background app habits matter more than the VPN itself — a VPN sitting idle alongside a phone that’s also syncing five other apps in the background will get blamed for all of it.
How AmneziaWG keeps a connection light
- It runs in the kernel, not as a userspace process, so there’s no constant handoff between the app and the operating system for every packet.
- It uses ChaCha20-Poly1305 encryption, a cipher built for speed on mobile CPUs — independent benchmarking has measured CPU overhead from this kind of kernel-level encryption well under 1%, even under load.
- It completes its handshake in a single round trip and then stays silent — no repeated keepalive chatter waking the radio every few seconds.
- AmneziaWG is RunVPN’s default, tuned for a stable connection, so the app doesn’t need to fall back to heavier retry logic that would cost extra battery.
Getting the most battery life out of an always-on VPN
- Pick an app built on a modern protocol rather than legacy OpenVPN configs — this alone accounts for most of the difference.
- Keep the app updated — protocol and battery optimizations ship in updates, not in a config you set once.
- Don’t judge by the battery-usage screen alone — check actual screen-on time and standby drain over a few days instead of one data point.
- Give a modern phone the benefit of the doubt — if battery use spikes only on an older device, the hardware, not the VPN, is usually the bottleneck.
FAQ
Does leaving a VPN on overnight kill your battery? With a kernel-level protocol like AmneziaWG, no — idle overhead measured in recent testing stays under 0.5% per hour, so an 8-hour night costs a few percent at most.
Why does my phone’s battery screen show the VPN using so much power? Because that screen typically ranks apps by data transferred, not actual energy used. A VPN routing a video-streaming session will show high data volume even though its CPU cost is small.
Is WireGuard actually better than OpenVPN for battery, or is that marketing? It’s architecture, not marketing: WireGuard-based protocols run in the kernel with a lightweight cipher and a single handshake, while OpenVPN runs in userspace and sends periodic keepalives — independent testing has repeatedly measured lower power draw for the former.
Does RunVPN use a battery-heavy protocol? RunVPN defaults to AmneziaWG, the kernel-level protocol described above, built for a stable connection without the overhead that drains older VPN setups.