GlossaryProtocolsIntermediate

WireGuard

WireGuard is a modern VPN protocol built to be fast and simple. Its code is small enough to audit properly, and it connects quicker and runs faster than older protocols like OpenVPN.

Last updated July 29, 2026

Definition

WireGuard is the set of rules a VPN app uses to build an encrypted tunnel between your device and a VPN server. It was released in 2020 as a deliberate rethink of older protocols such as OpenVPN and IPSec, which had grown large and complicated over decades.

Its defining feature is size. OpenVPN runs to roughly 100,000 lines of code; WireGuard is around 4,000. That matters more than it sounds: less code means fewer places for bugs to hide, and a codebase small enough that security researchers can actually read all of it.

Why it feels faster

  • It runs closer to the hardware. WireGuard can operate inside the operating system kernel, so traffic is not constantly shuffled between system layers.
  • Connections start almost instantly. The handshake takes a single round trip, so switching servers feels immediate rather than taking several seconds.
  • It survives network changes. Moving from Wi-Fi to mobile data does not drop the tunnel — useful on a phone that changes network all day.
  • It is easier on the battery, because it only does work when data is actually moving.

How the encryption is arranged

WireGuard does not let you choose from a menu of ciphers the way OpenVPN does. It picks one modern, well-regarded set and uses it everywhere. That sounds restrictive, but it removes a whole class of misconfiguration, and if a weakness were ever found the protocol version is simply replaced rather than patched around.

Each side has a public and a private key, exactly like SSH. Your device and the server exchange public keys once, then recognise each other instantly on every future connection. Traffic travels over UDP, which is quicker than TCP but can be blocked on restrictive networks — which is why providers still keep OpenVPN available as a fallback.

The privacy catch, and how providers solve it

Plain WireGuard was designed for connecting your own machines, not for running a commercial VPN. To route traffic it assigns each connected device a fixed internal IP and keeps it on the server — which, left alone, would be a record linking a user to a session.

Reputable VPN providers work around this rather than ignore it, typically by adding a layer that assigns addresses dynamically and discards them, or by keeping the whole system in RAM so nothing survives a reboot. Several ship it under their own name — NordLynx at NordVPN, for example — precisely because it is modified WireGuard rather than the stock protocol. If a provider offers WireGuard, it is fair to ask how they handle this.

Should you use it?

For most people, yes — it is the best default in almost every VPN app today, and the speed difference is genuinely noticeable on fast connections. Switch to OpenVPN only if WireGuard is blocked on the network you are using, since OpenVPN can disguise itself as normal HTTPS traffic in a way WireGuard cannot.

Examples

1

Picking WireGuard in your VPN app's protocol settings and noticing servers connect in about a second instead of five

2

NordVPN's NordLynx and Mullvad's WireGuard support, both built on the protocol with privacy adjustments layered on top

3

Running a personal VPN on a home server or cloud VPS so you can reach your own network securely while travelling

4

Keeping a VPN connection alive on a phone that switches between Wi-Fi and mobile data throughout the day

Common Use Cases

Everyday VPN use where speed matters most
Streaming and gaming over a VPN with minimal slowdown
Mobile VPN connections that survive network switching
Self-hosted personal VPNs and remote access to a home network
Site-to-site links between offices or cloud networks
Low-latency connections for automation and scraping infrastructure

Frequently Asked Questions

Yes, usually by a clear margin. It runs in the kernel, uses a much leaner codebase, and completes its handshake in one round trip. On a fast connection you will typically notice both higher throughput and much quicker server switching.
Yes. It uses modern, well-regarded cryptography and has been independently reviewed. Its small size is itself a security advantage, because researchers can audit the entire codebase rather than sampling parts of it.
Because they have modified it. Standard WireGuard stores a fixed internal IP for each connected device, which conflicts with a no-logs promise. Providers add a layer that assigns addresses dynamically, and brand the result — NordLynx being the best-known example.
When WireGuard is blocked. WireGuard runs over UDP and is fairly easy to identify, so some restrictive networks and countries filter it. OpenVPN can run over TCP port 443 and blend in with ordinary HTTPS traffic.
Yes. There are official clients for Windows, macOS, Linux, Android, iOS, and most routers, and virtually every major VPN provider now supports it in their apps.
Yes, and it is one of the easier protocols to self-host. A small cloud server plus a key pair is enough. Bear in mind a personal VPN gives you control but not crowd privacy, since all traffic from that server is obviously yours.