cindertransfer

peer-to-peer over WebRTC — cinder only carries the handshake
← Send / receive text Chat (prototype) → API reference
Files never touch this server. Cinder relays a few hundred bytes of WebRTC handshake between you and the other person — once that opens a direct connection between your two browsers, the actual file moves peer-to-peer, encrypted end-to-end by WebRTC itself (DTLS). See the main page for what cinder is.
Share this however you like (call, chat, in person) — whoever has it can connect to whoever else has it. Both sides use the same one, and both sides can send and receive once connected — no roles to pick.
Or pair automatically (recommended)
Each side generates a one-time key and you both derive the same secret between you (ECDH) — nobody but the two of you ever transmits it, and it's never reused for another transfer. The cinder-standard pairing method — see D009 in this repo's own plan — shared with cinderchat.
Got a cinder link instead of the secret itself? Load it here
Or share it via a cinder link instead of the raw secret
With Generated key or Password, send the link and the key/password over two different channels — an attacker who only sees one of them still can't recover the secret.
Read once: whoever opens the link consumes it — if anything goes wrong, it's just as easy to agree on the secret again as to redo this step. Read up to 5: survives a chat app's own link-preview crawler fetching the link before the real recipient does (a real, observed problem — Discord's own preview bot burning a read-once link before the intended person ever clicked it) while still expiring quickly once actually used.
Idle

Files to send

Picked here, sent once you're connected.
Drop files here, or click to choose

Incoming files

Waiting to connect…