VPN for Public Wi-Fi: When You Actually Need One

Quick answer

Most public Wi-Fi is safer in 2026 than the warnings suggest, and the US Federal Trade Commission says so itself: because most websites now use encryption, "connecting through a public Wi-Fi network is usually safe." A VPN is genuinely worth using in four situations — an open network with no password, a network run by someone you would not trust with your traffic, work or account logins you do not want tied to your IP, and a network that blocks the sites you need. It is largely wasted money in four others, and it does not protect you from the risks that actually cause losses on café Wi-Fi: fake login pages, hostile hotspots, and unpatched devices.

Every VPN company on the internet sells the same picture: you sit down in a café, connect to the free Wi-Fi, and somewhere in that room a hooded figure is reading your bank balance off a laptop. It is a good story. It was even true around 2010, when most sites served their pages and login forms over plain HTTP and anyone on the same network could watch the traffic go by.

What changed is HTTPS. Nearly every site you actually use — banks, email, social platforms, shopping, this page — now encrypts the whole session, not just the login form. That makes the classic "guy in the café reads your password" attack mostly a historical problem. It also means most of what you are buying when you buy a VPN for public Wi-Fi is something other than what the marketing says.

I use a VPN on public networks regularly, and I still think this is worth writing down honestly: if you understand what the tunnel does and does not cover, you can decide per-network instead of paying a subscription to feel safe. Here is the actual picture, starting with the regulator's own position.

Is public Wi-Fi still dangerous, or has that advice expired?

Start with the Federal Trade Commission, which is not a VPN vendor and has no product to sell you. Its consumer guidance page on public Wi-Fi opens by noting that hotspots in coffee shops, malls, airports and hotels "often weren't secure" in the early days of the internet — and then says plainly that things have changed. The explanation it gives is specific:

"In the past, if you used a public Wi-Fi network to get online, your information was at risk. That's because most websites didn't use encryption to scramble the data and protect it from hackers snooping on the network. Today, most websites do use encryption to protect your information. Because of the widespread use of encryption, connecting through a public Wi-Fi network is usually safe."

That is the sentence the VPN industry does not quote. It is also the correct technical baseline for 2026. The old attack — passive sniffing of an unencrypted stream — requires an unencrypted stream, and unencrypted streams are now rare enough that browsers actively label them "Not secure" in the address bar. Chrome has done this since 2018. If you are on an HTTPS site and the padlock is real, another device on that network cannot read the page you loaded or the password you typed into it.

So the blanket advice "always use a VPN on public Wi-Fi" is out of date as a security statement. It is not out of date as a privacy statement, and it is not out of date as advice about which networks to trust — which is where the rest of this article lives.

What can someone on the same network actually see?

This is the part most articles skip, and it is the only way to answer the question honestly. Even with HTTPS everywhere, a person who controls or monitors the network can still observe:

What they cannot see, on a properly encrypted connection, is the content: the page, the message, the password, the form fields. So the honest summary is that unencrypted public Wi-Fi leaks metadata rather than content, and metadata is exactly what a VPN hides — because the only visible destination becomes the VPN server.

Whether that matters to you is a personal question, not a technical one. If you are checking a personal inbox on a café network, hiding the fact that you visited your mail provider from a stranger in the same room is a fairly small benefit. If you are a journalist, a clinician, or someone logging into a work system from a hotel, it is a real one.

When does a VPN on public Wi-Fi actually do something?

Four situations, and they are narrower than the ads imply.

1. The network has no password at all

An open network — no WPA2 or WPA3 key, just "connect and accept" — is one where the link layer itself is unencrypted. Everything above it still depends on HTTPS, but on an open network any device in range can join, and an attacker does not need to break into the router to sit on the same segment as you. This is the classic case. A VPN here does real work: it removes the metadata exposure described above and it means the local network sees a single encrypted stream to one server.

2. The network is run by someone with an interest in your traffic

A café's router is a coffee accessory. A hotel's, an airport's, or a conference venue's is often a managed service contracted out, sometimes badly secured, sometimes logging aggressively for "analytics." Treating a network as hostile by default — and a VPN is the practical way to do that — is reasonable when you did not choose the operator and cannot see their configuration. This is also the honest answer to "is hotel Wi-Fi safe": it is not that hotel networks are booby-trapped, it is that you have no way to audit one.

3. You are logging into something you would not want tied to that network

Work systems, admin panels, accounts that hold money, anything where the fact of the login is sensitive. A VPN does not make a weak password strong, but it does mean the local network cannot see which service you authenticated to, and it means the service sees your VPN exit rather than a hotel IP shared with every other guest.

4. The network blocks what you need, or throttles it

Plenty of public networks block ports, filter categories, or rate-limit video. This is a functionality problem rather than a security one, and a VPN solves it — which is also why some networks block VPN protocols outright. Worth knowing before you rely on it: if the network is hostile enough to block VPN traffic, you will find out quickly.

