VPN protocols explained: WireGuard, OpenVPN and IKEv2 in 2026

Protocol choice decides three things you will actually feel: how much CPU your tunnel burns, how fast it reconnects after the network changes, and how much throughput survives on your hardware. Everything else in the feature list is secondary to those three.

How each one actually works

WireGuard

A single handshake based on Curve25519, ChaCha20-Poly1305 and BLAKE2s, running over UDP. Stateless by design: the server keeps no session table, so a peer that changes address simply sends the next packet and continues. The whole implementation is a few thousand lines, which is why it costs so little CPU and why the roaming behaviour is good.

OpenVPN

TLS-based, available over UDP or TCP, with a wide choice of cipher suites and a long history of interoperability. TCP mode survives hostile networks better than raw UDP, at the cost of head-of-line blocking and noticeably more overhead. Session setup is heavier: certificate exchange plus a TLS handshake, which is visible as a slower reconnect.

IKEv2 / IPsec

Native to iOS and macOS and well supported on Windows and Android, which makes it the least invasive choice on mobile. Its MOBIKE extension handles address changes cleanly, so hand-offs between Wi-Fi and cellular are fast. Configuration is the fiddly part, and the cipher negotiation has more moving pieces than WireGuard.

Side by side

WireGuardOpenVPNIKEv2/IPsec
TransportUDP onlyUDP or TCPUDP (500/4500)
HandshakeOne round tripTLS, several round tripsTwo round trips (IKE_SA + CHILD_SA)
CPU costLowestHighestLow to moderate
Reconnect after network changeImmediateFull handshakeFast via MOBIKE
Mobile supportThird-party appThird-party appBuilt into OS
Battery impact on phonesModerate (app wake-ups)HigherLowest (system stack)
Cipher flexibilityFixed, modern setConfigurable legacy and modernConfigurable

Throughput: where the ceiling really is

Published figures are almost always measured on server-grade hardware, which is not the machine you own. On consumer devices the practical ceilings look roughly like this, and they move with CPU generation:

Device classWireGuardOpenVPN (UDP)IKEv2
Modern laptop, 8+ cores800 Mbps – multi-gigabit250–500 Mbps500–900 Mbps
Older laptop, 2–4 cores250–450 Mbps80–180 Mbps200–350 Mbps
Phone, mid-range150–350 Mbps60–120 Mbps150–300 Mbps
Travel router80–250 Mbps25–60 Mbps60–150 Mbps

These are ranges, not promises. Measure your own: the same line, same server, both protocols, five runs each, median of the last four. If WireGuard is not at least twice the OpenVPN figure on the same device, the bottleneck is elsewhere — usually MTU or a single-core server.

The settings that decide the outcome, regardless of protocol

Most "protocol is slow" reports resolve to one of these four parameters:

Which to pick

You wantPickWhy
Maximum throughput on a fast lineWireGuardLowest per-packet cost, kernel implementations available
Fastest reconnect on a phone that moves between networksIKEv2MOBIKE plus the system stack, no app involved
Compatibility with old devices or restrictive networksOpenVPN (TCP)Widest support, survives UDP-hostile paths
Simple self-hostingWireGuardTwo peers, one interface, no certificate authority
Least battery drain on iOSIKEv2Handled by the OS networking stack
Local rules on encrypted tunnels differ and change; corporate devices often forbid them entirely. Check both before configuring a client, and keep the kill switch enabled so a dropped tunnel never exposes traffic.

Ten-minute verification

  1. Run the same transfer on both protocols; record median throughput.
  2. ping the same host in each state; record the added latency.
  3. Toggle airplane mode; time the reconnect.
  4. Lower MTU by 40 bytes and repeat one large transfer — if it improves, MTU was your bottleneck.
← All guides