Hotels enable AP isolation on their networks for security - which also breaks AirDrop, LocalSend, PairDrop, Quick Share, and almost every other file-sharing tool that assumes devices can see each other on the same network. Here's the workaround.
What breaks on hotel WiFi
AirDrop
AWDL needs peer WiFi visibility. AP isolation breaks discovery. Sometimes falls back to Bluetooth, often unreliably.
LocalSend
mDNS multicast is blocked at the access point. Devices won't see each other.
PairDrop / Snapdrop
WebRTC peer-to-peer handshake fails. May show both devices but the transfer won't start.
Quick Share / Nearby
Same WiFi/Bluetooth discovery problem. Cross-vendor support is also fragile.
Bluetooth file transfer
Slow, often capped at small files, painful pairing flow, varies by platform.
Email / cloud upload
Works, but you log in everywhere, the file persists on a server, attachment limits cap you at ~25 MB.
Why this happens: AP isolation
Hotel access points - and many corporate, guest, and public WiFi networks - enable a setting called AP isolation. Each client can reach the internet, but not other clients on the same network. The router treats every device as if it's on its own private network.
This is good security: one guest can't sniff or attack another guest's traffic. It also breaks every file-sharing tool that assumes devices can see each other locally. mDNS, WebRTC, Bluetooth-over-IP, and AirDrop's WiFi peer-to-peer all rely on direct device-to-device visibility - which AP isolation explicitly removes.
There's nothing you can do about it from the client side. The hotel controls the router. The only workaround is to not need device-to-device visibility.
chirpfile's approach: the network never bridges the two devices
The file is encrypted in your browser. The encrypted blob goes over regular HTTPS to a relay - just like any web request. Hotel WiFi blocks peer connections, not HTTPS, so the upload works.
The decryption key, which the relay never sees, travels between the two devices as sound. Your laptop plays a 1-2 second chirp; your phone hears it through its microphone and decodes the key. No network is involved in that step. The hotel WiFi cannot block sound waves.
This means: phone on cellular + laptop on hotel WiFi works. Two devices on the same locked-down hotel WiFi works. Laptop on hotel WiFi + tablet on a different hotel's WiFi works. As long as both devices can load a webpage and hear each other, the transfer succeeds.
Specific scenarios that work
Send a document to a colleague's laptop
Same room, hotel lobby or meeting space. Both on hotel WiFi. Drop the file in your browser, your colleague hears the chirp, file appears on their browser.
Share a deck with a stranger at a conference
No need to exchange emails, AirDrop addresses, or pair anything. They open the page on their device, you chirp.
Send WiFi password to a guest's phone
Under 120 characters - bypasses the relay entirely. Pure sound, no internet needed for the password itself.
Hand off a contract during a meeting
Encrypted in your browser before upload. Server never sees the contents. Burned after first download.
Move a screenshot from phone to laptop in a coffee shop
Coffee shop WiFi often has AP isolation. Doesn't matter - chirpfile doesn't use device-to-device WiFi.
Try it now
Open chirpfile.com on both devices. No app, no account, no shared network needed.
Does chirpfile work if the hotel WiFi blocks UDP / WebRTC?
Yes. chirpfile uses regular HTTPS - the same path as a web search or email. Hotels block peer-to-peer protocols, not HTTPS. Web traffic always works.
What if my phone is on cellular instead of hotel WiFi?
That's fine - even better in some ways. The phone doesn't need to be on the same network as the laptop. Each device just needs its own internet path. The chirp handles the cross-device coordination.
Is the file actually encrypted? The relay doesn't see it?
Yes. AES-128-GCM in your browser before upload. The key is generated locally and transmitted via sound, never via network. There's a real-time audit panel at the bottom of every chirpfile page that lets you verify this - you can see every byte that leaves your browser.
What if hotel WiFi is too slow for a large file?
Bandwidth is what it is - chirpfile can't speed up a slow hotel connection. But you can send the file from a faster connection (cellular tethering) and have the recipient download on hotel WiFi, or vice versa. The two devices don't need matching bandwidth.
What about hotel WiFi captive portals?
Once you've signed in via the captive portal and have internet access, chirpfile works the same as on any other network. The portal doesn't affect chirpfile after you've authenticated.