Revault vs. Cryptomator
Cryptomator makes an encrypted vault behave like a drive. Revault organizes imported files inside its own vault interface. Choose around how you work with files and which cloud you want to use.
Reviewed October 28, 2026 · Sources belowThe feature breakdown
| What matters | Revault | Cryptomator |
|---|---|---|
| Everyday workflow | Import and organize files inside the app; explicit preview and export. No mounted desktop drive. | A virtual drive transparently encrypts and decrypts files as you work. [2] |
| Account requirements | No Revault account on mobile. The web app uses a passkey account. Native cloud sync requires the corresponding Apple or Google account. | Personal password-protected vaults need no Cryptomator registration; cloud-provider accounts are separate. [1] |
| Cryptography | AES-256-GCM; device pattern plus a random device secret; PBKDF2-SHA-256 wrapping and HKDF-SHA-256 streaming file encryption. | AES-based encryption; password-protected master keys use scrypt and AES Key Wrap. [2] |
| Storage choice | Local storage by default. Optional private iCloud on iOS or Google Drive appDataFolder on Android. The web cloud is separate. Browser uploads can also target your S3-compatible bucket. | An encryption layer over your existing cloud storage rather than a bundled storage service. [3] |
| Recovery | A separate vault recovery key plus an encrypted cloud copy or .qvault backup. A web account reset cannot decrypt a vault. | A confidential recovery key can reset the vault password. [4] |
| Visible metadata | Cloud providers can observe encrypted object sizes, counts, identifiers and timing. Encryption does not hide all activity. | File sizes, timestamps and file/folder counts remain visible; directory structure is obfuscated. [3] |
| Security review | No independent security audit completed. Review the security model and keep tested backups. | Open-source software with published independent security audits. [1] |
A vault that starts on your device.
You prefer a dedicated vault interface, device patterns, encrypted previews, and native private-cloud sync without a Revault account.
A different workflow fits better.
You want a virtual drive on a desktop, broad cloud-provider choice, and publicly documented security audits.
Know the tradeoffs.
Revault’s native cloud integrations are deliberately limited to each platform’s private cloud. Its browser supports individual encrypted uploads to S3-compatible storage, but that is not a general-purpose mounted filesystem. Revault has not undergone an independent security audit.
No app can protect unlocked files from a compromised device. Exporting a decrypted file creates a copy outside the vault; deleting access cannot recall copies someone already saved. Keep recovery secrets and tested backups separately.
Revault’s security modelSources & scope
Primary documentation checked on October 28, 2026. Comparisons describe the documented personal product, not every enterprise plan or add-on. No price ranking is included because pricing varies by region and store.
- Cryptomator: workflow, registration and security review
- Cryptomator: security architecture
- Cryptomator: security target and metadata limits
- Cryptomator: password and recovery key
Revault statements describe the implementation in this project; native store availability depends on release. Revault has not undergone an independent security audit. Cryptomator is a trademark of its respective owner. No affiliation or endorsement is implied.