Clipcroft vs LocalSend

LocalSend is a polished open-source file-sharing tool that runs as a native app on every desktop and mobile OS. Its design is local-network-only — your data never leaves the LAN, no internet required. Clipcroft is a browser-based clipboard that takes the other approach: nothing to install on either end, no shared network required, and a real-time text clipboard with local persistent history.

LocalSend vs Clipcroft

Note: third-party feature details change. The summary above reflects what was publicly documented at the time of writing.

Where LocalSend wins

• Open source under Apache 2.0. Read the code, audit it, fork it. For users where open source is a hard requirement, LocalSend is the right pick over Clipcroft. We're not OSS.
• Local-network-only by design — strong privacy story. Data never leaves your LAN, and there's no remote infrastructure at all — no relay server to compromise, no TURN credentials to manage, no third-party operator. For users whose threat model includes "what happens if the relay operator is subpoenaed", that's the strongest possible answer. Clipcroft keeps data on the LAN too when it can — if both devices are on the same Wi-Fi, the files travel directly between the two browsers and don't cross the internet — but it does use a remote server to introduce the devices, plus a TURN relay as a fallback when they're on different networks. That's a different trust posture from LocalSend's "no remote server, ever".
• Native apps everywhere. First-class apps for Windows, macOS, Linux, Android, and iOS. Faster than a browser-clipboard API for very rapid copy-paste loops, and the apps integrate with native OS features (system share sheet, file manager). Clipcroft is browser-only.
• No cost, no ads. LocalSend is funded as an open-source project; Clipcroft's hosted service is free and ad-supported. If you prefer a no-ad model, LocalSend wins.

Where Clipcroft wins

• Cross-network transfers — the use case LocalSend explicitly doesn't cover. If you're on cellular and your laptop is on home Wi-Fi, or you're at a café on guest Wi-Fi and your home desktop is on residential, LocalSend can't connect you. Clipcroft uses WebRTC over the open internet (with TURN fallback for hard NATs), so the two devices can be anywhere.
• Real-time text clipboard, not just file sharing. LocalSend is built around "pick a recipient, send a file or message". Clipcroft is built around a continuously-synced clipboard — text and files appear live on every connected device. If most of your sharing is text snippets between your own devices, that's a very different experience.
• Persistent clipboard history. Your history lives in your browser's local storage — not in any cloud or server. Thousands of items per clipboard, organised into Texts / URLs / Files sections, with bulk operations per category. Configurable 7-day default retention TTL.
• Browser-only on every platform — zero install. No app to push to managed devices, no permissions check on a corporate laptop, no admin rights required. Open the URL on both devices, you're connected. LocalSend has a web app but the full UX expects the native app on at least one side.
• Optional end-to-end encryption with locally-derived keys. LocalSend uses HTTPS in transit + optional PIN verification — strong for the LAN threat model. Clipcroft adds optional per-clipboard E2E encryption: with a password set, contents are encrypted in the browser via PBKDF2-derived AES-GCM before they leave the device, including the localStorage at rest. This protects the relay path too, not just transport.
• Multiple clipboards per device. One browser holds many independent clipboards, each with its own history, password, retention, and device list. LocalSend has the concept of paired devices but they share a single device pool.
• Multi-file transfer queue with retry, cancel, and resume. Eight queue states (Queued, Preparing, Connecting, Transferring, Retrying, Completed, Failed, Canceled). Cancel one without disturbing the rest. Auto-resume from the last received byte if the network drops. LocalSend handles transfers individually; queue semantics are simpler.

How to use Clipcroft instead of LocalSend

1. On one device, open clipcroft.com in any browser and tap or click Create a new online clipboard. You'll get a clipboard name like "coolfox42".
2. On the other device, open clipcroft.com, enter the same clipboard name, and tap or click Open. Both devices are now connected — even on different networks.
3. Tap or click the icon to pick one or more files. They start transferring to the other device right away. Tap or click Save on each received file — or use the sidebar's Export content option to save them all at once.

The same flow works in any direction, between any mix of devices — and, unlike LocalSend, the two devices don't need to be on the same network.

Use-case recommendations

Use LocalSend when: open source is a hard requirement, you're happy installing native apps, you have strict no-cloud requirements that include "no relay anywhere", and both devices are on the same Wi-Fi.

Use Clipcroft when you want a browser-only flow with nothing to install — on the same Wi-Fi or across different networks — you want a real-time text clipboard with persistent history, optional end-to-end encryption, or multiple separate clipboards per device.

Frequently asked questions

What is LocalSend?

LocalSend is a free, open-source (Apache 2.0) cross-platform file-sharing tool. It has native apps for Windows, macOS, Linux, Android, and iOS, plus a web app at web.localsend.org. The native apps are local-network-only by design — devices on the same Wi-Fi discover each other and transfer files directly, without anything leaving the local network and without needing internet access.

Does LocalSend work between two devices on different networks?

Not by design. LocalSend's privacy story is that data never leaves the local network — it requires both devices to be on the same Wi-Fi or LAN. If you want to share between, say, your phone on cellular and your desktop on home Wi-Fi, LocalSend won't help. Clipcroft is built for cross-network transfers via WebRTC over the open internet (with TURN fallback), so the two devices can be on different networks.

Is LocalSend encrypted?

Yes. LocalSend uses HTTPS for all transfers and offers optional PIN verification for extra security. Because everything stays on the LAN, the threat model is mostly "protect against another device on the same Wi-Fi". Clipcroft adds optional per-clipboard end-to-end encryption with a user-derived key (PBKDF2 + AES-GCM), which protects against the relay path itself.

Does LocalSend have a real-time text clipboard?

No. LocalSend is built around discrete file or message sends — pick a recipient on the LAN, hit send. Clipcroft is a continuously-synced clipboard: paste text on one device and it appears on every connected device live, with persistent history.

Can I run LocalSend on a device that doesn't have an installer?

There is a web app at web.localsend.org. It is a separate implementation from the native apps and, unlike them, may require an internet connection to reach other devices. For a fully offline, local-only transfer you would still use the native app. Clipcroft is browser-only on every platform — no install on either end.

Do I need an account to use Clipcroft?

No. Clipcroft has no account system — no Apple ID, no Microsoft account, no Google account, no email, no signup.

Which one should I use?

Use LocalSend when open source is a hard requirement, you're happy installing the native app, you want strict local-only privacy with no relay anywhere, and both devices are on the same Wi-Fi. Use Clipcroft when devices are on different networks (or you don't want to think about networks), you want a real-time text clipboard with history, you want a browser-only flow with no install, or you want optional end-to-end encryption that protects the relay path too.