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, idle auto-lock, and a multi-receiver fan-out.

Feature comparison

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.
• No ads, ever. ToffeeShare is described as a free, independent project. Clipcroft is free with an ad gate after 5 MB cumulative session traffic (a single short ad opens an hour of unlimited transfers, repeats). If a no-ads experience is load-bearing for you, ToffeeShare wins.
• "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, no localStorage to clear. For one-off shares where you specifically want zero residue, that's a feature, not a gap.
• Independent and small. Run by a small team in the Netherlands. Some users prefer that over a roadmap-driven hosted product. Clipcroft has a clearer commercial path (ad-supported), which is fine for some and not for others.

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 clipboard history with bulk export. Thousands of items per clipboard, organised into Texts / URLs / Files / Images sections, with bulk operations per category (download all, ZIP all, share all, copy all, export URLs as HTML). Configurable retention (3-day default). ToffeeShare has no history concept; close the browser, the share ends.
• Multiple clipboards per device. One browser holds many independent clipboards (work / personal / family / project / kiosk), 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 use WebRTC's DTLS 1.3 for transport. 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 5 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 eight lifecycle states. 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 — so a 1 GB file traverses the sender's uplink once. ToffeeShare's published flow is sender-to-receiver pairwise.

Use-case recommendations

Use ToffeeShare when: you want the smallest possible UI for a one-off file send, you don't want any artefact to persist, ads are a deal-breaker, or you prefer an independent small-team project on principle.

Use Clipcroft when: you need a clipboard (text + files), you want history with bulk export, you want multiple separate clipboards per device, you want an optional encryption layer with a user-chosen password and idle auto-lock, or you want to send one file to many devices at once.

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 derived in the browser via PBKDF2, AES-GCM ciphertext, no plaintext anywhere on wire, relay, or local persistence. 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 / Images sections, with bulk operations and a configurable retention TTL.

Can I send to more than one receiver at once with ToffeeShare?

ToffeeShare's published flow is a single sender, single receiver per share. 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 — so a 1 GB file traverses the sender's uplink once, regardless of receiver count.

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, end-to-end encryption, and don't need any artefact to persist after the share is done. Use Clipcroft when you also want a real-time text clipboard, persistent history with bulk export, multiple separate clipboards per device, an idle auto-lock for protected sessions, and the ability to reach 20 devices at once with a single drop.