Snapdrop

Local file sharing without accounts, apps, or Apple tax. Honestly reviewed.

TL;DR

• What it is: A browser-based, peer-to-peer local file sharing tool inspired by Apple’s AirDrop. Open the same URL on two devices on the same Wi-Fi — they see each other, you drag, you drop, done [4][5].
• Who it’s for: Anyone who regularly moves files between devices that don’t play nicely together: Android + Windows, iPhone + Linux, Raspberry Pi + anything. Also useful for sending files to guests without asking them to install anything [4][1].
• Cost savings: AirDrop is free but Apple-only. Every cross-platform paid alternative (WeTransfer, SendAnywhere premium) disappears once you self-host Snapdrop on a $5/mo VPS or your home server [1][5].
• Key strength: Zero friction. No account, no app install, no file size limits, no third-party server touching your files. Pure WebRTC peer-to-peer [4][5].
• Key weakness: The original project was acquired by LimeWire in early 2025. Snapdrop.net now routes files through LimeWire’s cloud storage instead of peer-to-peer. The open-source classic still works — but you have to self-host it [3].

---

What is Snapdrop

Snapdrop is a Progressive Web App that puts AirDrop-style local file sharing in a browser tab. You open it on two devices on the same network, they detect each other automatically, you click the other device’s icon, pick a file, and it transfers directly between them over WebRTC. No account required. No file size limit. No upload to a cloud server. The receiving device gets the file; Snapdrop’s server only facilitates the initial handshake [4][5].

The project was created by Robin Linus and sat at ~19,700 GitHub stars as a beloved, minimal open-source tool for years [merged profile]. The tech underneath is straightforward: vanilla HTML/CSS/JS frontend, Node.js backend for WebSocket signaling, and WebRTC for the actual data transfer. Because WebRTC is peer-to-peer and encrypted in transit, the developer could honestly say “Snapdrop doesn’t even use a database” — there was nothing to store [4].

That changed in early 2025. The GitHub README now reads: “Snapdrop has been acquired by LimeWire, a leading file sharing platform with integrated AI tools.” The hosted version at snapdrop.net is now effectively a LimeWire-branded cloud upload service with an AI layer bolted on. Trustpilot reviews from February 2025 are not subtle about this: “Acquired by Limewire. The whole process is now just essentially a short term cloud file storage and transfer” [3]. One reviewer put it plainly: “ZERO users wanted this, literally none of your users wanted this” [3].

The good news: the GitHub repository stays frozen at the classic version and the Docker image still works. If you want the original Snapdrop — the one that does one thing perfectly — you self-host it.

---

Why people choose it

The appeal is almost embarrassingly simple: it works on anything with a browser, and it requires nothing from the person on the other end.

The Ars Technica review [4] captures the use case better than any marketing copy could. The author describes a household where one person uses Apple devices and the other doesn’t. AirDrop is useless across that boundary. LocalSend (a native app alternative) requires installation on every device. Snapdrop requires nothing — “if both systems are technically capable of opening a browser, I use Snapdrop.” That’s the entire pitch.

The homelab Reddit thread [2] shows the self-hosting motivation. Users were hitting the hosted snapdrop.net during downtime and decided to run their own instance rather than depend on an external service. The fix was straightforward: pull the linuxserver Docker image, spin it up, done. No configuration headaches, no database to manage.

Where Snapdrop loses is on reliability and the 2025 LimeWire situation. The Ars Technica author notes: “Once in a while, the Snapdrop site has failed to load on a device” and acknowledges LocalSend as a fallback for when Snapdrop can’t find the other device [4]. The mobikin.com comparison [6] flags that Snapdrop only works on local networks — there’s no room-link feature for remote sharing, unlike ShareDrop. If both devices aren’t on the same Wi-Fi, Snapdrop (classic) can’t help you.

---

Features

Based on the README, Easypanel docs, and third-party reviews:

Core functionality:

• Browser-based, no install required on any device [4][5]
• Peer-to-peer file transfer via WebRTC — files never touch a server [4][5]
• WebSocket signaling for initial device discovery on local network [README]
• Auto-detects other devices on the same network; assigns quirky memorable names like “Purple Salamander” [4]
• Drag-and-drop or click-to-select file sending [5]
• Text message sending between devices (right-click or tap-and-hold) [4]
• No file size limits [6]
• End-to-end encrypted transfers [5]

Progressive Web App:

• Installable as a PWA from the browser — gives you an app icon without an app store [4]
• Light/dark mode toggle [4]
• Works on Chrome, Firefox, Safari, Edge, and other modern browsers [5]
• Mobile-optimized layout — works between phone and desktop [5]

Self-hosted extras:

