01
Match the manifest field exactly
A release manifest may contain several algorithms for the same artifact. Select the SHA-384 field and the correct filename or build variant. Copying a SHA-256 reference into a SHA-384 comparison cannot work, even though both are SHA-2 hashes. Preserve all digits, including any initial zeroes.
02
Compare encoding as well as the digest
Some systems represent hash bytes as Base64 rather than hexadecimal. Their displayed text will differ even when the underlying bytes agree. This page returns hexadecimal, so compare like with like. For a small local test, hash one unchanged file twice and confirm a stable 96-character value, then verify it with an independent SHA-384 implementation.
03
Understand the limits of a file fingerprint
The calculation does not include a secret key, so it is not HMAC-SHA-384. It also does not generate a digital signature. A matching trusted reference is useful for integrity checking, while authenticity depends on how that reference was obtained and on any surrounding verification protocol.