When you upload a file to a cloud storage service, the service typically encrypts it on their servers. This protects the file from outside attackers who might try to breach the storage infrastructure. It doesn’t protect the file from the storage company itself, from their employees, from legal requests, or from their AI systems that may scan or analyze your content.
Client-side encryption works differently. The file is encrypted on your device before it’s uploaded. The cloud service receives an encrypted blob it can’t read. The encryption key never leaves your device. This is a meaningfully stronger model for personal privacy — and it’s available for free with tools that have been battle-tested for years.
The Difference That Matters: Who Holds the Key
The core concept in file encryption is key management. Encryption converts your readable file into scrambled data using a mathematical key. The key is what allows decryption back to the original. Whoever controls the key controls access to the content.
In standard cloud storage encryption, the service generates and manages the encryption keys. This is called server-side encryption. Your file is encrypted, but the key is held by the company. The company (and anyone with legal authority over it) can decrypt your files.
In client-side encryption, you generate the key on your device. The file is encrypted before upload. The cloud service sees only the encrypted version. Even if the company wanted to read your file, they couldn’t — they don’t have the key.
The difference is especially relevant for:
- Financial documents (tax returns, investment records, bank statements)
- Medical and health records
- Legal documents (contracts, estate planning, sensitive correspondence)
- Personal journals, diaries, notes
- Creative work you don’t want exposed before it’s ready
- Documents involving other people who didn’t consent to their content being stored unencrypted in someone else’s cloud account
Cryptomator: The Most Practical Tool for Most People
Cryptomator is an open-source client-side encryption tool designed specifically for cloud storage. It’s available on Windows, macOS, Linux, iOS, and Android. The desktop version is free; the mobile apps have a small one-time purchase price. The source code is publicly available on GitHub and has been audited by independent security researchers.
The design philosophy is deliberate simplicity: you create a “vault” (an encrypted folder), point it at a folder inside your Dropbox, Google Drive, OneDrive, or any other cloud storage directory, set a password, and anything you put in the vault is encrypted before it syncs to the cloud.
From the cloud service’s perspective, your vault looks like a folder full of encrypted files with randomized names. The file structure, file names, and file contents are all protected. Someone looking at your synced files in Dropbox can see that encrypted data exists. They cannot read it without the vault password.
How to Set Up a Cryptomator Vault
Step 1: Download and install Cryptomator. Get it from cryptomator.org. Verify the download signature if you’re familiar with how to do that — the site provides checksums and GPG signatures.
Step 2: Create a vault inside your cloud storage folder. Open Cryptomator, click “Add Vault” → “Create New Vault.” Navigate to a location inside your cloud-synced folder (your Dropbox, Google Drive, or similar). Give the vault a name that doesn’t reveal its purpose to anyone looking at your file list.
Step 3: Set a strong passphrase. This is the most important step. Use a randomly generated passphrase from a password manager, or at minimum a passphrase with four or more unrelated words. Write it down and store it somewhere physically secure — if you lose the passphrase, you lose access to the vault permanently. There is no recovery mechanism.
Step 4: Unlock the vault. When you open Cryptomator and unlock a vault with your passphrase, it appears as a virtual drive on your computer. You can drag files into it, open them, edit them, and save them exactly as you would any other folder. When you lock the vault (or close Cryptomator), the drive disappears and the files are only accessible in encrypted form.
Step 5: Sync normally. Your cloud storage client (Dropbox, Google Drive, etc.) syncs the encrypted vault files to the cloud. You don’t need to change anything about how you sync. The encryption happens before the files reach the sync layer.
What Cryptomator Protects and What It Doesn’t
It’s important to understand the limits of what client-side encryption provides.
Cryptomator protects:
- File contents from your cloud provider
- File contents from cloud provider employees
- File contents from legal requests to the cloud provider
- File names (Cryptomator randomizes these in the cloud)
- File and directory structure (the organization of files within the vault)
Cryptomator does not protect:
- The fact that encrypted data exists in your cloud storage (this is visible)
- The file count or approximate size of the vault (inferable from the encrypted files)
- Files you’ve already uploaded without encryption (these are unaffected)
- Your passphrase if someone has access to your device and you’ve unlocked the vault
- Files if someone gets your Cryptomator passphrase
The protection is specific: it means your cloud provider cannot read the encrypted files, cannot analyze them for AI training, cannot hand them to a government with a standard legal request, and cannot expose their contents in a data breach affecting the cloud storage layer.
VeraCrypt: For Offline Archives
Cryptomator is optimized for files you’re actively syncing to cloud storage. For offline archives — large volumes of sensitive data you want to store securely on a hard drive, USB drive, or encrypted container file — VeraCrypt is the standard tool.
VeraCrypt creates encrypted containers or full-disk encrypted volumes. The setup is more complex than Cryptomator, and mistakes during full-disk encryption can result in data loss. For most personal file encryption use cases, Cryptomator is the right starting point. VeraCrypt is worth learning if you’re storing sensitive archives offline or on external drives.
Key differences:
- Cryptomator: file-by-file, cloud-optimized, simpler setup
- VeraCrypt: volume-level, offline-optimized, more complex but more flexible
Encrypting Files Before Other Cloud Storage
Cryptomator works with any folder that syncs to cloud storage. This means you can use it with virtually any cloud service, including services that already provide their own encryption:
- Dropbox
- Google Drive
- OneDrive
- iCloud Drive
- Box
- pCloud
- daftei (you can create a vault inside any folder that syncs with daftei)
Using client-side encryption on top of a service that already provides server-side encryption is redundant for most threat models — but it’s a reasonable choice if you’re storing particularly sensitive documents and want protection that doesn’t depend on the cloud provider’s key management.
For most people, the practical choice is simpler: use a service you trust with reasonable server-side encryption for general file storage, and use client-side encryption for the small subset of files that are genuinely sensitive.
A Note on Mobile
Cryptomator’s mobile apps (iOS and Android) allow you to access your vault on mobile. The experience is functional but less seamless than on desktop: you unlock the vault within the Cryptomator app, browse files from there, and open them in supported apps.
The mobile implementation is an important consideration if you need to access encrypted files from your phone regularly. For files you primarily access from a desktop and only occasionally need on mobile, the workflow is manageable. For files you need to edit actively on mobile, the friction is real.
The Passphrase Problem
The weakest point in any client-side encryption setup isn’t the encryption algorithm — it’s the passphrase.
A passphrase that’s easy to remember is weak. A passphrase that’s strong is easy to forget. If you lose the Cryptomator passphrase for a vault, the files inside are permanently inaccessible. There is no “forgot password” option, no company to call, no recovery mechanism. This is a feature, not a bug — it means no one else can recover access either — but it means you need a reliable system for storing the passphrase.
Practical options:
- Store the passphrase in a password manager (1Password, Bitwarden, etc.) secured with its own strong master password
- Write the passphrase on paper and store it in a physically secure location
- Both, with the paper copy as the backup
If you choose to store your vault passphrase in a cloud-based password manager, recognize that this creates a dependency: access to your encrypted vault now depends on access to the password manager, which is likely synchronized to a cloud service. The chain is only as strong as its weakest point.
When Client-Side Encryption Is Worth the Friction
For most files most people store in cloud storage, the encryption provided by the storage service itself is sufficient. Photos, documents, notes — the realistic threat for most users is a data breach, and server-side encryption protects against that.
Client-side encryption becomes worth the added friction when:
- The files are sensitive enough that you don’t want the cloud provider to be able to read them under any circumstances
- You have reason to expect legal process (divorce, litigation, regulatory investigation)
- The files involve other people who haven’t consented to their content being accessible to the cloud provider
- You’re in a jurisdiction or profession where confidentiality is a legal obligation
For most people, this is a small subset of their overall file storage — financial documents, health records, legal correspondence, personal diaries. That’s the right scope for client-side encryption. Using it for everything adds friction without proportionate benefit.
The practical takeaway: know what your cloud provider can access, choose a service whose data practices you’ve reviewed, and add client-side encryption for the files where the standard protections aren’t enough.