• Docker deployment via linuxserver image [1][5]
• Nginx + SSL support in the Docker Compose setup [1]
• Minimal resource usage — no database, no persistent storage [4]

What it deliberately doesn’t do: The FAQ is explicit that the developer “willfully rejects new feature ideas” to keep the tool focused [4]. No accounts, no file history, no cloud sync, no folder sharing (classic version), no remote transfer outside local network.

---

Pricing: SaaS vs self-hosted math

This category is almost too easy.

Snapdrop classic (self-hosted):

• Software: $0 (GPL-3.0) [merged profile]
• VPS or home server to run it on: $0 if you already have a home server; $5–10/mo on a shared VPS if you want it accessible from anywhere on your home network via VPN

Snapdrop.net (post-LimeWire acquisition):

• Basic file transfer: appears free with cloud upload
• AI tools and additional storage: subscription required (pricing not publicly listed in sources)
• Your files: uploaded to LimeWire’s cloud, stored for one week per user reports [3]

AirDrop (the thing Snapdrop replaces):

• Free, but requires Apple hardware on both ends. If you don’t own an iPhone and Mac, the cost is buying the hardware — not a software bill, but a real constraint [4].

Alternatives for comparison:

• WeTransfer free: 2GB file limit, files expire in 7 days, uploads to cloud
• SendAnywhere: 10GB limit on free tier, requires account for link sharing
• ShareDrop: free, open-source, similar model — but adds room links for cross-network transfers [6]

The self-hosted math is trivially in your favor if you already run any home server. There’s no recurring software cost, no per-GB charge, no account management. The only cost is the infrastructure you probably already pay for.

---

Deployment reality check

The noted.lol review [1] provides a concrete Docker Compose stack for deployment. It’s a two-container setup: one Node.js container for the Snapdrop server, one Nginx container handling SSL termination. The post explicitly notes: “Snapdrop works best using SSL behind reverse proxy.”

The Easypanel template [5] simplifies this to a one-click deploy using the linuxserver image (lscr.io/linuxserver/snapdrop:version-b8b78cc2). The linuxserver image is the most commonly recommended self-hosted path — the Reddit thread [2] specifically links to it as the solution that “works ok.”

What you need:

• A machine on your local network (Raspberry Pi, NAS, VPS) with Docker
• A reverse proxy (Caddy or Nginx) if you want HTTPS — and you want HTTPS, because WebRTC can behave inconsistently over plain HTTP
• A domain or local DNS entry pointing at your server
• No database, no external storage, no SMTP

Realistic time estimate: 20–45 minutes for someone comfortable with Docker Compose. The complexity ceiling is the SSL setup — if you’ve done that before for any other service, Snapdrop adds maybe 10 minutes on top.

What can go sideways:

• Device discovery sometimes fails. WebRTC relies on the devices being correctly routed on the same network segment. VLANs, guest Wi-Fi isolation, and some enterprise routers can silently break device discovery [4]. If devices don’t appear, the first thing to check is whether your network isolates clients from each other.
• The linuxserver image is the community-maintained option, not an official release from the original repo. It’s widely used and trusted in the homelab community, but worth knowing the provenance [2][5].
• If you’re running this for others in your household or office, make sure they open the browser on the same network. Snapdrop classic has no remote sharing mode [6].

---

Pros and Cons

Pros

• Genuinely zero friction. Open a URL on two devices. That’s the entire setup for the end user. No account, no pairing, no app store [4][5].
• True peer-to-peer. Files go directly between devices via WebRTC, encrypted in transit. Not staged on any server [4][5].
• Cross-platform by default. Works anywhere there’s a browser — Windows, macOS, Linux, Android, iOS, ChromeOS, Raspberry Pi [4][6].
• No file size limits. Unlike WeTransfer or similar cloud tools, transfers are only bounded by available memory and patience [6].
• Minimal infrastructure. No database, no persistent storage, barely any compute. A Raspberry Pi handles it without breaking a sweat [1].
• Useful for guests and one-off transfers. You don’t need to ask anyone to install anything [4]. Hand them the URL; they’re done.
• Self-hostable on Docker with a well-maintained linuxserver image [1][2][5].

Cons

