PairDrop Alternative for Transfers Beyond the Local Network

Step by step

1. Open Rapidfile on the sending device

   Go to rapidfile.cc in any browser, or open the Rapidfile app on Android. No account is needed for files up to 500 MB.

2. Add your files

   Drop files or a whole folder onto the uploader on a computer, or tap to pick them on a phone. Folders are zipped in the browser with their structure kept.

3. Choose the options

   Pick an expiry time from 1 hour to 7 days on the free plan, and optionally add a password or a download limit.

4. Share the link, code or QR code

   Send the link, read out the 6-digit code, or show the QR code. The receiver types the code at rapidfile.cc/receive, or scans the QR code.

PairDrop is a free, browser-based way to move files between phones, tablets and computers. It began as a fork of Snapdrop, the project that made local browser sharing popular, and it is open source under the GPL-3.0 license. You open the page on two devices, let them find each other or pair them, and send. No app and no account are needed. People look for an alternative for a few reasons: the devices are on different networks, a hotel or office Wi-Fi keeps them from seeing each other, or the other person wants the file tomorrow rather than now.

The short version

PairDrop figures come from its website and FAQ as of October 2026. Plans and features change, so check their site before you decide.

Sending a file with each tool

With PairDrop, open the page on both devices. If they share a network, they appear on each other's screen; select the device, choose your file, and accept on the other side. For devices you use often, pair them once and they keep finding each other. The transfer runs while both pages stay open.

With Rapidfile, open rapidfile.cc on the sending device and drop in your file. When the upload finishes you get a link, a 6-digit code and a QR code. The receiver can use any of them, at any time before the link expires, without needing your device to be online.

Where PairDrop is the stronger pick

• Speed on a shared network. A direct transfer skips the upload step. When two phones sit on the same fast Wi-Fi, the file moves in one pass and does not wait on a server.
• Nothing kept afterwards. The PairDrop FAQ says files are sent directly between peers and that the project does not use a database. For a direct transfer, there is no stored copy to expire or delete.
• Pairing for your own devices. Pair your phone and laptop once with a code or QR code, and they find each other again without typing anything. For regular moves between your own devices, that is convenient.
• Open source and self-hosting. The code is under GPL-3.0, and the project supports running your own instance. If you want full control of the server, PairDrop offers that and Rapidfile does not.

Where Rapidfile fits better

• Different networks. Pairing and rooms need both devices to be reachable. If one person is on mobile data and the other is at the office, a Rapidfile link works without anyone sharing a Wi-Fi network. The receiver can type the code at rapidfile.cc/receive.
• The receiver is not online yet. Rapidfile keeps the upload until it expires, so the other person can download tomorrow, from another city, on any device with a browser.
• Restricted networks. Guest, hotel and school Wi-Fi often isolates devices. Rapidfile needs only an internet connection on each end.
• Sharing with a group or with limits. One link can go to several people, a download limit can stop it after a set number of downloads, and a password can be added. See password-protected file sharing.
• Bigger files on the free plan. The free account allows 2 GB per transfer. Compare that with PairDrop's own limit on its site before you decide.
• Scanning. Every upload is scanned with ClamAV, an open-source virus scanner. Flagged files show a warning and a "Download anyway" option.

How PairDrop connects, and what that means for privacy

PairDrop uses three ways to connect, as described in its FAQ and project documentation. On the same local network, devices find each other and the file goes straight between the browsers. Paired devices are remembered, so they can reconnect later. Public rooms use a short code or QR code, and every device in the room sees the others.

When devices sit behind routers that block direct connections, the FAQ says the PairDrop TURN server routes the files and messages. The transfer is still encrypted in transit by WebRTC, but the data passes through PairDrop's relay instead of going device to device. That is a different trust position from a direct transfer, and it is worth knowing before you send something sensitive.

Rapidfile's position is different. Files are encrypted in transit with TLS and at rest on Cloudflare's network, and they are deleted at expiry. Rapidfile is not end-to-end encrypted, so it should not be treated as a vault. For a direct transfer on a home network, PairDrop has the stronger story because nothing is stored. For a file that must reach someone elsewhere, the choice comes down to whether the receiver can be reached at the same time as you.

Sending to several people

PairDrop's public rooms are built for a small group in one place, such as a workshop or a meeting, where everyone's device should appear in the same list. Each device in the room sees the others, so the sender can pick the right one. That works well while everyone is present and their pages are open.

Rapidfile suits the same group in a different way. Post one QR code on a screen or print one 6-digit code on a whiteboard, and anyone who scans or types it gets the same file. The receivers do not need to be in the same room or open at the same moment, and a download limit can cap how many copies go out. If the file is for a team that will not all arrive at once, a stored link is simpler than a live room.

Live transfers and stored uploads

The biggest practical difference is what happens when a connection drops. A PairDrop transfer is live: it runs while both pages are open, and if either side closes its tab or the screen goes to sleep, the transfer stops and must be started again. A Rapidfile upload is stored on the server once it finishes, so the sender can close the tab, and the receiver downloads from the link whenever they like.

For a quick move between two devices that are sitting side by side, a live transfer is the right tool. For a file that must reach someone on a different schedule, a stored link removes the need for both people to be present at the same time.

What about ShareDrop?

ShareDrop is a similar browser-based project that also uses WebRTC for direct transfers. Its ownership, hosting and source code status have changed over time, so check sharedrop.io and its source repository for the current position before you rely on it.

Which one should you use?

Use PairDrop when both devices sit on the same network, you want the transfer to stay direct, and you can keep both pages open until it finishes. Use Rapidfile when the other person is somewhere else, when they will not be online at the same time, or when a link, code or QR code is easier to hand over. Many people keep both: PairDrop for quick moves between their own devices at home, and Rapidfile for everything else.

FAQ

Updated 2026-10-20