VPNs and cloud gaming — a counterpoint to the easy advice

Standard cloud gaming guidance: turn your VPN off when using cloud services. The VPN adds latency, breaks the geo-routing the cloud service uses to assign you to the nearest data centre, and can trigger anti-fraud detection that interferes with payment or matchmaking.

The advice is correct for the median user. If you're playing GeForce Now from your home network, your VPN is making things worse.

Hotel and public WiFi. Many hotel networks throttle UDP traffic, which is what cloud gaming uses. A VPN that tunnels UDP over a TCP connection can sometimes improve cloud gaming reliability on bad networks. The latency cost is more than offset by the reliability gain.

ISP traffic shaping. Some ISPs throttle cloud gaming traffic identifying it as 'streaming video' (which gets deprioritised behind other traffic during peak hours). A VPN can sometimes mask the traffic shape and avoid the throttling. Comcast and AT&T have both been observed doing this; Verizon less so.

Specific regional issues. Cloud services in some markets route through congested transit links that VPNs can bypass. A user in India connecting to Singapore-based cloud servers may get better path through a VPN that exits in Singapore versus the default ISP routing.

Geo-arbitrage. Using a VPN to pretend you're in a cheaper-priced region (Brazilian GeForce Now, Indian Game Pass) is against the cloud services' terms of service. The detection is getting better and accounts have been suspended for this. We don't recommend it.

Triggering anti-fraud detection on payment. If you sign up for a cloud service through a VPN, the payment processor may flag the transaction as fraudulent. The account creation friction is real.

Matchmaking confusion in competitive games. VPN routing can put you on game servers far from your actual location, which produces worse latency to the in-game matchmaking server. This is invisible from the cloud service's perspective but visible in the game performance.

Home network, residential ISP, no specific reason to use VPN: don't use VPN with cloud gaming. Standard advice applies.

Hotel network, conference WiFi, sketchy public networks: try with and without VPN. Whichever performs better on the specific network is the right answer for that session. Don't assume the conventional advice transfers.

Suspected ISP throttling: experiment. Try a VPN at peak hours and see if cloud gaming quality changes. If it does, the ISP is the problem and the VPN is the workaround.

Wireguard-based VPNs perform better than OpenVPN for cloud gaming because the protocol overhead is lower. Mullvad, Tailscale, and ProtonVPN's WireGuard mode are well-suited.

Avoid free VPNs entirely. The performance is bad, the trust posture is worse, and the cloud services flag traffic from free VPN providers more aggressively.

Don't run the VPN client on the same device as the cloud client if you can avoid it. Running VPN at the router level is cleaner because it doesn't compete for CPU with the cloud gaming client.

Cloud services prefer to optimise for the home-residential-no-VPN baseline and treat everyone else as edge cases. The engineering work to handle VPN-routed sessions cleanly is real and the audience is small.

The geo-arbitrage concern is also real. Cloud services don't want to publish guidance like 'VPN is fine for these legitimate uses' because that creates legal complications for enforcing the arbitrage prohibition.

Result: the cloud services' official position is 'don't use VPN'. The practical reality is 'sometimes you should'. The guidance from the services papers over the more interesting situation.