How does send-any work?

You pick a file on the sender, get a 6-digit code plus a QR and /r/CODE link, then share any of them with the receiver. When they enter the code (or scan the QR), the file transfers directly peer-to-peer over WebRTC DataChannel when possible. If peer-to-peer is blocked by a strict NAT or firewall, the file streams through an in-memory relay on our server — never written to disk.

Yes. send-any is free with no accounts required, no ads, and no file-size limits. An optional free account lets you send to saved friends.

Is the file transfer encrypted?

Yes. All traffic is protected with TLS 1.3 from Let's Encrypt. Peer-to-peer WebRTC transfers add DTLS-SRTP on top. The server never writes file bytes to disk.

How long are files stored?

They are never stored. Bytes flow sender → ~64 KB in-memory buffer → receiver. Session pairing state expires after 10 minutes of inactivity.

Is there a file-size limit?

No hard limit is enforced by the server. Both sender and receiver must stay online until the transfer completes. Very large files in the multi-GB range may hit browser memory limits.

Do I need an account to use send-any?

No. Anonymous transfers via 6-digit code or QR are the default and require no account. Creating a free account only unlocks the Friends feature for sending to saved contacts.

Does send-any work on mobile?

Yes. send-any runs in any modern mobile browser. You can scan the sender's QR code to open the receive page with the code already filled in.

How is send-any different from WeTransfer or Firefox Send?

send-any does not upload your file to a storage bucket. There is no landing page to download from hours later. Transfers are synchronous: sender and receiver pair with a 6-digit code, and bytes stream between them — peer-to-peer when possible, otherwise through an in-memory relay that holds nothing once the transfer ends.

send-any — JavaScript required

send-any is a private, zero-account file transfer service. Share any file of any size with a 6-digit code or QR. End-to-end TLS 1.3, WebRTC peer-to-peer with a streaming in-memory relay fallback, nothing stored on disk.

Please enable JavaScript to use the sender and receiver.

Send a file
Receive a file
Privacy
Security
Status