Sending Files While Traveling on Public or Hotel Wi-Fi

October 11, 2026

Trying to send a file while traveling, hotel Wi-Fi, an airport lounge, a café, often feels harder than it should, and it's usually not for the reason people assume.

Why public Wi-Fi feels worse for this specific task

It's often not raw bandwidth, hotel Wi-Fi is frequently fine for browsing. The real issue is that many public networks are built around a captive portal and per-device isolation, meaning two devices on the "same" hotel Wi-Fi sometimes genuinely can't reach each other directly, even standing in the same room.

Why that isolation exists

Hotels and cafés deliberately isolate guest devices from one another as a security measure, so one guest's device can't snoop on another's traffic. A reasonable policy, that happens to also block the kind of local discovery some transfer tools rely on.

Where a relay-capable connection actually helps

This is the situation where a TURN relay would normally step in, and Nearsend does not run one. When a direct path between two isolated devices isn't possible, the transfer cannot start, and the fix is to move both devices onto the same ordinary network.

Practical tips for a flaky network specifically

Keep both devices' screens on and tabs in the foreground for the duration, background throttling compounds an already-shaky connection. If one device can switch to mobile data instead of the hotel Wi-Fi, that alone often resolves a stall caused by guest-network isolation.

When to just use mobile data on both ends

If a hotel or airport network is actively fighting you, two devices each on their own mobile data, sharing no network at all, is often more reliable than working around a shared network's restrictions.

Why hotel business centers and lobby Wi-Fi differ from your room's

It's worth noting that Wi-Fi quality inside a single hotel can vary meaningfully by location, a lobby or business center often has different, sometimes less restrictive, network configuration than guest room Wi-Fi, since it's frequently on a separate network segment intended for a different kind of use. If a transfer struggles in a hotel room specifically, trying from a lobby or common area is a genuinely different network worth testing, not just the same problem in a different spot.

Airport Wi-Fi has its own specific quirks

Airport networks add another layer worth knowing about: they're often heavily used by thousands of simultaneous travelers, and many airports route all guest traffic through a small number of shared gateways, which can introduce noticeable latency even when the connection itself seems stable. A transfer that's technically connected but unusually slow at an airport, more than a hotel, is frequently this shared-congestion effect rather than a sign anything is actually broken.

A habit worth building before you actually need it

Testing a transfer between your own devices before you're relying on it under time pressure, the night before a trip, on your home network, at least confirms the basics work, so that if it struggles on unfamiliar travel Wi-Fi later, you can be reasonably confident the network is the variable, not something else that changed at the same time.

Why this matters more for work travel specifically

For anyone traveling for work, where a deadline might genuinely depend on getting a file to a colleague or client while on the road, understanding this pattern in advance, expect guest-network isolation, have mobile data as backup, don't assume a bad connection means the tool is broken, turns a potentially stressful moment into a routine, anticipated inconvenience instead.