The scenario repeats itself daily in offices everywhere. A MacBook on your left, an Android phone in hand, a Windows PC humming quietly with a Linux VM somewhere in the background. A colleague pings you on Slack with a file. You need it everywhere. AirDrop won't acknowledge the PC exists, Quick Share mainly supports Android-to-Windows integration and doesn't support iOS or macOS, and the thought of uploading to Dropbox just to download it three times feels like admitting defeat.
Mundane? Absolutely. Solvable? Apparently not by Apple, Google, or Samsung.
That's the friction Tien Do Nam decided he'd had enough of. His answer, LocalSend, has quietly gathered 79.9k stars on GitHub—not through venture-backed marketing blitzes or influencer partnerships, but by doing something the platform giants collectively refuse to attempt: making file sharing work seamlessly across every major operating system, no internet connection required.
AirDrop's Beautiful Prison
AirDrop remains one of Apple's most genuinely useful features. It's also one of its most ruthlessly proprietary ones. AirDrop uses a proprietary protocol called Apple Wireless Direct Link, a technology so tightly controlled that your iPhone will simply never see your Linux box. Ever. No matter how much you might wish it otherwise.
Google and Samsung, for their part, merged their competing efforts into Quick Share in early 2024—an alliance that mostly just formalized what Android users already knew. But iOS and macOS users? Still on the outside looking in.
The result is a landscape littered with workarounds. People email files to themselves. They spin up temporary cloud folders for a single PDF. Some reach for browser-based tools like Snapdrop, which work just fine until you need background transfers or speeds that approach your Wi-Fi's actual capabilities.
LocalSend entered this messy ecosystem in 2022 with a proposition that bordered on radical in its simplicity: open-source, cross-platform, no servers, no accounts, no internet. Just devices on the same network, discovering each other, moving files at local speeds.
Under the Hood (Where It Gets Interesting)
Technically speaking, LocalSend uses a REST API over HTTPS with TLS certificates generated on the fly for each device. Discovery happens through multicast and HTTP broadcasts on port 53317. The protocol documentation is public—currently version 2.1, for anyone curious—which means security researchers can audit the model and developers can build compatible clients if they want to.
Nam built the app primarily in Dart using Flutter, which explains how he managed to ship native applications for Windows, macOS, Linux, Android, and iOS from a single codebase. There's also a web interface at web.localsend.org for recipients who haven't installed the app, served over local HTTP with a "share via link" feature that sidesteps installation entirely.
Performance, naturally, depends on your network. The documentation explicitly recommends 5 GHz Wi-Fi for speed and notes that encryption toggles affect throughput. If you've enabled AP isolation on your router, you'll need to turn it off. iOS and macOS devices require the "Local Network" permission to discover peers—a small hoop to jump through, but unavoidable given Apple's privacy framework.
The Hacker News Effect
LocalSend's first major appearance on Hacker News came in October 2023. That thread gathered 563 points and 229 comments, with developers comparing it to KDE Connect, Warpinator, and various browser-based alternatives. A second wave hit in March 2024 (447 points, 170 comments). By April of that year, PCWorld was publishing how-to guides.
The repository now shows 79.9k stars and 4.3k forks—metrics that don't always mean much, but in this case seem to reflect sustained utility rather than fleeting hype. Flathub, the Linux app distribution platform, reports roughly 50,000 downloads monthly. The app lives on the App Store for iOS, Google Play and F-Droid for Android, and can be installed via winget, Scoop, Chocolatey, Homebrew, Snap, and AUR, depending on which corner of the computing world you inhabit.
Nam operates LocalSend as a community-maintained project with GitHub Sponsors enabled. No venture funding. No company entity. Just an Apache 2.0 license and a German legal imprint listing his Berlin address. The privacy policy is admirably brief: the app does not collect, store, process, or use personal or non-personal data. Full stop.
Security in the Open
A recent version—1.17.0, described as a "small interim release before WebRTC is stable"—added an advanced network interface filter, mobile multi-select swipe gestures, and Windows paste-to-PNG support. More notably, it patched CVE-2025-27142, a path traversal vulnerability that could have allowed arbitrary file writes through upload endpoints.
A second security advisory has since addressed CVE-2026-25154, a stored cross-site scripting vulnerability in the web share interface, rated CVSS 6.1 (Moderate). The existence of these vulnerabilities matters less than the fact that they were publicly disclosed, patched, and documented in the open—exactly how open-source security is supposed to work, even if it doesn't always.
Relief, Mostly
Coverage picked up momentum through 2025 and into early 2026. PC Gamer called it "the most useful app I've come across in a very long time." Windows Central included it in a roundup of essential open-source Windows 11 applications. TechRadar positioned it as the Android-to-Mac solution, TechPP listed it among free open-source Mac apps, and Linux-focused outlets like UbuntuShell and LinuxAdictos published installation guides.
The common thread? Relief.
People describe finally solving a problem they didn't realize had a solution. Or discovering that the janky workarounds they'd normalized for years—the email-to-self ritual, the cloud service juggling act—were actually unnecessary.
Finding Its Lane
LocalSend occupies a specific niche, and it seems comfortable there. It's not trying to be KDE Connect, which offers device integration features like remote input and notification mirroring. It's not Syncthing, which handles continuous folder synchronization. It's not Tailscale Taildrop, which requires a VPN overlay and a different mental model entirely.
It's ad-hoc file sharing. You open the app. You see nearby devices. You send a file. The recipient gets a notification, accepts or rejects, and the transfer happens at whatever speed your local network can sustain. No configuration ritual. No pairing dance. No wondering if your firewall is in the right mood today.
Browser-based alternatives like Snapdrop and PairDrop offer zero-install convenience but can't match native app performance or background receiving. Quick Share handles Android-to-Windows but excludes Apple devices entirely. AirDrop remains the gold standard within its ecosystem—and completely useless outside it.
LocalSend trades ecosystem lock-in for universal compatibility. Which turns out to be exactly what a certain segment of users wants.
What Those 80,000 Stars Actually Mean
GitHub stars are, admittedly, a noisy metric. Projects accumulate them through hype cycles, marketing pushes, or simply being in the right place when a Hacker News thread goes viral. Some fade quickly.
LocalSend's 80,000 represent something more durable: sustained utility.
The project solves a daily annoyance for people who work across device boundaries. Developers running Linux workstations while testing on iOS devices. Product managers shuttling mockups between a MacBook and an Android tablet. Anyone who's ever refused to accept that moving a file from Point A to Point B should require consulting a compatibility matrix.
The open-source model matters here in ways that go beyond licensing philosophy. If LocalSend were a commercial product, its value would be capped by whoever owned it. Google would optimize for Android, Apple for iOS, Microsoft for Windows. Open source allows it to optimize for the problem itself, platform-agnostically, with contributions from anyone who needs it to work better.
Nam's project won't displace AirDrop or Quick Share. Those tools ship by default with billions of devices, and defaults are powerful. But LocalSend doesn't need to displace them.
It just needs to be there when the defaults fail—which, for anyone managing a mixed-OS environment, is more often than the platform vendors would probably like to admit.
