The documented difference
Cryptomator describes client-side encryption for files and filenames stored with a chosen cloud provider. Its personal vault workflow uses a password and presents an unlocked drive-like interface; the project publishes its source code. See Cryptomator’s official documentation.
Side-by-side decisions
| Question | NullVault | Cryptomator |
|---|---|---|
| Main job | Private mobile archive with pattern-addressed spaces | Client-side encryption layered over file storage |
| Storage choice | Follow the app’s platform-specific backup paths | Use a compatible storage provider and client workflow |
| Daily interaction | Open the intended vault in the mobile app | Unlock a file vault and work through supported file access |
When Cryptomator is the better choice
Cryptomator may be the better fit when you want to keep an existing cloud provider or desktop file workflow while adding client-side encryption. Its open-source model can also matter to readers who want to inspect implementation details.
When NullVault fits
NullVault is a candidate when the main task is organizing private media and notes directly on a phone in separately addressed spaces. It should not be described as a general encrypted-drive layer for arbitrary desktop applications. Read NullVault’s features and security limitations for the released scope.
Before you move an archive
Test the file types, offline requirements and recovery procedure you actually use. Distinguish personal Cryptomator from its separate team product. Keep a verified copy before changing storage layout, and check export destinations for plaintext working files.
How this comparison was prepared
This is a comparison of published product documentation as of 7 September 2026, not a hands-on security test or independent audit. Store plans and platform support can change. NullVault publishes this page; there are no affiliate rankings or invented star scores.