Cryptomator vs Encrypted Disk Image (Disk Utility)

[iamdannywyatt]

I think this topic helps a little bit:

Cryptomator Vault / Tresor vs. macOS encrypted Time Machine image / sparsebundle

— Englisch Translation — Hey everyone. I would really like to know what security advantage one backup variant has over the other. With a Cryptomator vault, an encrypted folder / image is created on a OneDrive server, for example. This is decrypted locally on my computer. I put files into the mounted drive locally. And these are encrypted and stored on the actual OneDrive vault. Isn’t that exactly the same as creating an encrypted sparsebundle image via macOS Disk Utility, putting it on OneDr…

So basically Cryptomator works locally, encrypts the files and uploads those files to Dropbox/iCloud, so the vault itself is not uploaded. Whereas a disk image, as pointed out by @tobihagemann, is uploaded to the cloud and any small changes, even if it’s 1KB would mean reuploading the whole disk image, which could be GBs of data just for a 1KB change.

Is this accurate? Would Dropbox/iCloud see the disk image, when changed in size and date modified, assume it was a new file and would try to re-upload the whole thing?