A WeTransfer alternative that encrypts files before upload

WeTransfer made sending files as easy as sharing a link. ShieldFive Send does the same job, with one difference that matters: the files are encrypted in your browser before they are uploaded, so the service moving them stores only ciphertext.

Send files encrypted

You drop files, we hand back a link, and the key to open it lives in the part of the link after the “#” — which is never transmitted to us. We hold ciphertext and nothing else.

The key never reaches the middleman

WeTransfer holds your upload in a form it can open. Here the file is encrypted on your device and the decryption key rides after the “#” in the link, a part of the URL browsers never send to a server. We receive ciphertext and a fragment we never see.

Crypto you can go and read

Each transfer is sealed with a random key under XChaCha20-Poly1305 from the open-source @shieldfive/crypto core. “Encrypted” is a claim you can check against the source rather than a badge on a marketing page.

EU-hosted, and unmeasured

Ciphertext sits in the EU, and there are no trackers on the send or download pages — no analytics on who you sent what to, because there is nothing readable to analyse in the first place.

Free, no email, no signup

Send a transfer without an account or an email address. Signing in only adds a history of what you sent and raises the size, expiry, and download limits.

Send a file in seconds

Drop it, share the link, and it’s encrypted before it leaves your device — no account required.

Send files encrypted

Questions

How is this different from WeTransfer?
WeTransfer can technically read the files you upload; its servers hold them in the clear. With ShieldFive Send, files are encrypted on your device first and the key is in the link fragment, which never reaches our servers — so we only ever store ciphertext.
Is it free, and do I need an account?
Sending a transfer is free and needs no account. Signing in adds a history of what you sent and raises the size, expiry, and download limits.
How large can a transfer be?
The in-browser transfer is currently limited to a few hundred MB total, because each file is encrypted whole in memory. Streaming for multi-GB transfers is a planned follow-up.