Cryptomator review — encrypt cloud storage without trusting the provider
Cryptomator encrypts your files on your own device before they sync to Dropbox, OneDrive, iCloud or any other cloud service, so the provider can't read them.

Cryptomator review
Cryptomator encrypts your files on your own device before they sync to Dropbox, OneDrive, iCloud or any other cloud service, so the provider can’t read them.
Who is this for? Anyone using a cloud service — Dropbox, OneDrive, iCloud, Nextcloud — who does not want the provider to have access to readable files. Cryptomator encrypts files locally before they are synced.
Cryptomator solves a specific problem: cloud storage is convenient, but the provider technically has access to your files. Cryptomator adds an encryption layer to your existing cloud sync without requiring you to switch services.
Open-source (GPLv3, desktop and mobile apps), made by Skymatic GmbH in Bonn, Germany, and independently auditable.
How it works
Cryptomator creates a vault — a folder on your disk. You unlock the vault with a password, and it appears as a regular drive in your file manager. Everything you store inside is encrypted before it touches the folder.
You place that encrypted folder inside your cloud sync folder (your Dropbox folder, OneDrive folder, etc.). The cloud sync then copies encrypted files to the server — the provider can’t read file contents or names, though it still sees sizes, timestamps and how many files there are (see Caveats).
Cryptomator encrypts locally and by default doesn’t store your password; the cloud server stores only the encrypted result. The vault’s master key travels along inside the vault folder (masterkey.cryptomator), wrapped with a key derived from your password. Anyone with a copy of the vault can therefore try to guess the password, so a strong one is what protects you.
Comparison with alternatives
| Cryptomator | VeraCrypt container in cloud | Proton Drive | Tresorit | |
|---|---|---|---|---|
| Cloud-provider agnostic | Yes — any service with a local sync folder | Yes | No — own service | No — own service |
| Per-file sync | Yes | No — whole container | Yes | Yes |
| Open-source | Yes (GPLv3) | Yes | Apps yes | No |
| Free on desktop | Yes | Yes | Limited (free tier) | Limited (free 3 GB plan) |
| Mobile | Free read-only; write access €29.99 / $29.99 one-time | No official app | Yes | Yes |
VeraCrypt note: a VeraCrypt container in a cloud folder works technically but is impractical for daily sync: to the sync client it is one large file, so one edited document marks the whole container as changed, and changes on two devices conflict over the entire container (our reasoning; how much is uploaded depends on the sync client). Cryptomator encrypts per file, so only the files you changed sync again.
Which cloud services are supported
Cryptomator works with any service that syncs files locally via a folder on your disk:
- Dropbox — via the Dropbox desktop app
- OneDrive — via the OneDrive desktop app
- Google Drive — via Google Drive for Desktop
- iCloud Drive — on macOS and Windows via the iCloud folder
- Nextcloud — via the Nextcloud desktop client
In principle also any other mechanism that uses a local folder, such as an SFTP mount or NAS folder: Cryptomator only asks for a directory.
The mobile apps connect to the cloud themselves: natively to Dropbox, Google Drive, OneDrive, pCloud and S3, on iOS also Box and iCloud, and to others such as Nextcloud via WebDAV. Cryptomator lists Mega as not usable on mobile (supported services).
Mobile: free read-only, paid write access
Both mobile apps are free to download and give read-only access: enough to open a vault and view files. Adding or editing files needs the full version, which you can try free for 30 days. A licence bought on one platform does not work on another (Cryptomator’s Android docs).
- Android, Google Play: two apps with the same features. The Freemium app unlocks with a yearly subscription or a one-time lifetime licence; the Full Version app is bought once up front (and can be shared via Google Play Family Library).
- Android without Google: an APK from cryptomator.org/android/, Cryptomator’s own F-Droid repository, the main F-Droid repository or Accrescent, unlocked with a licence key bought on the website. The F-Droid and Accrescent builds can’t connect to Google Drive, and the main F-Droid build also leaves out other cloud services that need an API key.
- iOS: via the App Store, unlocked with an in-app purchase.
Cryptomator’s pricing page lists the one-time unlock at €29.99 each for Android and iOS, its base price for Germany; prices vary by region, and Google Play and the App Store list the Full Version at $29.99 in the US. Skymatic’s choice: the desktop app is free and open-source, and the mobile payment funds development. Desktop-only users pay nothing, and mobile users can still read their vaults without paying.
Audit
Cure53 audited Cryptomator’s cryptographic libraries in 2017 (report PDF), in a project for 1&1 Mail & Media, whose Tresor apps use them. The scope was those libraries, not the desktop or mobile apps. Cure53 called the robustness “quite exceptional”, with a very small attack surface. One finding was rated “Critical”: the passphrase-protected private key used to sign releases was in public GitHub repositories, and Cure53 recommended replacing it. A note added to the report says the key only signed the libraries’ Maven releases and had no influence on the Tresor apps. The file is gone from the repositories’ current branches. We found no announcement of a replacement, but the signatures on Maven Central show that key (ID ending in 34C80F11) still signed the libraries until April 2020; since cryptolib 1.4.0 (September 2020) a different key signs them (our own check, November 2026).
Cryptomator’s site speaks of “independent security audits”. This 2017 report is the only published audit we found; Cryptomator’s forum also names a review of one library (SIV-Mode) by Tim McLean, which we did not read. Asked about a new audit in 2024, the forum answer was that it would need external sponsors.
The source code is public on GitHub and independently verifiable.
Getting started
Install:
- Windows / macOS / Linux: download from cryptomator.org/downloads/
- Linux (Flatpak): via Flathub:
flatpak install flathub org.cryptomator.Cryptomator
Create a vault:
- In Cryptomator, click + (Add Vault) at the bottom of the vault list → Create New Vault…
- Enter a Vault Name → Next
- Choose where the encrypted files go: Cryptomator lists the cloud folders it finds (Dropbox, OneDrive and so on); otherwise pick Custom location → Choose… and select your cloud sync folder. Cryptomator creates a folder with the vault’s name there (e.g.
~/Dropbox/MyVault/) → Next - Leave Enable expert settings off → Next
- Enter a strong password twice (at least 8 characters, longer is better): nobody can reset it for you
- Choose whether you want a recovery key (Cryptomator makes you pick; we recommend Yes please, better safe than sorry) → Create Vault
- If you chose a recovery key, store it now (see Caveats) → Next
- Cryptomator confirms the vault was added; click Unlock Now, or unlock it later
Open and use:
- Select the vault in Cryptomator → Unlock…
- Enter your password → Unlock (leave Remember password off on a shared or high-risk computer)
- Click Reveal Drive: the vault opens as a drive in your file manager
- Save files normally — encryption is transparent
- When you’re done, click Lock in Cryptomator
Already have a vault without a recovery key? Select it, make sure it is locked (Vault Options only appears then), then Vault Options → Password → Display Recovery Key and enter the password.
Migrate existing files:
Encryption only applies to files you store inside the unlocked vault. Existing files in your cloud folder are not automatically encrypted — copy them into the vault manually.
Caveats
Password loss is permanent: nobody can reset your password. If you forget it and have no recovery key, your files are permanently inaccessible. Store the vault password in a password manager.
Recovery key: when you create a vault, Cryptomator asks whether you want a recovery key, a sequence of words; for an existing vault you can display it later via Vault Options. It is a readable form of the vault’s master key, so anyone who has it can get in: store it in your password manager or on paper in a safe location. This is the only fallback if you lose your password.
Sync conflicts: if the same file changes on two devices before the sync catches up, your cloud service may create a conflict copy, as with unencrypted files. Cryptomator shows it in the vault with the provider’s suffix in the name; check both copies and keep the right one.
Cloud search does not work: the encrypted files in the cloud are unreadable to Dropbox or OneDrive search. Search only works while the vault is unlocked locally on your device.
What stays visible: Cryptomator doesn’t encrypt file sizes, timestamps or the number of files and folders, and its file extensions show that you use it. For hiding those, it points to container-based tools.
Mobile cost: reading vaults on mobile is free, but write access needs a one-time unlock per platform (€29.99 / $29.99) or, on Google Play, a yearly subscription: a barrier for mobile-only users who need to add or edit files. For desktop-only use there is no cost barrier; only dark mode on desktop is a paid extra.
Pros and cons
Pros
- Works with any cloud service that has a local sync folder — no provider switch required
- Per-file encryption — incremental sync stays efficient
- Open-source (GPLv3), crypto libraries audited by Cure53 (2017)
- Desktop free (dark mode is an optional paid extra); mobile vaults are readable for free
- Skymatic is a German company (Bonn), so EU rather than US jurisdiction
Cons
- Write access on mobile needs a paid unlock per platform (€29.99 / $29.99)
- Password loss = permanent data loss — no recovery without the recovery key
- Cloud search does not work on encrypted files
- File sizes, timestamps and file counts stay visible to the provider
- No protection if your device itself is compromised (true of all client-side encryption)
Conclusion
Cryptomator is the most practical way to encrypt an existing cloud service without switching providers. It fits into an existing workflow without additional subscriptions or new services.
The only real friction is the mobile unlock payment — for desktop use the barrier is low and the approach is solid.
If you already use a cloud service and do not want the provider reading your files: start here.
Next step
Chosen Cryptomator?
- Choose a password manager — the Cryptomator vault password should go in a password manager; this helps you pick one
Similar options
- VeraCrypt review — for local encrypted containers and full-disk encryption without cloud
- Proton Drive review — if you prefer switching cloud services over adding an encryption layer
- Tresorit review — end-to-end encrypted cloud service as an alternative to Proton Drive
Want to go further?
- Backup implementation guide — Cryptomator encrypts cloud storage but does not replace a backup; local copies are still necessary
- VeraCrypt: encrypted storage — for use cases where you do not need the cloud