VPN for travel: a ten-minute checklist
Set up your VPN before you leave, turn on Always-on, pick a nearby server and know what to do on hotel Wi-Fi. A ten-minute checklist for Android.
Ten minutes before a trip covers everything a VPN needs: install and connect once at home, turn on Always-on VPN so it survives reboots, know how you will pick a server when you arrive, and know what to do the first time hotel Wi-Fi shows a terms page. Done in that order, the app then looks after itself for the whole trip, and the only decision left is which city to connect to.
Before you leave
- Install the app and connect once. Android asks you to approve the VPN connection request the first time. Do this on a connection you trust, so a problem is a setup problem and not a hotel problem. It takes about two minutes.
- Turn on Always-on VPN. In Android's settings under Network, VPN, tap the gear next to the app and enable Always-on. The tunnel now comes back after every reboot and every network change without you remembering it. Always-on VPN on Android shows the screen.
- Decide about "Block connections without VPN". On the same screen. With it on, nothing leaves the phone when the tunnel is down, which is what you want on untrusted Wi-Fi; it also means a captive-portal page cannot load until you briefly allow it. Know it is there, and know where to turn it off for a minute.
- Exclude the apps that dislike VPNs. A banking app that refuses to work behind a VPN, or a local transport app that wants your real location, can be added to the split-tunnel exclude list rather than forcing the whole VPN off. Banking and local transport apps are the usual candidates.
- Make sure the app can stay alive. Some phones close background apps aggressively. Exempt the VPN from battery optimisation in Android's app settings so it is not killed mid-trip.
- Sort your data. If you are using a travel eSIM, install and test it now. VPN and eSIM explains why the two are separate jobs and why you probably want both.
- If you are on Premium, check the email works. Signing in with it is how the subscription comes back if the phone is lost or replaced abroad.
On arrival: choosing a server
Every packet makes a round trip to the VPN server, so distance is latency. A server in the city you are in, or the nearest one, is usually the right default for speed. Culvert VPN's picker shows each city with the round trip measured from your phone at that moment, and a headroom figure, so you can choose by number: the lowest latency with headroom to spare. How to choose a location goes through reading the list, and tapping a country connects to its quickest healthy city if you would rather not choose.
There are two reasons to pick a server farther away. A service at home that challenges logins from an unfamiliar country will settle down if your exit address is one it is used to. And a network where the nearest city is heavily loaded may be quicker through a city one hop further with more headroom, which is what the headroom figure is there to tell you.
The hotel Wi-Fi routine
| What you see | What it means | What to do |
|---|---|---|
| Wi-Fi connected, VPN stuck connecting | A captive portal is holding traffic until you accept terms | Open the browser, accept the terms, then let the VPN retry |
| VPN connects, then drops after a few seconds | The network filters the protocol the app tried first | Wait; an app that tries several methods will switch to one on TCP port 443 |
| VPN connected, sites will not load | The tunnel is up but something is wrong with routing or DNS | Disconnect and reconnect; if it persists, try another city |
| Everything works, then stops at midnight | The Wi-Fi's own session expired | Re-accept the portal; the VPN comes back on its own |
Using a VPN on hotel Wi-Fi goes through each of these in more depth, including why a VPN cannot see the terms page for you.
Roaming and mobile data
If you are on your home plan's roaming, mobile data is your own connection and nobody else shares it, which makes it safer than any hotel Wi-Fi even before the VPN. The VPN still earns its place: it hides your destinations from the roaming carrier and gives you a chosen exit address. The cost is a small overhead on metered data, a few percent per packet, which matters only on a very small allowance.
Switching between Wi-Fi and mobile data is where a VPN app shows its quality. Modern protocols reconnect in under a second on a network change, and Always-on ensures the tunnel comes back rather than leaving the phone on the raw connection.
Every day of the trip
- Glance at the key icon in the status bar before doing anything you care about on Wi-Fi.
- Check the exit IP on the connect screen once after connecting; it should belong to the city you picked.
- If the app says connected and nothing loads, reconnect before blaming the hotel.
- Leave Always-on enabled until you are home.
Culvert VPN does the parts of this list that can be automated, trying several connection methods on each network and keeping the one that works, showing every city's live latency from your phone, and verifying the exit address through the tunnel, on Google Play.
Questions people also ask
Should I connect to a server near home or near where I am?
Near where you are for speed, since every packet makes a round trip to the server. Near home if a service you rely on reacts badly to a login from an unfamiliar country. The app's per-city latency figure tells you what each costs.
What if the hotel Wi-Fi will not let the VPN connect?
Accept the Wi-Fi's terms page first; a VPN cannot connect through a captive portal. If it still fails, the network may be filtering VPN protocols, and an app that tries several methods will usually find one on TCP port 443.
Is mobile data safer than hotel Wi-Fi?
Generally yes, because nobody else is on your connection. A VPN on top covers both, so the choice becomes about data allowance and signal rather than safety.