LocalSend vs PairDrop

Editor take

Choose LocalSend for native apps and transfers that stay on your network. Choose PairDrop for a browser on both ends and pairing across networks.

Editor

Where they differ

Only what is true of one of them and not the other. Each app's weak spots are the other app's strengths.

LocalSend

Where LocalSend is stronger

  • Native apps on every platformiOS, Android, macOS, Windows and Linux clients, plus a web client; PairDrop is browser only.1
  • No relay or serverDevices talk directly on the LAN with no TURN server in the path; PairDrop routes paired devices through coturn when a direct connection fails.2

PairDrop

Where PairDrop is stronger

  • Pairs across networksA pairing code links two devices for good, and a public room gathers devices across networks; LocalSend is built for the same LAN.3

LocalSend vs PairDrop: specs side by side

Every spec for both apps in one table, so you can check install options, hardware and client apps before you pick one.

Spec
PriceFreeFree
LicenceApache-2.0GPL-3.0
Web UIYesYes
iOSYes–
AndroidYes–
WindowsYes–
macOSYes–
LinuxYes–
Docker–Yes
Linux packageYes–
WindowsYes–
macOSYes–
Tech stackFlutterNode.js
Docker ContainersNone – runs locally1 (app only)
Architecturex86 + ARMx86 + ARM

Common questions

Sources: LocalSend docs and PairDrop docs.

Updated