Best Snapdrop alternative — side-by-side comparison
Snapdrop popularised the "drop devices on a canvas, click to send" UX, but it's local-network-only and its upstream went quiet for long stretches. Several actively maintained tools now occupy the same niche with different trade-offs. We compared the five realistic options on the things that actually differ — cross-network support, encryption, persistent history, multi-device fan-out, and account requirements.
TL;DR. If open source + self-hostable + cross-network is your priority, PairDrop. If LAN-only privacy with native apps everywhere matters more, LocalSend. If you want the smallest possible UI for a one-off P2P send, ToffeeShare. If you want a real clipboard with text + files + persistent history + multi-device live sync, Clipcroft. ShareDrop and Snapdrop itself remain in the running mostly for users who already have a workflow built around them.
Feature matrix
| Clipcroft | Snapdrop | PairDrop | ShareDrop | LocalSend | ToffeeShare | |
|---|---|---|---|---|---|---|
| Browser-only | Yes | Yes | Yes | Yes | Web app + native apps | Yes |
| Cross-network | Yes (TURN) | LAN only | Yes (pairing + TURN) | LAN by default; "+" cross-network mode | LAN only | Yes (WebRTC over internet) |
| Open source | No | MIT | GPL-3.0 | Yes | Apache 2.0 | No |
| Self-hostable | No | Possible | Docker / compose | Possible | Native installer | No |
| Real-time text clipboard | Yes | Message support | Message support | No | Message support | No |
| Persistent history | 3-day default, configurable | No | No | No | No | No |
| Categorised bulk export | Texts / URLs / Files / Images | No | No | No | No | No |
| Optional E2E (user key) | Clipboard password (PBKDF2 + AES-GCM) | WebRTC transport only | WebRTC transport only | WebRTC transport only | HTTPS + optional PIN | DTLS 1.3 transport |
| Idle auto-lock | AutoForget | No | No | No | No | No |
| Multi-device fan-out (>2) | Up to 20, parallel | Pairwise | Public rooms (still pairwise sends) | Pairwise | Pairwise | Pairwise |
| Multiple clipboards per device | Yes | No | No | No | No | No |
| Multi-file queue with retry/resume | 8 lifecycle states | No | Per-transfer | No | Per-transfer | Per-transfer |
| Account / signup | None | None | None | None | None | None |
| File size limit | No per-file cap | No per-file cap | No documented cap | No documented cap | No documented cap | No limit |
| Free | Yes (ad-supported) | Yes | Yes | Yes | Yes (no ads) | Yes (no ads) |
Note: third-party feature details change. The matrix above reflects what was publicly documented at the time of writing. Re-check each project's site if you're making a critical decision.
Quick picks by use case
- "I want open source + self-hostable + cross-network." PairDrop. Active maintenance, GPL-3.0, Docker / compose deploy, persistent device pairing or temporary public rooms.
- "I want strict no-cloud privacy and native apps everywhere." LocalSend. Apache 2.0, Win/Mac/Linux/iOS/Android native apps + web, LAN-only by design.
- "I want a real clipboard, not a file-share tool." Clipcroft. Real-time text + files, persistent history, multiple clipboards, multi-device fan-out, optional E2E with idle auto-lock.
- "I want the smallest possible UI for a one-off P2P send." ToffeeShare. Browser-only, no signup, DTLS 1.3, no size limit, close-the-tab-to-end semantics.
- "I'm already in Snapdrop's flow and don't want to retrain anyone." PairDrop is the closest UX migration with first-class cross-network pairing. ShareDrop is the closest community-equivalent — same-public-IP by default with an opt-in "+" cross-network mode.
One-paragraph summaries
Clipcroft
Real-time multi-device clipboard with files, history, encryption, AutoForget
Browser-only on every platform, cross-network via WebRTC, up to 20 devices on one clipboard with parallel fan-out, persistent history with bulk export, multiple independent clipboards per device, optional per-clipboard end-to-end encryption with idle auto-lock, multi-file queue with eight lifecycle states. No account, no install. Free with an ad gate after 5 MB cumulative session traffic.
PairDrop
Open-source Snapdrop fork with cross-network pairing
GPL-3.0, browser-based WebRTC, persistent device pairing via 6-digit codes, temporary public rooms via 5-letter codes, TURN relay for cross-network. Active maintenance, self-hostable via Docker. No account, no install. The right pick if open source and self-hosting are priorities.
LocalSend
Open-source LAN-only file share with native apps
Apache 2.0, native apps for Windows / macOS / Linux / Android / iOS plus a browser web app. LAN-only by design — data never leaves the local network. HTTPS + optional PIN. No account, no ads, no tracking. The right pick if "no cloud relay anywhere, including ours" is the requirement.
ToffeeShare
Minimalist browser P2P with DTLS 1.3
Free independent project, browser-only, WebRTC peer-to-peer, no size limit, no account, no install. Close-the-tab-to-end semantics — nothing persists. DTLS 1.3 transport encryption. No real-time clipboard, no history. The right pick if "one-off file send" is the entire job.
ShareDrop
Snapdrop-shaped peer-to-peer file share
Open source, browser-only, WebRTC. The default flow pairs devices on the same public IP; a "+" button enables cross-network transfers. VPN remains unsupported (the project explicitly asks users to deactivate any VPN before connecting). No account, no install. The right pick if you want a Snapdrop-style canvas UX with the option to extend across networks.
Snapdrop
The original LAN-only browser AirDrop
MIT-licensed, browser-only, WebRTC. LAN-only — devices on the same Wi-Fi find each other on a canvas and click-to-send. Upstream maintenance has been intermittent over the years; community forks (most notably PairDrop) carry the active development. The right pick if you specifically want the original UI and your devices are always on the same LAN.
How we picked these five
Pulled from the top organic Google results for "snapdrop alternative". Excluded native-app-only Android tools (SHAREit, xShare) since the SERP-intent is browser-based, and excluded WeTransfer-style cloud relays since they're a different shape than Snapdrop. The five surveyed here are the ones a real searcher is most likely to land on when trying to replace Snapdrop. Snapdrop itself is included for reference. We re-fetched each project before writing this page, but third-party software changes — re-check the source if anything is load-bearing for your decision.
Frequently asked questions
Why look for a Snapdrop alternative?
Snapdrop is local-network-only by design and its upstream project has had long stretches of inactivity. People look for alternatives when they need to share between devices on different networks, want active maintenance, want a real clipboard rather than one-off file transfers, or need encryption with a user-derived key rather than just WebRTC's transport layer.
Which Snapdrop alternative crosses networks?
PairDrop and Clipcroft both cross networks via WebRTC over the open internet (TURN fallback when peer-to-peer doesn't work). PairDrop adds a 6-digit pairing code and 5-letter public rooms; Clipcroft uses a clipboard ID. ShareDrop's default flow is same-public-IP, but a "+" button enables cross-network transfers (VPN remains unsupported). Snapdrop and LocalSend are local-network-only by design.
Which alternative is open source?
PairDrop (GPL-3.0) and LocalSend (Apache 2.0) are open source. ShareDrop's repo is also open. Clipcroft and ToffeeShare are not open source. If open source is a hard requirement, PairDrop and LocalSend are the picks.
Which alternative has clipboard history?
Only Clipcroft. Snapdrop, PairDrop, ShareDrop, LocalSend, and ToffeeShare are all built around discrete file or message transfers — once the share is done, there's no record. Clipcroft keeps thousands of items per clipboard, organised into Texts / URLs / Files / Images sections, with bulk export per category and a configurable retention TTL.
Which alternative supports more than two devices at once?
Clipcroft supports up to 20 connected devices on the same clipboard with parallel WebRTC fan-out from a single sender. The others are pairwise — pick one receiver per file. PairDrop's public rooms allow many devices in the same room, but transfers are still sender-to-one-receiver-at-a-time.
Which one should I pick?
If you want open source + self-hostable + cross-network, pick PairDrop. If you want strict LAN-only privacy with native apps everywhere, pick LocalSend. If you want a minimal one-off P2P file share with no install and no signup, pick ToffeeShare. If you want a real clipboard (text + files + history + multi-device) and don't need open source, pick Clipcroft.
Try Clipcroft for real-time multi-device clipboard sync with history.
Open Clipcroft