Veracrypt

Looking at the published feature set of Cryptomator, it seems to be exclusively a file-based container. Whereas VeraCrypt additionally offers partition (including the system partition to protect the OS) and whole drive encryption.

Creating a quick Cryptomator vault, I noticed the key generation was automatic, VeraCrypt includes user-based input (mouse movement) as part of its key generation. In my opinion, done right / taken seriously, this offers better entropy.

VeraCrypt offers 15 encryption and 4 hash algorithms to choose from.

VeraCrypt also offers PIM (Personal Iterations Multiplier) modification / customization.

VeraCrypt can use a keyfile.

VeraCrypt offers hidden volumes for plausible deniability.

Looks like Cryptomator sets up a fairly deep directory structure, creating an encrypted file for each file added to the vault. This eludes to not only how many files are in the vault but also reveals size and date/time information. VeraCrypt’s container is just a single file of predetermined size, date/time stamp update is optional but off by default.

I believe these items make VeraCrypt more secure but at the cost of requiring the user to be more sophisticated.

I’m not a hater, Cryptomator’s ease of use may offer encryption to someone who may not otherwise leverage it and that is valuable.

Depending upon use case, performance may come into play which may be worth measuring.