WireGuard vs OpenVPN: the honest comparison
WireGuard is faster, smaller, easier to audit, and has fewer knobs. OpenVPN is older, has wider firewall traversal, and works in restrictive networks where WireGuard's UDP-only design fails. Here's the full picture.
The five-second answer
- Personal VPN, modern device, normal network: WireGuard.
- Need to traverse hostile / DPI-heavy firewalls (China, some hotels, captive portals): OpenVPN over TCP/443.
- Need granular per-user policies and a long-lived RADIUS or LDAP integration: OpenVPN.
- Site-to-site between two cloud regions: WireGuard.
- You already have an OpenVPN server that works: probably keep it; switch only if you have a concrete reason.
Throughput
WireGuard is meaningfully faster in real-world conditions on the same hardware. The most-cited number is from the original WireGuard benchmark — roughly 1 Gbps WireGuard vs 250 Mbps OpenVPN on similar CPUs. Our own benchmarks on a 2 vCPU Inferno VPS (single TCP stream over a 1 Gbps link, sender and receiver both in Helsinki):
| VPN | Throughput | CPU (server) |
|---|---|---|
| No VPN | 940 Mbps | 3% |
| WireGuard (UDP) | 912 Mbps | 22% |
| OpenVPN (UDP, AES-256-GCM) | 340 Mbps | 78% |
| OpenVPN (TCP, AES-256-GCM) | 180 Mbps | 82% |
Two reasons WireGuard wins: it runs in the kernel (Linux mainline since 5.6) and its cryptographic primitives are simpler. OpenVPN sits in userspace and copies packets across the kernel boundary on every send.
Code size and auditability
WireGuard is roughly 4,000 lines of code. OpenVPN is approximately 100,000 lines including its OpenSSL dependency. Smaller surface area means fewer bugs, faster audits, and more reviewers per line. WireGuard's whitepaper is short enough to read in one evening; OpenVPN's source spans years of accumulated patches.
This matters less for "is this safe today" — both protocols are considered secure — and more for long-term confidence and ease of debugging.
Crypto and configurability
OpenVPN supports many cipher suites, hash algorithms, and key exchange options. Flexibility is its design goal. The cost is configuration mistakes: insecure cipher combinations are still selectable.
WireGuard supports exactly one cipher suite (ChaCha20-Poly1305 for symmetric encryption, Curve25519 for key exchange, BLAKE2s for hashing, HKDF for key derivation). No negotiation, no downgrade attacks, no foot-guns. If the suite ever needs to change, that's a protocol version bump, not a config edit.
Connection model
OpenVPN maintains a stateful TLS-like session. The client negotiates, authenticates, and stays connected until disconnected. Reconnects after a network change typically take 5-15 seconds.
WireGuard is stateless at the network level — there is no "connection," just keys and a UDP flow. Roaming between Wi-Fi and cellular is invisible to the application layer; the next packet's source IP just changes and WireGuard adapts. Subjectively, this makes mobile use feel instant.
Firewall traversal
This is OpenVPN's one clear win. OpenVPN over TCP/443 looks remarkably like HTTPS to a casual deep-packet inspector. With --tls-crypt the handshake doesn't even reveal that it's a VPN until well into the conversation.
WireGuard is UDP-only and its packet structure is recognizable. Many restrictive networks block UDP entirely (some hotels, corporate guest Wi-Fi, captive portals on mobile) or block known VPN ports. There is no "WireGuard over TCP" out of the box — workarounds exist (udp2raw, AmneziaWG, WireGuard-over-Shadowsocks) but they're not first-class.
If you regularly travel through hostile networks, OpenVPN UDP/1194 with TCP/443 fallback is more resilient than WireGuard.
Authentication model
| WireGuard | OpenVPN | |
|---|---|---|
| Per-peer keys | Yes (only option) | Yes |
| Username + password | No | Yes |
| X.509 certificates with CA chain | No | Yes |
| RADIUS / LDAP / SAML | No (out of band) | Yes (plugins) |
| MFA | No (out of band) | Yes (PAM, TOTP plugins) |
For a personal VPN, "just keys" is a feature — fewer moving parts. For an enterprise with existing identity infrastructure, OpenVPN's plugin ecosystem is hard to replicate with WireGuard alone.
Server-side complexity
WireGuard server: one wg0.conf file, one systemd unit, < 30 lines of config for most setups. See our 10-minute install.
OpenVPN server: a CA, server cert, client certs, CRL, DH params, TLS-crypt key, server.conf with 30+ directives, ccd/ directory for per-client config, scripts/ for connect/disconnect hooks. A first-time install commonly takes a day. Easyrsa helps; it doesn't eliminate the complexity.
Battery and idle behavior
WireGuard's per-packet overhead is small and there's no keepalive unless you ask for one (PersistentKeepalive = 25). Idle drain on a phone is negligible.
OpenVPN's idle drain is also low in practice, but the larger packets and userspace processing add up on long sessions. Anecdotal — your mileage varies.
What about IKEv2?
IKEv2/IPsec is the other modern option. Native on iOS and macOS, strong reconnect behavior on mobile, decent throughput. It's a reasonable third choice but most self-hosters skip it because the server-side setup (strongSwan) is configuration-heavier than either WireGuard or OpenVPN.
When to migrate WireGuard → OpenVPN (or vice versa)
Migrate to WireGuard if
- You're CPU-bound on the current OpenVPN server.
- Mobile users complain about reconnect lag.
- You're spending more on certificate management than on the rest of the VPN combined.
- You don't actually use the OpenVPN flexibility (RADIUS, etc.).
Migrate to OpenVPN if
- You repeatedly hit networks that block UDP entirely.
- You need to plug into existing identity systems (RADIUS, LDAP).
- You need an obfuscation story your auditor will accept.
The pragmatic answer
For 90% of self-hosters reading this page, WireGuard is the better choice. It's faster, smaller, easier to operate, and the ecosystem around it (wg-easy, Tailscale, Headscale) is healthy.
Keep OpenVPN in your back pocket for the specific situations where WireGuard's design choices are wrong for you — restrictive networks, enterprise identity integration. Don't pick OpenVPN out of habit; it earned its reputation in an era when WireGuard didn't exist.
VPS for either VPN?
Both run comfortably on a 1-2 GB Inferno plan. The difference is throughput at the cap — WireGuard saturates a $4 VPS's bandwidth; OpenVPN typically tops out below it.
What to do next
- Picked WireGuard? Install in 10 minutes.
- Want a UI? wg-easy.
- Plan to use it on phones too? Per-OS client setup.
- Want only some traffic through the VPN? Split tunneling.
Author: Daniel Ferro — Lisbon. Last reviewed: 2026-05-22 with own benchmarks on Inferno 2 vCPU plan.