When is a VPN on public Wi-Fi a waste of money?

The mirror image, and this list is longer than the previous one for a reason.

1. You are only reading public pages

News, weather, a restaurant menu, a train timetable. There is no secret to protect, and the metadata you are hiding is the fact that you looked up the weather. Turning on a VPN for this costs you throughput and battery for nothing.

2. All your traffic is already HTTPS and you are not logging into anything

If the padlock is present and you are not authenticating, the tunnel is protecting metadata only. That is a legitimate privacy choice, and some people make it deliberately. It is not a security necessity, and it is not worth paying $10 a month for on its own.

3. You are on your own mobile hotspot

A hotspot you control is not a public network. The "public Wi-Fi" threat model does not apply to it, and adding a VPN on top just slows the connection down.

4. The VPN you would use is a free one of unclear origin

This is the one that actually causes harm. A VPN moves your trust. You stop trusting the café's router and start trusting the VPN operator instead, who now sees every domain you visit and every connection you make. If that operator is unknown, free, and funded by something you cannot identify, you have not improved your position — you have handed the same metadata to a party with a business model built on it. Our breakdown of how free VPNs actually make money goes through the specific mechanisms, and it is worth reading before installing one on a travel laptop.

What does a VPN not protect you from?

This is where the sales narrative breaks down most visibly. Five things people assume a VPN covers, which it does not:

Fake login pages. The FTC's guidance makes the point precisely: scammers "create fake websites and encrypt them to make you think they're safe when they're not. If you visit a scammer's website, your data may be encrypted on its way to the site, but it won't be safe from scammers operating the site." A VPN encrypts the trip to a malicious site. It does nothing about the site being malicious. Phishing is the most common way people actually lose accounts on public Wi-Fi, and a VPN is not a defence against it.

A hostile hotspot you chose to join. An "evil twin" network — a hotspot broadcasting the same name as the real one, run by someone nearby — gets you to connect to it voluntarily. Once you are on it, a VPN does encrypt your traffic, so the operator cannot read content. But if they serve you a portal page that looks like the hotel's login and you type your credentials into it, the VPN is irrelevant: you gave the password to the attacker directly.

An unpatched device. Encryption protects data in transit. It does not close an open port, patch a browser, or stop someone on the same network from probing your machine. On shared networks, the settings that matter are the boring ones: turn off file sharing and peer discovery, keep automatic updates on, and leave the firewall on. A VPN sits on top of those, not in place of them.

What the website itself does with your data. Once your request arrives at the destination, the VPN's job is over. Tracking scripts, account profiling and data resale all happen at the endpoint, where the tunnel does not reach.

Anything you do after you turn it off. Split tunnelling, a dropped connection, or simply forgetting to reconnect puts you back on the local network's view. This is what a kill switch exists for, and it is the one feature I would check before trusting any client.

Why does your VPN break the hotel login page, and how do you fix it?

This is the most common practical complaint about VPNs on public Wi-Fi, and it has a clear technical cause. A captive portal — the page that asks for a room number, an email, or a "I agree" click before granting internet access — works by intercepting your first request and redirecting it. That interception depends on seeing your plain HTTP request before it leaves the network.

If your VPN connects first, your traffic is already inside an encrypted tunnel to a server outside the network. The portal cannot intercept it, cannot serve its redirect, and the portal never appears. You end up with a VPN that says it is connected, a browser that loads nothing, and no obvious explanation.

The order that works: join the network, let the portal appear, complete the portal, confirm the internet works, and only then start the VPN. If the VPN client connects automatically on startup, turn that off for travel. On networks that re-prompt periodically — many hotels do, every few hours — you will need to disconnect the VPN, re-authenticate, and reconnect. That is normal behaviour, not a broken client.

How do you tell a VPN worth trusting from one that isn't?

If you have decided you want one for the four situations above, the selection question is less about protocol and more about who you are handing your metadata to. The FTC's own list of things to check before installing a VPN app is a decent starting filter: research the app before you obtain it, review what permissions it requests, confirm that it actually encrypts your information, and check whether it shares your data with third parties.

Translated into what I would actually look at:

Our 2026 VPN roundup compares the options I would actually consider on these criteria rather than on headline speed claims. And if a VPN makes your connection crawl, that is usually configuration rather than the provider — the causes of a slow VPN connection are worth ten minutes before you switch providers over a problem you can fix.

Which risks does a VPN actually stop, and which does it miss?

This is the whole argument in one table. "HTTPS" means ordinary encryption on the connection; "VPN" means a tunnel to a third-party server.

Risk on public Wi-Fi Real in 2026? Stopped by HTTPS? Stopped by VPN? What actually solves it
Someone reads your password off the network Rare — needs an unencrypted site Yes Yes Check the padlock and the exact domain before logging in
Someone sees which sites you visit Yes, on any network you don't control No Yes VPN, or DoH plus ECH where supported
You sign into a fake login page Yes — the most common real loss No No Type the address yourself; never log in from a link or portal
You join a hostile hotspot with a familiar name Yes, in busy venues Partly — content only Partly — content only Confirm the network name with staff; forget the network afterwards
Someone on the network attacks your device Low, but not zero No No Firewall on, file sharing off, OS and browser patched

