Checksums on Azure Blob Storage

You can enable calculation of file integrity checksums for each file uploaded using Files.com. This lets you prove that the file was uploaded correctly and matches the original source file. When two files have the same checksum, they are almost certainly identical.

The MD5 checksum that Files.com provides is the actual MD5 checksum represented as a sequence of 32 hexadecimal digits. If you compare MD5s provided by Files.com with MD5 checksums provided by Azure, you will find them to be different, because Azure displays MD5 checksums as a base64-encoded byte array.

To compare the MD5 checksum from Files.com with the MD5 checksum from Azure, first convert the checksum from Files.com to a byte array, and then base64 encode that. The result matches the checksum from Azure.