Insights

End-to-end encrypted file sharing: what it protects and what to check

Learn how end-to-end encrypted file sharing works, who can read your files, and how to check encryption for your sharing workflow.

Illustration of external drive with removable hardware key.
On this page

End-to-end encrypted file sharing encrypts a file on your device and decrypts it on the recipient's device. The service that carries or stores it can't read its contents without the decryption key. To choose a suitable method, check where encryption happens, who controls the keys and whether it covers the sharing feature you'll use.

In short:

  • Device boundaries. Files stay encrypted between your device and the recipient's device.
  • Key control. The service can't read the contents without the decryption key.
  • Check the feature. A plan-level label doesn't confirm end-to-end encryption for every sharing workflow.

Who can read your files

The encryption boundary in end-to-end encryption (E2EE) runs from the sender's device to the recipient's device. Plaintext is the readable content, while ciphertext is its encrypted form. A decryption key is the secret used to turn ciphertext back into readable content.

Hypothetical example: You send a private document through a storage server. Your device encrypts it before upload, and the recipient's device uses the key to decrypt it. The server can store the encrypted file without reading its contents because it doesn't have the key.

E2EE can work through a server, so a direct device-to-device connection isn't required. A direct connection alone doesn't prove E2EE. What matters is where encryption and decryption happen, and who can get the keys.

How other encryption differs

Encryption in transit protects a connection, often using Transport Layer Security (TLS). Encryption at rest protects a stored copy of a file.

These models differ in where protection applies and whether the model alone excludes provider access.

Encryption modelProtection boundaryProvider access
In transitBetween connection endpointsNot excluded by this model alone
At restStored file copyNot excluded by this model alone
End to endSender device to recipient deviceExcluded when the provider lacks decryption keys

A service can encrypt its connections and storage while still holding the keys needed to read your files. Transit and storage encryption can also coexist with E2EE. Neither label alone tells you who controls the keys.

What to check before you send

Check the sharing feature, not just the provider's encryption label. Dropbox's Transfer page lists end-to-end encryption as a plan feature, but that listing alone doesn't establish its scope for Transfer. FileCloud's file-transfer page describes encryption at rest and in transit, which alone doesn't establish endpoint-only key control.

Use your intended sharing workflow and its feature-specific documentation for this checklist. Record each answer and the passage that supports it.

  1. Name the exact feature. Record whether you're sending a download link, sharing a folder or transferring directly between devices. Find documentation for that feature, not just the plan or service.

  2. Check where encryption happens. Look for encryption on your device before upload and decryption on the recipient's device. Encryption that starts only after the file reaches the service doesn't meet that boundary.

  3. Check who can decrypt. Record who holds the keys and whether the service can read the file. Check how the recipient gets the key or secret link. Mark missing answers unconfirmed instead of assuming the feature is either protected or unprotected.

  4. Check whether you must enable it. In Filemail's documented workflow, you enable E2EE and enter a key before transfer. Its instructions say that the key encrypts the files before the transfer begins. Don't assume the right setting is on for every send.

  5. Protect access-bearing links and passwords. As an architecture example, blindsend's documented design lets anyone possessing the link decrypt the files, with a password also required when one is set. Treat that link as a secret, not just an address. Where a separate password is supported, share it through a different secure channel, such as in person.

  6. Send a harmless sample first. Confirm that the intended recipient can open a file with no private content. That proves delivery and recipient access, not that the cryptography is secure. If access fails, check the link, key or password and required settings before sending sensitive content.

Decision rule: Treat E2EE as documented for your workflow only when the instructions confirm endpoint encryption and explain why the service can't decrypt the file. If an answer is unconfirmed, get feature-specific documentation before relying on that claim. Clear documentation and a working sample aren't a security audit.

What encryption doesn't protect

E2EE doesn't protect readable data on a device that's already compromised. Malware on the sender's or recipient's device can expose the content. Once the recipient decrypts a file, E2EE doesn't stop them from copying or sharing it.

Leaking an access-bearing link or key can also expose the file. Content encryption doesn't by itself hide file names, sizes, addresses, timing or access records. Don't treat E2EE as proof of anonymity or no logs.

In FileSender's documented workflow, expiry stops later downloads. It doesn't remove copies a recipient has already downloaded. Filemail says that if you lose or forget your encryption key, neither you, the recipient nor Filemail can decrypt the files. Check your chosen workflow's recovery rules instead of assuming they match that example.

Where doxx.net fits. doxx.net offers direct device-to-device connections and full, unmodified file transfer, but its documented E2EE chat doesn't establish E2EE for file transfers. To try its private network, create a doxx.net account, download the app and connect a device.

Ask an AI assistant

Share this article

Private Everywhere

Stop giving the internet everything

Keep your browsing, messages, files, and agents private.