Cryptomator’s security target describes client-side encryption for cloud storage. It protects file contents and names while leaving some metadata visible, including file sizes, timestamps and counts. That design suits a cloud-file workflow, but it is not a promise to hide all information about the vault.

VeraCrypt’s beginner tutorial instead walks through creating a file container, mounting it as a volume and placing files inside. A container can be moved like a normal file. Its tutorial warns that selecting an existing file as the new container target overwrites that file; create a new filename rather than pointing at data you want to encrypt.

For files already managed through a cloud folder, Cryptomator is the more directly aligned documented workflow. For an encrypted volume that you mount for a local project or carry on removable storage, consider VeraCrypt’s container approach. Cloud transfer behavior depends on the sync service: we have not measured bandwidth, conflict handling or speed for either tool.

Neither choice removes the need for backups or a trustworthy computer. Cryptomator explicitly warns that malware can read an unlocked vault and that programs may leave separate working copies. Try non-sensitive sample files, confirm recovery access, and lock or dismount after use. This is a documentation comparison, not a cryptographic audit.