Every storage plan says it encrypts your files. Where that encryption happens decides whether the provider can read them, and whether a forgotten password costs you everything.
Every cloud storage service seems to advertise encryption, which makes it easy to assume they all protect your files the same way. They do not. The word covers at least three different arrangements, and the one a provider uses determines whether the company can read what you store, lose it in a breach, or hand over readable copies under legal pressure. Here is what each arrangement actually means, in plain language, before you pay for a plan.
Encryption in Transit, at Rest, and End to End
Start with the basic operation. Encryption, as the National Institute of Standards and Technology defines it, transforms readable data, called plaintext, into a scrambled form called ciphertext, and decryption reverses the process for anyone holding the right key. Every flavor of cloud encryption uses that same operation. The differences come down to where it happens and who holds the key.
Encryption in transit protects data only while it moves. When your app connects to a storage service over an encrypted channel such as TLS, the traffic crossing the network is unreadable to eavesdroppers. The FTC describes the https arrangement on websites as the sign that information you provide is encrypted as it is transmitted. But the protection ends at the server. The data arrives unencrypted on the provider’s systems, and it also sits unencrypted on your own device.
Encryption at rest covers the stored copy. The provider scrambles files on its disks so that a stolen drive or a leaked backup archive is useless without the keys. The catch is that this defends against passive access. If an attacker gains active control of a running server, the keys the system needs for daily operation are often right there and can be taken along with the data.
End-to-end encryption moves the transformation all the way back to your device. NIST defines it as encryption in which data stays encrypted while passing through a network, though routing information remains visible. In practice, your app encrypts a file before it leaves, the ciphertext crosses the network and sits on the provider’s servers in scrambled form, and only a device holding the right key can turn it back into something readable. Germany’s federal IT security agency summarizes the effect: you need to trust only the endpoints of the communication, not the servers in between.
What the Provider Can See in Each Case
The three arrangements answer one question differently: can the operator of the service read your files?
| Arrangement | Encrypted on your device before upload? | Provider can read contents? | What the provider still sees |
|---|---|---|---|
| In transit only | No | Yes, once data arrives | File names, sizes, contents, previews |
| In transit plus at rest | No | Yes, when the provider holds the keys, the usual setup | File names, sizes, previews, search indexes |
| End to end | Yes | No | Metadata: connections, storage amounts, sharing activity |
Even a well-built end-to-end system leaks patterns. NIST’s definition notes that routing information remains visible, and metadata such as how much you store and with whom you share stays available to the service. That metadata is far less sensitive than file contents, but it is not nothing.
End-to-end systems also tend to lean on asymmetric encryption, a pair of keys where one key encrypts and only its private partner decrypts. To share a file, your app can encrypt a copy with the recipient’s public key, so only their private key can open it. Symmetric schemes use a single shared key instead, and many systems combine the two, using asymmetric methods to agree on a shared key.
A Worked Example: One Folder, Two Plans
This example is an illustration of how the arrangements differ, not a description of any specific provider. Suppose you scan a folder of tax records, upload it, and share it with your accountant.
On a standard plan, the app opens an encrypted connection and sends the files. The provider’s servers store them, and because the provider holds the encryption keys, its own software can generate thumbnail previews, search text inside documents, and produce the files in response to a legal demand. A thief who steals a hard drive from a data center walks away with ciphertext. The provider itself holds plaintext.
On a zero-knowledge plan, the app encrypts each file on your device with a key derived from your password, and only the scrambled result is uploaded. The provider stores ciphertext it cannot open. Previews and in-file search stop working or require awkward workarounds, since the server cannot see what it is storing. When you share the folder, your app encrypts the files with your accountant’s public key instead of ever revealing your own.
What Zero-Knowledge Means for Your Password
Zero-knowledge describes an architecture, not a bolt-on feature. The service is built so that the key that opens your data exists only on your side of the connection; the company running the servers never receives it. Reviewers often use the terms zero-knowledge encryption and client-side encryption interchangeably, since both mean data is scrambled on your device before upload.
The consequences cut both ways. The provider cannot read your files, cannot accidentally expose them in readable form, and cannot surrender readable copies, because it never had them. An attacker who breaches the servers gets ciphertext. On the other side of the ledger, everything now depends on a secret only you hold, usually your password or a key derived from it.
Before paying for a plan advertised this way, check two details. Coverage: some providers apply client-side encryption to an entire account, while others protect only one special encrypted folder and leave the rest of the account on ordinary encryption. Jurisdiction: the country a provider is incorporated in and the locations of its servers determine which data protection laws it must follow.
Because the password effectively becomes the key, how you store and back it up matters as much as the service itself. Our guide to what to check before you install a password manager covers the questions to ask of whatever tool ends up holding it.
The Recovery Trade-Off When You Forget
Standard accounts come with a safety net: click forgot password, confirm your email, choose a new one. A zero-knowledge service usually cannot offer that, because the password is part of what decrypts the data and the provider never had it. Forget it, and the company has no way to restore your files, no matter how many years you have paid. The limit binds outsiders too. Even law enforcement with a warrant cannot compel a properly implemented end-to-end service to produce readable contents.
That is the bargain in miniature. Nobody else can read your files, including the people you might one day need help from. Decide before signing up how you will handle the key: a recovery code the service lets you save offline, a trusted family member who knows the arrangement, or an accepted risk. It is also worth thinking about keys and accounts after death, which our guide to what happens to your online accounts when you die covers.
Watch for
If a service advertises zero-knowledge encryption, assume its password reset will not save you. Set up whatever recovery option it offers right away, and store the recovery code somewhere separate from the password it recovers.
One more limit to keep in view. End-to-end encryption protects stored data and data in motion, but it cannot protect a device that is already compromised. Someone controlling your computer or phone can read files after decryption, keys included.
How to Read a Provider’s Security Claims
Marketing pages compress all of this into phrases like encrypted cloud storage, and the phrases outrun the standards. There is no universally accepted technical definition of end-to-end encryption. An effort at the Internet Engineering Task Force to define the term has been underway, and its output has carried only informal status. That gap leaves room for claims that sound stronger than they are.
A few questions cut through the wording:
- Where does encryption happen? If files are encrypted on your device before upload, that is client-side encryption, the arrangement behind genuine zero-knowledge claims. If encryption happens on the provider’s servers, you are looking at ordinary at-rest protection.
- What does it cover? A whole account, or a single encrypted folder with the rest of the account left on standard encryption?
- Who holds the keys? A provider that can reset your password, restore your access, or generate previews must hold usable keys by definition.
- What happens if you forget the password? The honest answer from a true zero-knowledge service is that the files are unrecoverable.
- Where are the servers, and which country’s laws apply to them?
- Is the implementation open to inspection? Published security audits or open-source client software let a claim be checked rather than taken on faith.
The baseline matters as well. An encrypted connection to a service, the https the FTC points to, is standard practice now rather than a distinguishing feature. Any provider still without it fails a far lower bar than the one you should be applying.
Where End-to-End Encryption Fits in a Backup Plan
End-to-end encryption solves a confidentiality problem, not a data-loss problem. Your encrypted cloud copy lives on someone else’s servers and on your own devices, and a sync-style service will mirror whatever your devices do, deletions included. A complete backup setup still needs at least one copy on separate storage the internet cannot touch, and it needs restore tests, because a copy you have never restored is not yet proof of anything.
The encryption choice changes what the cloud copy is worth. With standard encryption, the copy is convenient but readable by the provider. With zero-knowledge, the copy is private but hinges on one password, so your backup plan has to include your recovery plan. Used with eyes open, end-to-end encryption lets you keep sensitive documents off-site without trusting the storage company with their contents.
If you are assembling that setup, our timeline for setting up your first cloud backup walks through the order of operations, and our guide to how much cloud storage you actually need helps you figure out how much space your household really requires before the encryption question even comes up.
The essentials
- Encryption in transit protects files only while they travel; the provider stores, and can generally read, them once they arrive.
- End-to-end, also called zero-knowledge, encryption happens on your device, so the provider holds only ciphertext and never your key.
- The trade-off is recovery: a zero-knowledge provider usually cannot reset a forgotten password, so plan for that before you sign up.
- Some providers apply client-side encryption to one folder only, and a provider’s server locations determine which laws apply.
- End-to-end encryption protects confidentiality, not backups: keep a separate copy on other storage and test that restores work.
Reader questions
Does an https connection mean my cloud files are end-to-end encrypted?
No. An https connection encrypts data in transit only. Files arrive unencrypted on the provider’s servers, which is the opposite of end-to-end protection.
Can my cloud storage provider read my files?
With standard plans, generally yes, because the provider holds the keys it needs for previews, search, and account recovery. Zero-knowledge providers build their systems so they cannot.
What happens if I forget my zero-knowledge password?
The provider typically cannot decrypt your files or restore access, since it never held the key. Use any recovery code the service offers and store it somewhere safe and offline.
Can law enforcement get the contents of my encrypted cloud storage?
A provider using real end-to-end encryption can hand over only ciphertext, which even a warrant cannot turn into readable files. Standard-plan providers can produce plaintext contents.
We describe how services generally work; features, settings and terms change often, and they differ between companies. This is general information, not legal advice. Check the provider’s current policies and official sources such as FTC.gov.