Read the third and fourth columns together and the sales pitch falls apart: the risks that are most likely to cost you something are the two that neither HTTPS nor a VPN stops.

What should you actually do on a café or hotel network?

The order matters, mostly because of the portal problem above. Six steps, about a minute:

# Step Why
1 Confirm the network name with a human before joining Rules out the most common evil-twin setup
2 Complete the captive portal with no VPN running Portals cannot intercept traffic inside a tunnel
3 Turn off file sharing, AirDrop-style discovery, and "join known networks automatically" Reduces what other devices can see and reach
4 Start the VPN, if this network meets one of the four criteria Hides destinations and metadata for the rest of the session
5 Navigate to banking and email by typing the address, not by following a link Phishing is the risk a VPN cannot touch
6 Forget the network when you leave Stops the device auto-joining a same-named hotspot later

If you skip steps 1, 3 and 5 and buy a VPN instead, you have spent money on the one layer that was already covered.

Our position: a VPN is a good tool with an oversold use case. On public Wi-Fi it reliably hides where you go and who you talk to, which is a real privacy benefit for some people and close to worthless for others. What it does not do is stop the attacks that actually separate people from their accounts — fake portals, familiar-looking hotspots, and unpatched software. Buy one if you handle sensitive logins on networks you did not choose; skip it for reading the news at a café and spend the ten minutes on settings that matter more.

How We Put This Together

The regulatory position quoted here — that public Wi-Fi is "usually safe" because most websites now use encryption, and that scammers encrypt fake sites so the connection is safe while the site is not — comes from the US Federal Trade Commission's consumer guidance page "Are Public Wi-Fi Networks Safe? What You Need To Know," published February 2023 and still the FTC's current public-Wi-Fi advice as of November 2026. The VPN-app selection criteria (research the app, review permissions, confirm encryption, check third-party data sharing) come from the FTC's 2018 guidance on VPN apps. The technical descriptions — what the TLS handshake exposes, DNS visibility, captive-portal interception, and what encryption does not cover — are standard networking behaviour rather than vendor claims, and the captive-portal order-of-operations was confirmed against how portals redirect requests before a tunnel exists. This article deliberately contains no measured speed figures or failure-rate statistics, because I did not test those and would rather leave them out than estimate them. Where this article disagrees with VPN marketing, the disagreement is stated as an editorial position, not as a finding.

Frequently asked questions

Is it safe to check email on public Wi-Fi?

Usually yes. Webmail and mail apps use HTTPS, so other devices on the network cannot read the content of the connection. The FTC's own position is that public Wi-Fi is usually safe now because most sites encrypt. The realistic risk is not someone reading your mail but you logging into a convincing fake page — a phishing problem, not a Wi-Fi problem.

Can someone see my password on public Wi-Fi?

Not over HTTPS — the password is encrypted in transit. Someone on the network can typically see which domains you connected to and the timing and volume of that traffic, but not what you typed. The exception that matters is signing into an unencrypted site, or being redirected to a fake login page by a hostile network. Check the padlock and the exact domain before typing a password.

Do I need a VPN on hotel Wi-Fi?

Not for encryption alone if you stay on HTTPS sites. Hotel and airport networks deserve more suspicion than a café's because they are often run by a contractor, collect an email or room number at the portal, and are a common venue for credential-harvesting pages. A VPN is reasonable there if you handle work data or log into accounts you would not want tied to that network. For reading news and checking a personal inbox, HTTPS is already doing most of the work.

Is a free VPN good enough for public Wi-Fi?

Technically it encrypts the tunnel, which is the part that matters for metadata. The problem is how a free VPN is funded — bandwidth and servers cost money, so the revenue comes from somewhere: ad injection, traffic logs, or making you an exit node. The FTC's guidance is to research the app, review its permissions, confirm encryption, and check whether it shares data with third parties. A free tier from a reputable paid provider is usually a better bet than an unfamiliar free product.

Can a VPN stop someone from hacking my device on the same network?

No. A VPN encrypts traffic leaving your device; it does not close ports, patch software, or stop another machine from probing yours. On a shared network, the protections that matter are the ones people skip: turn off file sharing and peer discovery, keep the OS and browser patched, and leave the firewall on. A VPN adds to those — it does not replace them.

Next: if you are choosing a provider rather than deciding whether to use one, the 2026 VPN comparison covers the options worth paying for. For the no-account route, how Mullvad signup works without an email explains a model where you never hand over an identity in the first place. And if a free plan is what you have in mind, what Windscribe's 10 GB free tier actually covers is the realistic version of that decision.

Get more guides like this

Free tools, VPNs and realistic side income — tested hands-on, delivered weekly.

Subscribe free