Two laptops on the same conference-room Wi-Fi. A phone and a desktop on the same home router. “Same network” sounds like it should be the easy case for moving a file — no internet round trip needed, both devices are right there. In practice it’s often the case where sharing tools break in the most confusing way: the devices are visibly on the same SSID, and AirDrop still can’t find the other one, or Windows’ Nearby Sharing sits there searching forever.
Why “same Wi-Fi” doesn’t mean “can see each other”
AirDrop, Nearby Share, and Windows’ Nearby Sharing all work the same underlying way: each device broadcasts itself on the local network so the other can discover it, then negotiates a connection directly. That broadcast step is the part that breaks. Office networks, school Wi-Fi, hotel and café guest networks, and even some home routers’ guest mode enable a setting called client (or AP) isolation, which stops connected devices from talking to each other directly — on purpose, as a security measure so one guest can’t poke at another guest’s laptop. The discovery broadcast never arrives, so the two devices never see each other, even though both show the same network name in their Wi-Fi settings.
Mixed-platform pairs make it worse before isolation even enters the picture: AirDrop only discovers other Apple devices, and Nearby Share only discovers other Android devices, so an iPhone and a Windows laptop were never going to find each other locally no matter how the network is configured.
Pairing doesn’t depend on local discovery
FileTransferX sidesteps the broadcast step entirely. Instead of the two devices finding each other on the network, the sending device generates a short-lived transfer code and matching QR code, and you hand that code to the receiving device yourself — by showing the screen, reading it aloud, or letting it scan the QR image. Nothing about that pairing step depends on the local network allowing devices to see one another; it works the same whether isolation is switched on or off, because the two devices are being introduced by you, not by a broadcast.
Once paired, FileTransferX attempts a direct connection between the two browsers. If the network blocks that — the same isolation setting that broke AirDrop can also block a direct path here — it automatically falls back to an encrypted relay, so the transfer still completes. You can read more about that fallback on the security page.
To send a file this way:
- On the device with the file, open filetransferx.com and choose Send Files.
- Select the file, or files, to send.
- On the second device, open filetransferx.com and choose Receive Files.
- Scan the QR code, or type the short transfer code shown on the sending device.
- Accept the incoming files to start the transfer.
There’s no shared folder to set up, no matching OS requirement, and no permissions dialog to get through first.
When being on the same network actually helps
Most home routers don’t enable client isolation by default, so on a typical home network a direct connection between two devices can route straight across the router itself rather than out to the internet and back. That matters most for large files on a slow upload connection: a transfer that never has to travel further than your own router isn’t bottlenecked by your ISP’s upload speed the way an internet-routed transfer would be. The pairing step takes the same few seconds either way — it’s the data itself that benefits from staying local.
Common situations this fits
Handing a slide deck to whoever’s laptop is plugged into the conference room projector. Getting a document to the computer connected to the office printer. Moving a photo between two family members’ phones at home without anyone digging up an email address. A short code is also just easier to communicate in person than an email address — read it out, or hold the QR code up to a camera, and the other person is receiving within seconds. It works the same way in a shared coworking space, where you’re on the building’s Wi-Fi alongside people from other companies and would rather not rely on a network file share that a stranger’s laptop might also be able to see.
If pairing seems stuck
Transfer codes are single-use and short-lived by design — once a code has been used to pair a session, or it’s gone unused for a few minutes, it stops working. If a code doesn’t seem to be accepted, the fix is almost always to go back to the sending device and start a fresh Send Files session for a new one, rather than continuing to retry an expired code. Both devices also need a reasonably recent version of Chrome, Edge, Firefox, or Safari; there’s nothing to install, but very old browser versions can lack the features a direct connection relies on.
Sharing the Wi-Fi password itself
There’s a related, smaller problem worth mentioning: getting someone onto the network in the first place, before you can even get to the file. Reading a Wi-Fi password out character by character, or scrawling it on a whiteboard, is its own minor friction point in an office or classroom. FileTransferX’s companion tool, Transfer Text, pairs the same way — QR code or short code — but sends a short message instead of a file, so a password, a guest-network name, or a one-time code can be beamed to the new device instead of typed in. It’s the same pairing mechanism this guide already covers, just for text.
It isn’t limited to one network
None of the above is a requirement — it’s just where FileTransferX happens to work especially well. The exact same five steps pair two devices on completely different Wi-Fi networks, different mobile carriers, or different cities, with no setting to change between the two cases. See the how it works page for what happens on the connection side of a transfer between devices that aren’t sharing a network at all.