LocalSend: Open-source, cross-platform file sharing to nearby devices

Original Article ↗ Hacker News Discussion ↗

Positioning vs. Other Tools

  • LocalSend is framed as a cross‑platform, open‑source AirDrop analogue for quick, ad‑hoc file transfers, not continuous sync.
  • Several commenters stress it is not a Syncthing competitor: Syncthing is for folder syncing; LocalSend is for one‑off sends of photos/files.
  • Compared to Tailscale Taildrop, some see Taildrop as over‑complex or alpha; others say it works fine across many platforms after simple setup.

Transport, Networks, and Discovery

  • LocalSend relies on a local network (Wi‑Fi/LAN); it doesn’t use Bluetooth or create ad‑hoc Wi‑Fi like AirDrop.
  • This limits use in scenarios without infrastructure (e.g., firefighters in the field); possible workarounds mentioned:
    • Phone hotspots / local-only Wi‑Fi,
    • VPN overlays (WireGuard/Tailscale),
      but these are less seamless than AirDrop.
  • Multiple people wish for Bluetooth-based discovery and small‑file transfer, and/or Wi‑Fi Direct support.

Alternatives and Ecosystem Fragmentation

  • Many alternatives are listed:
    • LAN/desktop tools: Syncthing, rsync, SFTP, NFS, uploadserver, simple-file-server.
    • GUI cross-platform: KDE Connect, LANDrop, Feem, Nextcloud, Payload, TrebleShot.
    • Browser-based: Snapdrop, PairDrop, ShareDrop, FilePizza, Instant.io, drop.lol, etc.
    • CLI: croc, Magic Wormhole, wormhole-william, p2pcopy, pcp.
  • Some lament that every few months a new tool appears, none become ubiquitous, and non‑technical users still resort to email, WhatsApp, Signal, etc.

Usability, Bugs, and Performance

  • Many praise LocalSend’s ease of use, cross‑platform coverage (Android, iOS, macOS, Windows, Linux), and simple setup.
  • Reported issues:
    • Preventing system sleep on Windows/Linux.
    • High CPU usage on Linux when the Flutter UI window is visible; disabling animations helps.
    • On Android, receiver must be awake and app foregrounded.
    • Transfer speeds reportedly lower than SMB, croc, and even LANDrop for some; unclear if network complexity is a factor.
    • Doesn’t work on Chromebooks (linked issue).

Privacy, Terms, and Openness

  • Privacy policy is extremely minimal: claims no personal data is collected, hence nothing is shared or sold. Some call this ideal; others criticize lack of detail on non‑personal data and telemetry.
  • Terms of Service disallow users under 18, which disappoints those wanting family use.
  • Code is MIT‑licensed and mirrored on non‑GitHub hosting; a side discussion clarifies that GitHub’s status doesn’t affect LocalSend being open source.

Standards and Interoperability

  • Several commenters want:
    • A common open protocol for local file sharing, or
    • A multi‑protocol tool that can interoperate with many existing projects.
  • Consensus that the main missing piece industry‑wide is not technical feasibility but a ubiquitous, preinstalled, cross‑vendor standard.