A hotel can advertise fast Wi-Fi, deliver exactly the speed it promised, and still make a 4K stream stutter on purpose.
That's the part nobody believes when I bring it up. Most people assume "slow hotel Wi-Fi" just means a weak signal or too many guests sharing one router, and that a travel VPN exists purely to get around regional blocks on streaming apps. It does that too — but for anyone doing the digital-nomad shuffle between flats and hotel rooms, the more useful trick is figuring out which problem you're actually looking at before trying to fix it.
Why Streaming Gets Singled Out on Hotel Networks
Run a speed test in most hotel rooms and the number on screen looks perfectly reasonable. Thirty megabits down is plenty for a crisp picture — Netflix only asks for about 15 Mbps to deliver its 4K catalogue, and YouTube wants roughly 20 Mbps for Ultra HD. On paper there's headroom to spare. Then the stream crawls anyway, drops to a soft 480p, and sits there looking like it was filmed through a dirty window (the kind of picture you'd expect from a connection running on fumes, except the fumes were never actually the problem).
What's actually happening has nothing to do with the number the speed test reported. A lot of hotel networks run Deep Packet Inspection on everything passing through the router, sorting traffic by what it looks like rather than how much of it there is. It works a bit like an airport scanner that doesn't weigh your bag, just notices the shape of what's inside it. Anything shaped like a video stream gets waved into a slower lane, on purpose, no matter how much bandwidth is sitting unused elsewhere on the network. That's throttling, and it's aimed specifically at video, not at your connection as a whole. Open a document, check email, load a map, and the same "slow" Wi-Fi behaves perfectly normally. Open Netflix or iPlayer on that exact same router, and suddenly it can't cope.
Does a VPN Actually Make a Slow Connection Worse?
Most advice about VPNs and weak Wi-Fi says to turn the VPN off, and most of the time that's the right call. Wrapping every packet in AES-256 encryption adds overhead, an extra layer the data has to pass through on both ends, which costs some speed and some latency. On a connection that's genuinely struggling for other reasons, that extra layer can be what tips a wobbly stream into no stream at all.
But when the thing killing your stream is deliberate sorting rather than genuine weakness, that same encryption stops being a cost and turns into the fix. Once the data is wrapped, the router sorting traffic by shape can't tell a 4K documentary from a work backup syncing to a cloud drive — it just sees encrypted noise, and encrypted noise doesn't get sorted into the slow lane. The bandwidth was there the whole time. The VPN doesn't create speed out of nowhere, it just stops the hotel deciding you're not allowed to use what you're already paying for.
The clearest proof of this showed up in an Airbnb in Príncipe Real, in Lisbon, where the BBC Two ident rendered crisp and full-resolution within about two seconds of pressing play. No spinning wheel, no drop to a blurry frame first, nothing. Same building, same router, same "slow" Wi-Fi the night before.
Setting Up for a Stable 4K Stream
I tried skipping the VPN altogether once and used a Smart DNS service instead. It worked fine on BBC iPlayer for a couple of weeks, then stopped overnight with no warning and no error message, just a blank screen where the stream used to load (no explanation, just gone). It's a different tool for a different job, and it does nothing for throttling, because it was never built to disguise what you're streaming — a VPN hides the shape of the traffic; a DNS swap just tells the stream a different story about where you are.
A few practical things matter once you know what you're actually fixing. If beating throttling is the goal, connect to the VPN server that's physically closest to you rather than the one that would normally spoof your home country. Try Lisbon to a Lisbon or Madrid server, Bangkok to a Bangkok or Singapore one. Shorter distance means less latency stacked on top of the encryption overhead, so there's only one problem to fight instead of two. That's a different rule from the one you'd follow for region-locked content, where you want a server in a specific country rather than the nearest one, and mixing the two up is probably the single most common reason people give up on a VPN too early.
My friend Sorcha, who does the same city-hopping thing for her own work, left me a voice note well past eleven one night about this exact mix-up — the kind of message that really could have been a two-line text. She'd been connected to a UK server from a flat with perfectly adequate Wi-Fi, wondering why 4K wouldn't hold, and switching to the nearest server instead fixed it in under a minute.
The same confusion shows up when a VPN appears to stop working entirely rather than just running slow, except that's usually a block on the streaming side, not throttling on the hotel's side, and the two need completely different fixes. I've been through the late-night University Challenge crisis often enough to know the answer is almost never "get a new VPN" but rather "change which server you're pointed at."
Sometimes the bottleneck isn't the network at all, it's the television. A lot of hotel smart TVs are underpowered and run VPN apps badly, if they run them at all (hotel electronics budgets clearly don't stretch to a decent processor), which is why I travel with a streaming stick that handles the VPN itself instead of trusting the TV's own software. I've put the full setup into a practical guide to VPN workarounds for hotel TVs, because it's too much detail to repeat here, but the short version is that a dedicated device beats fighting a five-year-old TV's menu system every single time.
Protocol settings help too. Most VPN apps bury a choice of a couple of different protocols in their settings, and switching to WireGuard specifically tends to claw back some of the overhead encryption adds in the first place. It's a lighter way of wrapping the same data. Pair a nearby server with the lighter protocol and the overhead shrinks small enough that it stops mattering against a throttled connection.
What Actually Fixes It, and What Doesn't
A reader named Saoirse wrote in a while back, certain her VPN had simply broken after she moved to Tokyo for a teaching contract and lost access to ITVX overnight. It hadn't broken. She just needed a different server for a different kind of block, and she still checks back every few months to confirm the fix is holding, which it always has been (she's thorough like that). That's really the whole correction in one story: a VPN that seems slow, broken, or useless is usually just solving the wrong problem for the situation you're actually in. Work out whether you're fighting a block or a throttle, point the server at the right target for that specific fight, and the "rubbish hotel Wi-Fi" usually turns out to have been fine all along.