OpenVPN TCP vs UDP
Updated 21 September 2026 · How we research
OpenVPN can carry your tunnel over UDP or TCP. The choice is not about security — the encryption is identical — but about how the transport behaves when packets go missing.
The core difference
UDP sends packets and does not care whether they arrive. TCP guarantees delivery and order, retransmitting anything lost. Inside a VPN tunnel that guarantee becomes a liability, because the application inside the tunnel is usually TCP as well.
TCP-over-TCP meltdown
When to use each
Match the transport to the network you are on, not to a general preference.
| Situation | Use | Why |
|---|---|---|
| Home broadband, normal use | UDP | Lower latency and no double retransmission |
| Streaming or gaming | UDP | Latency and jitter matter more than perfect delivery |
| Hotel, airport or campus Wi-Fi that blocks UDP | TCP on 443 | Looks like ordinary HTTPS and is rarely filtered |
| Very lossy mobile connection | Test both | TCP may stabilise a broken link, or may make it far worse |
| Behind a strict corporate proxy | TCP on 443 | Often the only transport that reaches the internet at all |
Ports in practice
OpenVPN UDP commonly runs on port 1194. OpenVPN TCP is usually offered on 443, the HTTPS port, because almost every network must allow it. Running a VPN on 443 is not obfuscation on its own — deep packet inspection can still identify the OpenVPN handshake — but it defeats simple port blocking. For networks that inspect more deeply, see obfuscation.
How to test which is better for you
- Connect on UDP to the nearest server and note whether pages load promptly.
- Run the same check on TCP to the same server, so only the transport changes.
- Repeat at a time when the network is busy; TCP problems appear under load.
- Record what you observe rather than trusting a single measurement — see how to test a VPN.
According to ZoogVPN