VPN Protocols Explained and Which One to Pick
You open your VPN app's settings and see a dropdown with WireGuard, OpenVPN UDP, OpenVPN TCP, IKEv2 and maybe a branded protocol you have never heard of.

You open your VPN app's settings and see a dropdown with WireGuard, OpenVPN UDP, OpenVPN TCP, IKEv2 and maybe a branded protocol you have never heard of. Pick the wrong one and your connection drops every time your phone switches from Wi-Fi to mobile data, or your speed falls by half. This guide to VPN protocols explained in plain terms will help you choose once and stop fiddling.
A protocol is simply the set of rules your device and the VPN server use to build the encrypted tunnel. They all aim to keep your traffic private, but they trade off speed, reliability on unstable networks, and how easily they get past restrictive firewalls.
VPN protocols explained in one paragraph each
WireGuard
WireGuard is the newest of the mainstream protocols, built into the Linux kernel in 2020. Its code base is around 4,000 lines, compared with tens of thousands for older protocols, which makes it easier to audit. It uses modern encryption (ChaCha20 and Curve25519) and is usually the fastest option, often by 20 to 40 percent over OpenVPN on the same server. It reconnects almost instantly when your network changes.
OpenVPN
OpenVPN has been around since 2001 and is the long-standing default for many services. It is open source, heavily audited and very flexible. It can run over UDP, which is faster, or TCP, which is slower but more reliable on networks that block or interfere with traffic. Its main downside is speed and battery use on phones.
IKEv2/IPsec
IKEv2 is built into iOS, macOS and Windows. Its standout feature is a mobility extension called MOBIKE, which keeps your session alive when you move between networks. It is a solid choice on phones, though some restrictive networks block the ports it uses.
Branded protocols
Several providers ship their own protocols, often built on top of WireGuard with extra privacy features, such as not storing your real IP address on the server. Some are well documented and audited. Others are closed, which means you are trusting a marketing page rather than code anyone has checked.
How the main protocols compare
| Protocol | Speed | Network switching | Gets past strict firewalls | Best use |
|---|---|---|---|---|
| WireGuard | Fastest | Excellent | Sometimes blocked | Default for most people |
| OpenVPN UDP | Good | Fair | Sometimes blocked | Fallback if WireGuard fails |
| OpenVPN TCP (port 443) | Slower | Fair | Best | Hotels, offices, campus Wi-Fi |
| IKEv2 | Good | Excellent | Often blocked | Phones on the move |
Note what is missing: PPTP and L2TP without IPsec. PPTP has known weaknesses that have been publicly documented since the 2010s and should not be used for privacy. If an app still offers it, treat that as a warning sign about the service.
Which protocol to pick for each situation
For most people the answer is short. Use WireGuard unless something stops it from working.
- At home on a laptop or desktop. WireGuard. It is fast and stable, and the speed matters for large downloads and video calls.
- On your phone, moving around. WireGuard or IKEv2. Both survive the switch from Wi-Fi to mobile data without dropping your apps.
- On hotel, airport or office Wi-Fi that will not connect. OpenVPN TCP on port 443. That port is the same one used by normal secure websites, so networks rarely block it.
- On a router. WireGuard if your router supports it. Older router processors struggle with OpenVPN's overhead, and you may lose more than half your bandwidth.
If you travel often, our list of laptop security settings to turn on before you travel pairs well with setting a backup protocol in advance.
The "strongest encryption" advice is mostly beside the point
A lot of guides tell you to hunt for the protocol with the strongest encryption, usually pointing at AES-256 as the gold standard. That is not wrong, but it is not useful either. Every modern protocol listed above uses encryption that nobody is practically breaking. ChaCha20 in WireGuard and AES-256 in OpenVPN are both far stronger than the weakest link in your setup.
That weakest link is almost always somewhere else. A VPN without a working kill switch leaks your real traffic for a few seconds when the tunnel drops. A provider that logs your activity defeats the tunnel no matter which cipher it uses. DNS requests that bypass the tunnel reveal every site you visit. Spend your attention there first. Our explainer on what a VPN kill switch does and why it matters covers the setting that protects you when the connection hiccups.
How to check your protocol choice is working
Switching protocols takes about a minute. Here is a simple test you can run without any special tools.
- Measure speed. Run a speed test with the VPN off, then with each protocol on the same nearby server. Note download, upload and ping. A drop of 10 to 30 percent is normal. A drop of 60 percent or more suggests a protocol or server problem.
- Test switching. On your phone, start a voice call through a messaging app, then turn Wi-Fi off. With WireGuard or IKEv2 the call should keep going after a brief stutter.
- Check for leaks. Visit a DNS leak test page with the VPN on. Your DNS servers should belong to the VPN provider, not your internet provider.
- Leave it running. Use the protocol for a normal day. Any protocol that forces you to reconnect manually more than once is the wrong one for that network.
What a protocol cannot do for you
No protocol makes you anonymous. Websites can still identify you through logged-in accounts, cookies and browser fingerprinting. No protocol stops phishing pages or malware. And no protocol fixes a VPN provider that sells or hands over logs. If you are unsure what a VPN can realistically protect, read what a VPN actually does and what it does not before paying for extra features.
Frequently asked questions
Is WireGuard more secure than OpenVPN?
Both are considered secure when properly configured. WireGuard has a much smaller code base, which makes it easier to audit and reduces the chance of hidden bugs. OpenVPN has a longer track record and more configuration options. For most people, the security difference is not the deciding factor; speed and reliability are.
Should I use UDP or TCP for my VPN?
Use UDP by default because it is faster and handles streaming and calls better. Switch to TCP, ideally on port 443, only when a network blocks or keeps dropping UDP connections. TCP is slower because it retransmits lost packets inside an already reliable tunnel.
Which VPN protocol is fastest?
WireGuard is usually the fastest, often by a noticeable margin on phones and routers. Actual results depend on the server distance and load, so test two or three servers close to you. If speeds are still poor, the bottleneck is likely the server or your own connection rather than the protocol.
More in VPN Basics
VPN Basics
VPN vs Proxy vs Tor and Which One Fits the Job
A reader wrote to me in September after cancelling his VPN subscription.
VPN Basics
How to Run a VPN Leak Test for DNS, IP and WebRTC
A VPN app can show a green shield and the word "Connected" while your laptop quietly sends every website lookup to your...
VPN Basics
How to Choose a VPN Server Location for Each Task
You open the VPN app and it offers you 94 countries, a "fastest server" button and a map with glowing dots.