Clipcroft vs ToffeeShare
ToffeeShare is one of the cleanest peer-to-peer file-sharing tools on the web — browser-only, WebRTC-based, no signup, no size limit, end-to-end encrypted via DTLS 1.3. It and Clipcroft are the closest direct match in shape on the entire "online clipboard" / "P2P file transfer" SERP. The differences aren't whether the basic transfer works — both do that well — but whether you also want a clipboard, a history, multiple separate workspaces, password protection, idle auto-lock, and a multi-receiver fan-out.
TL;DR. Use ToffeeShare for one-off P2P file transfers where the minimalist UI is the point. Use Clipcroft when "send a file" is part of an ongoing workflow that also needs text sync, history, multiple clipboards, password-protected sessions, and the ability to send once and have it land on every connected device.
ToffeeShare vs Clipcroft
| Feature | ToffeeShare | Clipcroft |
|---|---|---|
| Browser-only on every platform | Yes | Yes |
| WebRTC peer-to-peer | Yes | Yes |
| End-to-end encryption (transport) | DTLS 1.3 | DTLS via WebRTC |
| Application-layer E2E (user-derived key) | No | Optional clipboard password (PBKDF2 + AES-GCM) |
| Encrypted at rest in localStorage | n/a (no persistence) | Yes (when password set) |
| No signup / no install | Yes | Yes |
| Real-time text clipboard sync | File transfer only | Yes (live across all devices) |
| Persistent local clipboard history | No (close tab to end) | Yes (7 days, configurable) |
| Categorised bulk export | No | Texts / URLs / Files |
| Multi-device live fan-out (>2) | Share-link based | Up to 20 devices, parallel WebRTC pipes |
| Multiple clipboards per device | No (one share session) | Yes |
| Idle auto-lock (AutoForget) | No | Yes (configurable) |
| Multi-file queue with retry / cancel / resume | Per-transfer | Yes |
| File size limit | None | None per file |
| Free | Yes (ad-supported; ad-free for donors) | Yes — unlimited GB, ad-supported |
Note: third-party feature details change. The summary above reflects what was publicly documented at the time of writing.
Where ToffeeShare wins
- Minimalist UI. One drop zone, one share link, one progress bar. Nothing else. If "send a file from A to B" is the entire job, ToffeeShare's UI is harder to beat — fewer surfaces, fewer settings, fewer ways to get confused.
- Ad-free option for supporters. ToffeeShare shows Google ads to fund its free service, but offers an ad-free experience to anyone who makes a donation. Clipcroft is free and ad-supported. If a paid ad-free path matters to you, ToffeeShare offers one.
- "Close the tab, the share ends" semantics. ToffeeShare leans into the "nothing persists" model — there's no history to manage, no retention TTL to think about.
Where Clipcroft wins
- Real-time text clipboard sync, not just file transfer. Paste text or URL on one device and it appears live on every connected device. ToffeeShare is one-shot file shares only.
- Persistent local clipboard history with bulk export. Thousands of items per clipboard, organised into Texts / URLs / Files sections, with bulk operations per category (download all, ZIP all, share all, copy all, export URLs as HTML). Configurable retention (7-day default). ToffeeShare has no history concept; close the browser, the share ends.
- Multiple clipboards per device. One browser holds many independent clipboards, each with its own history, password, retention, and device list. ToffeeShare's session is implicitly singular.
- Optional application-layer end-to-end encryption. Both tools rely on WebRTC's built-in DTLS transport encryption. Clipcroft adds an optional layer on top: with a password set, contents are encrypted in the browser via a PBKDF2-derived AES-GCM key before they leave the device. This protects against any path where transport encryption alone wouldn't (TURN relay, browser data channels, future protocol changes), and the same key encrypts the localStorage at rest. The application-layer key never leaves either browser.
- AutoForget — idle auto-lock for protected clipboards. Configurable idle window (default 15 minutes); when the timer fires, the in-memory AES key handle and the persisted raw key are dropped, and the modal re-prompts on next interaction. Active transfers defer the lock so you don't lose work mid-upload. ToffeeShare has no protected-session concept.
- Multi-file transfer queue with retry, cancel, and resume. Drop any number of files; each tracks its own state (Queued, Preparing, Connecting, Transferring, Retrying, Completed, Failed, Canceled). Cancel one without disturbing the rest of the queue. Auto-resume from the last received byte if the network drops. ToffeeShare handles transfers individually.
- Multi-device fan-out from a single sender. Up to 20 devices on the same clipboard; one drop reaches all of them via parallel WebRTC pipes from one sender — a 1 GB file is read and encrypted once, then streamed in parallel to every device. ToffeeShare centres on sharing a file through a download link.
Use-case recommendations
Use ToffeeShare when: you want the smallest possible UI for a one-off file send.
Use Clipcroft when: you need a clipboard (text + files), you want to send one file to many devices at once, you want persistent local history with bulk export, you want an optional encryption layer with a user-chosen password, or you want multiple separate clipboards per device.
Frequently asked questions
What is ToffeeShare?
ToffeeShare is a free peer-to-peer file-sharing service from the Netherlands. It runs in the browser, uses WebRTC to send files directly between devices, has no size limit, requires no account or install, and documents end-to-end encryption via DTLS 1.3. The data isn't stored online — close the browser tab and the share ends.
Is ToffeeShare end-to-end encrypted?
Yes. ToffeeShare uses WebRTC's built-in DTLS 1.3 transport encryption, with the keys negotiated browser-to-browser. No relay server sees the contents. Clipcroft also uses WebRTC for transport, and adds an optional application-layer encryption with a user-chosen password — keys are derived in the browser via PBKDF2, so everything is encrypted with AES-GCM before it leaves the browser: on the wire, on the relay, and in local storage. The application-layer key never leaves the user's browsers, and is not derived by the browser itself.
Does ToffeeShare have a clipboard history?
No. ToffeeShare is built around one-shot file transfers — pick a file, share the link, done. Once the browser tab closes, the share ends and there's no record. Clipcroft keeps thousands of items per clipboard, organised into Texts / URLs / Files sections, with bulk operations and a configurable retention TTL.
Can I send to more than one receiver at once with ToffeeShare?
ToffeeShare shares a file through a download link and doesn't document a multi-device clipboard or one-to-many fan-out. Clipcroft supports up to 20 connected devices on the same clipboard, with a single drop reaching all of them via parallel WebRTC pipes from one sender — a 1 GB file is read and encrypted once, then streamed in parallel to every device.
Does ToffeeShare work between mobile and desktop?
Yes — ToffeeShare runs in any modern browser including mobile browsers. Clipcroft has the same browser-only model. The differences aren't "which devices" but "what the experience is like once both devices are connected" — Clipcroft adds real-time text sync, history, and multi-device fan-out.
Which one should I use?
Use ToffeeShare for one-off file transfers between two devices where you want a minimal UI, no signup, no install, and end-to-end encryption. Use Clipcroft when you also want a real-time text clipboard, the ability to reach 20 devices at once with a single drop, persistent local history with bulk export, or multiple separate clipboards per device.
Try Clipcroft for real-time multi-device clipboard sync with history.
Open Clipcroft