Redshift — how a transfer works

9:41

Tap to securely share your files

Bundling files…

file.zip 8.9 MB

Transfer Code

42-wandering-otters

file.zip 8.9 MB

3.8 MB / 8.9 MB

Ready to receive? Tap here

9:41

Scan or enter transfer code

42-wandering-otters

3.8 MB / 8.9 MB

Ready to send? Tap here

— zsh — 80×24

~ %

Redshift

Receive a transfer

Paste the code from the sender, or open an rs:// link.

Waiting for code…

Receive a transfer

Paste the code from the sender, or open an rs:// link.

Code looks good — press Return

Joining transfer session…

Receiving

file.key 184 MB · 0% · 22.1 MB/s

Direct P2P Decrypting locally

Saved to ~/Downloads · Verified end-to-end

A Redshift transfer, at a glance

Pick a file. The sender's app turns it into a sealed payload — bytes are encrypted on-device before they leave.
Share the code. A short nn-verb-noun code, a QR, or an rs:// link — whatever's easiest.
Receive it. Phone, CLI, or Mac. The code authenticates the channel; bytes never sit decrypted on a server.
Verified delivery. The full file is integrity-checked end-to-end with BLAKE3.