Localsend: An open-source cross-platform alternative to AirDrop

Localsend, an open-source, cross‑platform file transfer tool, is being highlighted as a practical way to move photos, videos, configs, and text between Windows, macOS, Linux, Android, iOS, and other devices on the same local network. Many users praise its reliability, simplicity, browser support, and lack of accounts compared with AirDrop and Android’s Quick Share, but note that it lacks AirDrop’s seamless peer‑to‑peer network creation, Bluetooth-based discovery, and often its speed. The debate widens into comparisons with alternatives like KDE Connect, PairDrop, Blip, Syncthing, Magic Wormhole, and various WebRTC or VPN-based tools, underscoring how hard it is to match AirDrop’s frictionless, infrastructure‑free sharing in a fully interoperable, open solution.

Overall reception

  • Many commenters use LocalSend daily across Windows, macOS, Linux, Android, iOS, and FireOS and describe it as reliable and fast enough for typical use.
  • It’s praised for being open source, cross‑platform, easy to set up, and not requiring accounts or a central server.
  • Some consider it the “best option” they’ve found for LAN file transfer; others see it as one tool among several (often alongside KDE Connect).

Typical use cases

  • Moving photos and large videos (100 MB–3 GB) between phones and desktops, especially across platforms (Apple ↔ Android ↔ Linux ↔ Windows).
  • Ad‑hoc secure transfer of sensitive configs (SSH keys, VPN profiles, .env files) without cloud storage or chat apps.
  • Sending plaintext snippets between devices (e.g., debugging sessions, notes).
  • One‑off transfers for devices that don’t share an ecosystem (e.g., iPad → Windows laptop, old Android → Mac).

Comparison to AirDrop

  • Core limitation: requires both devices on the same LAN or a manual hotspot; cannot autonomously create peer‑to‑peer Wi‑Fi like AirDrop.
  • Several people say AirDrop is faster and more integrated but notably unreliable; others say LocalSend is more dependable even if less slick.
  • Some argue LocalSend is not a “true” AirDrop replacement because it lacks automatic proximity discovery and off‑network operation.
  • A few users find LocalSend noticeably slower than AirDrop; others say speed is excellent for their needs.

Technical behavior & constraints

  • Uses REST over HTTPS on the local network; some note it can run purely in the browser via a WebRTC-based web client.
  • Troubles with VPNs (especially Tailscale) and complex or isolated networks are reported; often it works once VPN is disabled.
  • On some systems it reportedly prevents sleep or has high resource usage; implementation details are debated (Flutter vs. “heavy Electron”; unclear).
  • Interrupted transfers can leave corrupted partial files instead of cleaning them up, which is seen as a serious flaw.

Alternatives and related tools

  • Frequently mentioned alternatives: KDE Connect, Quick Share, PairDrop, Blip, Feem, Magic Wormhole, Syncthing, send/ffsend, wormhole.app, FlyingCarpet, Sendme/Iroh, and various ad‑hoc methods (HTTP server, rsync/sshfs).
  • Some prefer browser‑only or WebRTC tools for zero‑install sharing; others prioritize strictly local, offline operation and reject internet‑relay solutions.