• The hosted version is now LimeWire. If someone finds snapdrop.net without context, they get a cloud upload service that stores their files on LimeWire’s servers, not direct P2P transfer [3]. The brand is compromised.
• Local network only. No remote sharing, no link-based transfer to someone on a different network. ShareDrop has room links; Snapdrop classic doesn’t [6].
• Device discovery can fail silently. Network isolation, VLANs, and guest Wi-Fi all break the discovery handshake with no clear error message [4].
• Occasional reliability issues on the hosted version (pre-acquisition) — the Reddit thread was started specifically because people kept hitting downtime [2].
• No folder transfer in the classic version — files only, not directories [compared to LocalSend in 4].
• Limited Trustpilot signal. Only 9 reviews at 3.0/5, which is too small a sample to be meaningful — but the 2025 reviews are uniformly negative about the LimeWire transition [3].
• Development is effectively frozen. The original author built it to do one thing and stay that way. No new features coming; no company maintaining it [4].

---

Who should use this / who shouldn’t

Use Snapdrop (self-hosted) if:

• You regularly transfer files between devices from different ecosystems — Android phone + Windows PC, iPhone + Linux laptop — and AirDrop isn’t available.
• You want to give guests or colleagues a frictionless way to send you files without installing anything.
• You already run a home server or NAS and a 20-minute Docker setup is nothing.
• You need something to send files to headless servers or single-board computers where installing a native app is annoying.

Skip it (use LocalSend instead) if:

• You want something more robust with folder transfers, manual IP entry when auto-discovery fails, and a proper native app on your devices [4]. LocalSend is the belt-and-suspenders version — slightly more setup friction, significantly more reliable.

Skip it (use ShareDrop instead) if:

• You need to share files with someone on a different network. ShareDrop supports room links for cross-network transfers; classic Snapdrop does not [6].

Skip it entirely if:

• You’re looking at snapdrop.net without knowing about the LimeWire acquisition. Read source [3] first. The hosted version now works differently from what most people expect Snapdrop to be.
• Your network isolates wireless clients from each other (common on enterprise Wi-Fi or guest networks). Snapdrop’s device discovery will fail, and there’s no fallback [4].

---

Alternatives worth considering

• LocalSend — The most direct comparison for a self-hoster. Open-source, native apps for all major platforms, folder support, manual IP discovery when auto fails. Slightly more friction for the receiver (they need the app installed), but more robust [4]. Probably the better long-term choice for home server deployments.
• ShareDrop — Same browser-based model as Snapdrop but adds room link support for cross-network sharing. Open source, actively maintained, no acquisition drama [6].
• PairDrop — The Trustpilot reviews from 2025 explicitly recommend this as the post-LimeWire alternative [3]. It’s a Snapdrop fork that continues the original vision — worth checking if you want a hosted option that hasn’t pivoted.
• Warpinator — GNOME project, Linux-first, also cross-platform. Native app, no browser required. Better for Linux-heavy households.
• Magic Wormhole — Command-line tool, not browser-based, but genuinely secure and works across networks. For technical users only.
• Tailscale + any file transfer — If you’re already running Tailscale for your homelab, you get secure cross-network access and can use any of the above tools as if everyone were on the same LAN.

---

Bottom line

Classic Snapdrop does one thing — local network file transfer, browser-based, no accounts — and it does it with less friction than almost anything else available. For the specific problem of sending a file from your Android phone to your Windows laptop without plugging in a cable or fighting Bluetooth, it’s still the fastest solution. The self-hosted Docker version preserves everything that made it worth using.

The complication is the 2025 LimeWire acquisition, which turned snapdrop.net into something the original users didn’t want and don’t trust. If you want Snapdrop, self-host it — or use PairDrop, which carries the original torch. Either way, the answer isn’t the hosted version anymore.

For non-technical founders: if you’re using WeTransfer or a similar tool to move files between your own devices, this replaces that completely at zero recurring cost. A $5 VPS or spare Raspberry Pi and 45 minutes of setup is the entire investment.

---

Sources

1. noted.lol — “Snapdrop - A Self Hosted Airdrop Alternative”. https://noted.lol/snapdrop-a-self-hosted-airdrop-alternative/
2. Reddit r/homelab — “Does anybody host snapdrop in their home? Or know better alternative?”. https://www.reddit.com/r/homelab/comments/yrg5pc/does_anybody_host_snapdrop_in_their_home_or_know/
3. Trustpilot — “Snapdrop Reviews” (9 reviews, 3.0/5). https://www.trustpilot.com/review/snapdrop.net
4. Kevin Purdy, Ars Technica — “I use these 2 apps for universal AirDrop rather than pushing people to Apple” (Mar 2024). https://arstechnica.com/gadgets/2024/03/the-two-apps-i-use-when-i-need-airdrop-on-non-apple-devices/
5. Easypanel — “SnapDrop | Self-Host on Easypanel”. https://easypanel.io/docs/templates/snapdrop
6. MobiKin — “ShareDrop vs. Snapdrop: An Even-handed Comparison [2025]”. https://www.mobikin.com/mobile-phone/sharedrop-vs-snapdrop.html