Security Deep Dive

Zero-Knowledge File Transfer: What It Is and When You Need It

Zero-knowledge means the service provider cannot access your files, even if compelled by law. Here's how it works and whether you need it.

What zero-knowledge actually means

The term gets thrown around loosely in marketing. Here's what it means precisely.

In a zero-knowledge architecture, files are encrypted on the client's device before they are uploaded to the server. The encryption key never touches the server. The provider stores only encrypted data that they literally cannot decrypt, because they never had the key in the first place.

This is the strongest privacy model available for cloud-based file transfer. Even if the provider is hacked, served with a subpoena, or compromised by a malicious employee, your files remain encrypted with a key the provider never possessed.

The "zero-knowledge" part refers to what the provider knows about your data: nothing. They can see file sizes, timestamps, and metadata, but the actual content of your files is mathematically inaccessible to them.

How zero-knowledge encryption works

A simplified look at the technical flow, no cryptography degree required.

Key generation

Your device generates a unique encryption key. This key is created locally and never leaves your device (or is derived from a password only you know).

Local encryption

Your files are encrypted on your device using that key before anything is uploaded. The server never sees the unencrypted data.

Encrypted upload

The encrypted data is transmitted to the server over TLS. The server stores encrypted blobs it cannot read. It has no way to decrypt them.

Key stays with you

The encryption key remains on your device or is shared directly with your recipient (often via a link fragment that the server never sees). The provider is never in the loop.

Zero-knowledge file transfer tools

If you've determined you need true zero-knowledge file transfer, these are reputable options.

Tresorit

Zero-knowledge

True zero-knowledge architecture built from the ground up. Files are encrypted client-side before upload, and Tresorit never has access to your encryption keys. Swiss jurisdiction adds legal privacy protections. Designed for businesses with strict compliance requirements.

From $14/user/mo

SendSafely

Zero-knowledge

Client-side encryption with an API-first approach. Files are encrypted in the browser before upload, and encryption keys are embedded in the link fragment (never sent to the server). Good for developers who need to integrate secure file exchange into existing workflows.

From $30/user/mo

SpiderOak

Zero-knowledge

Zero-knowledge cloud backup and storage. Your data is encrypted locally before it leaves your device, and SpiderOak cannot access your files or passwords. Focused on backup and sync rather than file delivery.

From $6/mo (personal)

Keybase (now Zoom)

End-to-end encrypted

End-to-end encrypted file sharing and messaging. Open-source cryptography. Since the Zoom acquisition, the long-term direction of the product is uncertain, but the existing file sharing functionality remains strong.

Free

The trade-offs of zero-knowledge

Zero-knowledge is the strongest privacy model, but strength comes with real costs. Be honest about what you're giving up.

No password recovery

If you lose your encryption key or password, your data is gone. The provider cannot help you because they never had your key. There is no "forgot password" for your encrypted files.

No server-side processing

The server cannot read your files, which means no server-generated thumbnails, no full-text search, no automated virus scanning, and no content-based workflows. The server sees only encrypted blobs.

Key management complexity

Someone has to manage encryption keys. In zero-knowledge, that someone is you (or your client). This adds friction, especially for non-technical users who just want to upload a document.

Limited collaboration features

Features like payment gates, server-side audit trails, automated expiration enforcement, and admin oversight require the server to have some level of access or control. Zero-knowledge limits what the platform can do on your behalf.

When zero-knowledge matters most

There are real situations where zero-knowledge is the right, or only, choice. If any of these apply to you, prioritize zero-knowledge architecture.

✓Attorney-client matters involving active litigation against a government entity
✓Whistleblower protection where the platform itself could be compelled to produce data
✓National security or intelligence contexts
✓Situations where you fundamentally do not trust any third-party provider
✓Journalism involving sources who face physical danger if identified
✓Political dissidents communicating under authoritarian regimes

When it's not necessary

For most professional document delivery, server-managed encryption with strong access controls and cryptographic erasure provides practical security without the usability costs.

