The short answer
No. Dropbox is not end-to-end encrypted by default. Your files are encrypted at rest with AES-256 and in transit with TLS, but Dropbox holds the keys. So Dropbox can read your files, decrypt them after a breach, and hand them to a court when compelled. Encrypted, yes. Private from Dropbox, no.
What Dropbox actually encrypts
Dropbox runs the standard security model, and it's worth describing accurately rather than dismissing. Files sitting on Dropbox's servers are encrypted with 256-bit AES. Data moving between your device and Dropbox rides through a TLS tunnel. Both are real protections — the first against a thief who walks off with a drive, the second against someone sniffing the open Wi-Fi at a café.
Neither protects you from Dropbox. The keys that decrypt your AES-256 blocks live on Dropbox's infrastructure, managed by Dropbox. That's server-side encryption: the provider encrypts your data, and the provider can turn around and decrypt it. Picture a locked box. In one version you keep the only key; in the other, the storage company keeps a copy and promises not to open it. Dropbox runs the second box.
Why "Dropbox holds the keys" matters
Key custody isn't an abstraction. When a court compels Dropbox to produce your files, Dropbox can comply, because it can decrypt them — its transparency reports document exactly this traffic of requests in and data out. A provider that genuinely couldn't read your files would have nothing to hand over. The same custody bites on breaches: Dropbox has been broken into before, and the 2012 incident eventually surfaced credentials for around 68 million accounts. Under server-side encryption, an attacker who reaches the keys reaches your plaintext. Under end-to-end encryption, that same attacker walks away with ciphertext they can't open. Server-side decryption is also what makes full-text search, web previews, and AI features possible at all — convenient, and only possible because Dropbox can see inside your files.
What about Dropbox's encrypted folders?
Dropbox does offer genuine end-to-end encryption, and fairness demands naming it. In its 2024 Spring release Dropbox shipped encrypted team folders: only folder members hold the key, and Dropbox is excluded. That's real zero-knowledge encryption, built in natively.
The caveats are where it gets honest. It's limited to Business Plus, Advanced, and Enterprise — not personal Plus or Professional. It's opt-in, never the default. And switching it on disables features, including sharing files with anyone outside your team. For the overwhelming majority of Dropbox accounts — every personal plan, plus any team that hasn't deliberately flipped the switch — files sit under server-side encryption that Dropbox can read.
The AI-training question
In late 2023 Dropbox took heavy criticism when users found a "third-party AI" setting toggled on by default, wired to its Dash and AI-search features. The fear was that personal files were being routed to OpenAI as training data. CEO Drew Houston pushed back: the toggle doesn't passively send anything, third-party AI is invoked only when you actively use a labeled AI feature, and any data sent is deleted within 30 days.
Take that account at face value — the structural point survives it. This debate is only possible because Dropbox can read your files. Under true end-to-end encryption the question never forms, because a provider can't ship to an AI model what it can't decrypt. The argument over toggles and defaults is a downstream symptom of who holds the keys.
What zero-knowledge does instead
Zero-knowledge encryption moves the keys off the server entirely. Your data is encrypted on your device, with keys derived from a passphrase that never leaves it. The server stores ciphertext and nothing that can decrypt it. A subpoena lands, the provider hands over encrypted blocks, and the blocks are useless without your key. There's no AI toggle to argue about, because there's nothing readable to train on in the first place.
That's the model Beebeeb's architecture is built on. Your passphrase runs through Argon2id (256 MB, 4 iterations), file keys are wrapped with X25519, content is sealed with AES-256-GCM, and key material is zeroized from memory after use. The encryption applies on every tier, including the free one — zero-knowledge isn't a business-plan upsell here. We can't read your files, which is also why we can't recover them if you lose your recovery code. We say that out loud because it's the honest cost of a design where only you hold the key.
Common follow-ups
Can Dropbox see my files? Yes. On personal plans and standard team folders, Dropbox holds the keys and can decrypt your content.
Is Dropbox zero-knowledge? No — except inside opt-in encrypted team folders on Business Plus, Advanced, or Enterprise.
Can Dropbox hand my files to the government? Yes, when legally compelled. It can decrypt them to comply.
Is Dropbox still safe? For convenience and resilience against outside attackers, it's a solid product. For files you don't want the provider — or anyone the provider answers to — able to open, server-side encryption is simply the wrong model.
If you want files Dropbox can't read
Dropbox's encryption is real; the limitation is custody. If your threat model includes the provider itself — subpoenas, breaches, AI pipelines — you need encryption that happens before your data reaches the server, with keys only you control. We wrote a point-by-point look at how a zero-knowledge alternative stacks up against Dropbox, including the cases where Dropbox is still the better pick. Data lives on dedicated servers in Falkenstein, Germany, and the product clients are open source.