Sending files between devices on different networks
Almost every quick file-transfer tool has the same footnote: both devices must be on the same Wi-Fi. That is fine at home. It falls apart the moment your phone is on mobile data, your laptop is on a café network, or you are on an office Wi-Fi that isolates clients from each other.
This page explains why that limitation exists, and what to do when it applies to you.
Why most tools need the same Wi-Fi
The fast browser-based tools work by having your two devices talk to each other directly, over the local network, without a server in the middle. That is what makes them quick and private — the file never leaves your house.
It is also exactly what breaks. Direct device-to-device connections need the two devices to be able to see each other, and that requires:
The same network. Different networks means no shared address space.
Client isolation switched off. Most public, hotel, and corporate Wi-Fi turns it on deliberately, so devices on the network cannot reach each other. This is why these tools so often fail on office Wi-Fi even when both devices are genuinely on it.
A firewall that permits it. Corporate laptops frequently do not.
So “same Wi-Fi” is really “same Wi-Fi, and that Wi-Fi has to allow it” — which is why the tools feel unreliable rather than simply limited.
What works across different networks
A relay-based browser tool
Instead of connecting the devices directly, the file goes up to a server and comes back down on the other side. You lose the “never leaves my house” property and you are bounded by your upload speed. In exchange, it works from anywhere to anywhere.
Mubifiles works this way. Open the site on both devices, share a six-digit code, send. The two devices never need to see each other. Files are deleted when the session closes.
PairDrop public rooms or pairing
PairDrop, the successor to Snapdrop, crosses networks two ways. A temporary public room needs no setup at all: enter a five-letter code on both devices and they connect over the internet, with a TURN server bridging NAT automatically. Persistent pairing does the same for devices you use together often.
Transfers stay peer-to-peer, which means no third party stores your file and there is no hard size limit — but it also means both devices have to be online at the same moment, with both tabs open.
Cloud storage
Google Drive, Dropbox, OneDrive. Reliable and universal, but heavier: upload, wait, switch device, find the file, download, and then remember to delete it. Good for things you want to keep. Overkill for a screenshot.
Messaging yourself
Works everywhere, but compresses images and video, and permanently clutters a chat you use for other things.
What does not work across networks
Worth being direct about these so you do not waste time:
LocalSend — same local network, by design
Snapdrop / ShareDrop — same, and the original Snapdrop domain has changed hands and is no longer the project people remember
Quick Share / Nearby Share — proximity-based
AirDrop — proximity-based
KDE Connect — same network unless you configure your own relay
Bluetooth — proximity, and slow
If you are on the same reliable network, prefer one of these. Local transfer beats anything routed through the internet on both speed and privacy.
A practical rule
Same trusted Wi-Fi, large file LocalSend
Same Wi-Fi but it’s public or corporate and the tools keep failing use a relay-based tool instead; client isolation is fighting you
Different networks, one-off Mubifiles, or a PairDrop public room
Different networks, both devices online together, large file PairDrop — peer-to-peer, no size cap
Different networks, sender and receiver at different times Mubifiles — the file waits in storage
You want to keep the file long-term cloud storage
Frequently asked questions
- Can I send a file from mobile data to a computer on Wi-Fi?
- Yes, with a relay-based tool. Open the site on both, share the code, send. The devices do not need to be on the same network.
- Why does Snapdrop or LocalSend fail on my office Wi-Fi?
- Most likely client isolation. The network deliberately prevents devices on it from seeing each other, which is exactly what those tools depend on.
- Is a relay slower than a direct transfer?
- Usually, yes. Your file travels up and then back down, so your upload speed sets the pace. On a fast connection with a small file the difference is not noticeable.
- Is it safe to send files through a server?
- It depends on the service. With Mubifiles, the session code is random and short-lived, access requires a private token issued when you join, and files are deleted when the session closes. For anything highly sensitive, use the one-time download option.
- How large a file can I send?
- Up to 1 GB per file and 3 GB per session. It is still a ceiling the alternatives do not have: PairDrop transfers peer-to-peer and imposes no hard size cap, and LocalSend has none either. For a file past a gigabyte, use LocalSend on a shared network or PairDrop across networks.
Try it across your own two networks
Open mubifiles.com on both devices.
Start a session →