Does a VPN drain your phone battery?
A VPN uses some battery for encryption and keepalives, typically a small share of the day with WireGuard; distant servers and reconnects make it worse.
Yes, a VPN uses some battery, and on a modern phone with a modern protocol the amount is typically a small share of a day's use, and less again when the phone is idle. The cost comes from encrypting packets, from keeping the radio awake to send keepalives, and above all from reconnecting. A VPN that is stable on a nearby server barely registers. A VPN that drops and reconnects every few minutes, or that is stuck on a slow transport, can show up near the top of the battery list.
Where the battery goes
Four things cost power, and they are not equal.
Encryption. Every packet is encrypted on the way out and decrypted on the way in. WireGuard uses modern ciphers that phone processors handle efficiently, so this cost is small and scales with how much data you move. Older protocols do more work per packet and cost more for the same traffic.
Keepalives. A tunnel through a mobile carrier's address translation goes stale if nothing is sent for a while, so the app sends a small packet every so often to keep the path open. Each one wakes the radio briefly. Done every 25 seconds or so this is cheap; done every few seconds, or by several apps at once, it stops the radio ever sleeping properly.
Reconnects. A handshake costs more than minutes of idle keepalives: the app wakes fully, the radio goes to full power, the tunnel is negotiated and the routes are reinstalled. A VPN that reconnects a few times a day is fine. One that reconnects every time the screen turns off, or every time the phone hops between Wi-Fi and data, is the most common reason a VPN appears high in the battery list.
The transport. A TLS-wrapped transport on TCP, which the app falls back to when a network blocks UDP, does more work per byte because of its smaller packets and the extra TCP layer. On a restrictive network you pay a little more battery for having a tunnel at all.
Why distance matters here too
A far-away server does not cost more per packet, but it costs more per interaction. Each page load or message takes more round trips to complete, the radio stays in its high-power state longer while waiting, and lossy long routes cause retransmissions. Choosing a city with a low measured round trip is a battery decision as well as a speed one. The latency versus bandwidth explainer covers what that figure means.
What Android itself does
Android's battery optimisation will pause or kill background services it thinks are idle, and a VPN service is a background service. If the VPN is killed, the app has to reconnect when it is next allowed to run, and the reconnect costs more power than the idle tunnel would have. Some manufacturers add their own, more aggressive killers on top. The result is a loop: the optimiser kills the VPN to save power, the VPN reconnects, the optimiser kills it again, and the battery list blames the VPN.
If you see that pattern, the fix is to exempt the VPN app from battery optimisation and, on phones that need it, from the manufacturer's own background limits. Stopping the battery optimiser from killing your VPN walks through the settings, and keeping a VPN alive on Samsung and Xiaomi phones covers the manufacturer layers.
How to tell what is going on
Android's battery screen lists usage per app, and it is worth reading properly rather than reacting to the position in the list.
| What you see | What it usually means |
|---|---|
| VPN low on the list, stable connection | Normal; nothing to change |
| VPN high on the list, heavy data use that day | Encryption cost of the traffic itself; expected |
| VPN high on the list, light use, many reconnects | Battery optimiser or an unstable network is killing the tunnel |
| VPN high on the list only on one Wi-Fi | That network forces the slower TCP transport |
| Every network app high, not just the VPN | Poor signal keeping the radio at full power |
The third row is the one worth fixing, and VPN keeps disconnecting on Android goes through its causes.
What actually reduces it
- Use a city with a low measured round trip.
- Let the app use WireGuard where the network allows it; it is the lightest option.
- Exempt the VPN app from battery optimisation so it is not killed and restarted.
- Avoid running two VPN or filtering apps at once; they fight, and both reconnect.
- If the VPN is only heavy on one Wi-Fi network, that network is the cause, not the app.
Do not expect a large saving from turning the VPN off when idle. An idle WireGuard tunnel costs almost nothing; the handshake to bring it back costs more than an hour of idling.
Culvert VPN uses WireGuard wherever the network allows it, sends keepalives sparingly, and reconnects automatically at the 24-hour session ceiling rather than repeatedly, so a stable connection stays cheap; it is free on Google Play.
Questions people also ask
Does the VPN use battery when I am not using the phone?
A little. The app has to send an occasional keepalive so the connection survives, which wakes the radio briefly. A well-built app sends these rarely and lets the radio sleep between them.
Will turning the VPN off at night save much?
Usually not much, if the app is idle and the connection is stable. What saves battery is stopping the causes of drain: a server that keeps dropping, or a network that forces the app to reconnect repeatedly.
Is Always-on VPN worse for battery?
Not by itself. It keeps the tunnel up across app restarts, which avoids repeated handshakes and can save power. It costs more only if the tunnel keeps failing and Android keeps restarting it.
All 12 guides in Speed, battery and reliability · Every guide