What zero-knowledge encryption actually means for your files
Most cloud services say your files are “encrypted.” Technically true — and also close to meaningless on its own. The question that actually matters is: who holds the key?
Zero-knowledge encryption is the answer where the only person who can unlock your files is you. This article explains what that means in plain terms, why it’s different from the encryption most clouds use, and the single trade-off that comes with it.
Encryption isn’t one thing
There are three common levels, and they are not equal:
- Encryption in transit — your data is scrambled while it travels between your device and the server (this is what HTTPS does). Necessary, but it says nothing about what happens once the file lands.
- Encryption at rest — the file is stored scrambled on the provider’s disks. This protects against someone stealing the physical drives. But the provider holds the keys, so it can decrypt your files at any time.
- End-to-end / zero-knowledge — the file is encrypted on your device, with a key only you have, before it’s ever uploaded. The provider only ever stores unreadable ciphertext.
Ordinary cloud storage — including standard Google Drive and Dropbox — uses the first two. Zero-knowledge services use the third.
What “zero-knowledge” really promises
Zero-knowledge means the provider has zero knowledge of your file contents. Concretely:
- The company cannot read your files, even internally.
- A data breach exposes only ciphertext, which is useless without your key.
- A legal demand can only hand over scrambled data — the provider physically can’t produce the plaintext.
That’s a categorically stronger guarantee than “we promise not to look.”
How it works under the hood
The mechanics are simpler than they sound:
- Your password is put through a slow, memory-hard function (Ambry uses Argon2id) to derive your keys. This happens on your device and the password never leaves it.
- That produces a keypair — a public key the server can hold, and a private key that stays on your device.
- Every file gets its own random key, which is then locked with your public key. Only your private key can unlock it.
- The file — and its name and thumbnail — are encrypted with strong ciphers (Ambry uses XChaCha20-Poly1305) before upload.
If you want the full technical breakdown, see how Ambry protects your files.
The one trade-off: no password recovery
Here’s the honest catch. If the provider can’t read your files, it also can’t reset your password for you — because your password is what derives your keys. There is no “forgot password” link that can recover your data, because doing so would mean the provider had a back door all along.
This is a feature, not a bug: it’s the very thing that makes the encryption trustworthy. The practical takeaway is simple — store your master password in a password manager, and treat it as the one thing you must not lose.
Do you need it?
Not for everything. A shared grocery list doesn’t need zero-knowledge encryption. But for personal photos, financial documents, IDs, and anything you’d be uncomfortable a stranger reading, it’s the difference between “probably safe” and “provably private.”
If you’d like that guarantee on storage you already own, Ambry encrypts your files on your device and stores them in your own Google Drive — so the space stays familiar, but the privacy is real. See how it compares to Proton Drive, or read the security overview.