–Routine tax document delivery between a CPA and their clients
–Legal document exchange for standard transactions (closings, contracts, filings)
–Financial statements shared between advisors and clients
–Insurance documents, medical records for standard professional use
–Any situation where server-side features (audit trails, auto-expiration, payment gates) are more valuable than zero-knowledge privacy

Honest comparison: zero-knowledge vs. DeadVault's model

DeadVault uses AES-256-GCM with per-file keys, but the server manages those keys. That's not zero-knowledge. Here's exactly how the two models differ.

	Zero-Knowledge	DeadVault
Who holds encryption keys	You (the user)	Server (per-file keys, wrapped with master key)
Can provider read your files	No, never	Technically possible (server manages keys)
Password recovery	Impossible	Standard account recovery
Server-side audit trails	Limited (server can't see content)	Full access logging
Automatic expiration	Possible but key management is client-side	Server-enforced with cryptographic erasure
Payment gates	Not possible (server can't gate decrypted content)	Built-in
Client setup required	Often requires key exchange or account setup	Simple link, no account needed
Response to subpoena	Provider can hand over encrypted blobs they cannot decrypt	Provider could technically decrypt if keys exist (keys are destroyed on expiration)

Neither model is universally "better." They serve different threat models and use cases.

Frequently asked questions

Honest answers about zero-knowledge encryption and where DeadVault fits.

No. DeadVault is not zero-knowledge and we will not claim otherwise. DeadVault uses AES-256-GCM encryption with per-file keys, but the server manages those keys. This means DeadVault could technically access your files while they exist on the platform. The security model relies on cryptographic erasure: when a box expires, the encryption keys are destroyed, making the files permanently unrecoverable. This is a different security model than zero-knowledge, designed for a different set of priorities.

No. Zero-knowledge provides stronger privacy guarantees, but it comes with real trade-offs: no password recovery, no server-side features (audit trails, automated workflows, payment gates), and more complexity for end users. For most professional document delivery, where you need audit trails, automatic expiration, and client simplicity, server-managed encryption with strong access controls is the more practical choice. The "best" model depends entirely on your threat model.

This is technically possible but complex. You would need a system that handles client-side encryption (so the server never has keys) combined with automatic deletion of encrypted blobs on a schedule. Tresorit offers some expiration features with zero-knowledge encryption. For true zero-knowledge with guaranteed destruction, you may need to manage key destruction on your own devices. DeadVault chose server-managed keys specifically to make cryptographic erasure reliable and automatic.

Yes, a zero-knowledge provider can be served with a subpoena or court order like any other company. The difference is what they can hand over. A true zero-knowledge provider can only provide encrypted data they cannot decrypt. They literally do not have the keys. However, they may still have metadata: who created an account, when files were uploaded, IP addresses, file sizes. Zero-knowledge protects file contents, not necessarily all metadata.

Several layers: per-file encryption keys (not a single key for all files), key wrapping with a master key, access controls on each box (PIN protection, link-based access), audit logging of all access events, TLS for all data in transit, and, most importantly, automatic key destruction when boxes expire. The window of theoretical vulnerability exists only while the box is active. After expiration, cryptographic erasure makes the files permanently unrecoverable regardless of who has access to the storage.

If your primary requirement is that no third party, including your file transfer provider: can ever access your documents under any circumstances, then yes, you should use a zero-knowledge tool like Tresorit or SendSafely. If your priorities are client simplicity (no accounts or key management), server-enforced expiration and destruction, audit trails, and professional document delivery workflows, DeadVault is designed for that use case. Many professionals use both: zero-knowledge tools for their most sensitive matters, and tools like DeadVault for routine secure document delivery.

DeadVault isn't zero-knowledge.

It's server-managed encryption with cryptographic erasure, a different security model designed for professional document delivery. Your files are encrypted with AES-256-GCM using per-file keys, and those keys are destroyed when your box expires.

If you need true zero-knowledge, we've listed tools above that provide it. If you need secure, simple document delivery with automatic destruction and audit trails, that's what DeadVault does.

Try DeadVault free How our encryption works