Encrypted file sharing means the files are unreadable to anyone without the key. The strongest form is end-to-end encryption: your device encrypts the files before upload and only the recipient's device can decrypt them, so the service in between can't read them. Many popular services only encrypt files on their own servers, which protects against outsiders but not against the provider itself.
End-to-end vs server-side encryption
Nearly every file sharing service says your files are "encrypted". The question that matters is who holds the key.
- Server-side encryption. You upload the file over HTTPS, the provider receives it readable, then encrypts it on its disks with keys it manages. A breach of the provider, an insider or a legal demand can expose readable files.
- End-to-end encryption (E2EE). Your browser or app encrypts the file before it leaves your device. The provider receives and stores ciphertext and never gets the key. Only someone with the key, normally the recipient, can decrypt it.
Zero-knowledge describes the same idea from the provider's side: it has zero knowledge of your keys and therefore of your file contents. It rarely means the provider knows nothing. Account emails, file sizes, timestamps and on many services file names are still visible, because the service needs them to work.
How the key can travel in the link
A share link can carry the decryption key without the server ever seeing it. RocketShare links look like this:
https://rocketshare.app/d/abc123#k3Y-mAt3r1aL...
Everything before the # is sent to the server, which uses abc123 to find the encrypted files. Everything after the # is the URL fragment. Browsers keep the fragment on the device and don't include it in requests to the server; this is how URLs have worked since the URL standard (RFC 3986). The recipient's browser reads the key from the fragment and decrypts the files locally.
The trade-off is simple: the link is the key. Anyone with the full link can open the files, and if the link is lost, nobody can recover them. Send it only to the intended recipient, through a channel you trust.
What AES-256-GCM does
AES is the encryption standard used by governments, banks and the TLS connection your browser is using right now. The "256" is the key length in bits. Guessing a random 256-bit key by brute force is not feasible with any computer that exists.
GCM (Galois/Counter Mode) adds authentication. Each encrypted chunk carries a tag, and if anyone changes even one byte of the ciphertext, decryption fails instead of producing a corrupted file. That protects against tampering as well as reading.
RocketShare uses AES-256-GCM through the browser's built-in Web Crypto API. Each transfer gets a fresh random key, and each chunk of a file gets its own random 96-bit IV. Encrypting in chunks means multi-gigabyte files never have to fit in memory. The security whitepaper has the details.
Which services encrypt files end to end
As of November 2026, based on each provider's own documentation. Plans and features change; check the provider before relying on a row.
| Service | How file contents are encrypted | Who holds the keys | File names encrypted |
|---|---|---|---|
| RocketShare | End-to-end in the browser, AES-256-GCM, every plan | Sender and recipient (key in the link) | No |
| WeTransfer | TLS 1.2/1.3 in transit, AES-256 at rest | WeTransfer, on standard plans | No |
| Google Drive | AES-256 in transit and at rest; client-side encryption only on Workspace Enterprise Plus and Education Standard/Plus | Google, unless client-side encryption is set up by an admin | No |
| Dropbox | AES-256 at rest; end-to-end encrypted team folders on Advanced, Business Plus and Enterprise | Dropbox, except in encrypted team folders | No (Dropbox says metadata stays readable even in encrypted folders) |
| SwissTransfer | AES-GCM in transit, LUKS and AES-256 at rest on Infomaniak's servers | Infomaniak | No |
| Proton Drive | End-to-end, OpenPGP | The user | Yes, file and folder names |
| Tresorit | End-to-end, AES-256 | The user | Yes for files; reports differ on top-level folder names (uncertain) |
| Wormhole | End-to-end in the browser, AES-128-GCM | Sender and recipient (key in the link) | Yes, metadata is encrypted |
A few notes on the table:
- "End-to-end" is sometimes used loosely in marketing. If a page says "end-to-end" but the technical docs only describe TLS and encryption at rest, the provider holds the keys. Look for where the key is created and whether it ever reaches the server.
- Proton Drive and Tresorit are storage products. They encrypt more metadata than RocketShare and have published audits or certifications, but they are built for keeping and syncing files, with apps to install. See RocketShare vs Proton Drive and RocketShare vs Tresorit.
- Wormhole is the closest design to RocketShare. Both put the key in the link fragment. Wormhole also encrypts file names; RocketShare keeps links for longer and has paid plans. See RocketShare vs Wormhole.
- Google Drive, Dropbox, WeTransfer and SwissTransfer are well run and secure against outside attackers, but by default the provider can decrypt your files. See RocketShare vs WeTransfer, vs Google Drive, vs Dropbox and vs SwissTransfer.
What end-to-end encryption doesn't protect
E2EE solves one problem well: the provider can't read your files. It does not solve everything.
- Metadata. RocketShare encrypts file contents but stores file names, folder paths, sizes, the message to the recipient and email addresses unencrypted. Name files neutrally if the name is sensitive.
- The link itself. Whoever has the full link has the key. A forwarded email is a forwarded key.
- Optional email delivery. If you let RocketShare email the link for you, the key passes through our servers once to send the message. It is not stored, but sharing the link yourself keeps the key off our servers entirely.
- Infected devices. Malware on the sender's or recipient's computer can read files before encryption or after decryption.
- Trust in the code. In a browser-based service, the web page does the encryption, so you trust the code the server sends. RocketShare's code is not open source and has no published independent audit yet.
For a practical checklist on passwords, expiry and download limits, read secure file transfer.
Try encrypted file sharing with RocketShare
Open rocketshare.app and drop in files or a folder. No account is needed for up to 2 GB per transfer with a 3-day link. A free account gives 4 GB and 10 transfers per month, with a password, a download limit and links of up to 7 days. Paid plans start at $7 per month for 350 GB; see pricing. Files are stored encrypted in Amsterdam and deleted when the link expires.
For two devices on the same Wi-Fi, Local share sends files directly between browsers over an end-to-end encrypted connection, with nothing uploaded. File names are encrypted there too.