Calculate a 512-bit SHA-2 digest with Web Crypto and view hexadecimal or Base64 output.
The text digest remains first. This optional file workflow reuses the existing local SHA-512 engine to hash the exact bytes of one file, compare the full digest with an expected 128-character hexadecimal checksum, and create a copy-ready manifest line without uploading the file.
Files are read locally; the shared hash engine limits a single file to 256 MB because SubtleCrypto digest is not streaming.
connects text/file digests, checksum verification and HMAC workflows. Hashes compare exact bytes; HMAC additionally depends on a shared secret key.
Fast hashes such as SHA-256, SHA-1 and MD5 are not password-storage schemes. Production password storage should use a purpose-built slow password hashing/KDF design with salts and reviewed parameters; legacy algorithms remain here only for compatibility and checksum workflows.
Use the tool first, then apply these checks to verify inputs, interpret the result, and hand it off without displacing the primary workflow.
A checksum only proves equality when both sides hash exactly the same byte sequence. Text copied through an editor can change line endings, Unicode normalization, a final newline, or character encoding, while a file digest covers the stored bytes directly. For release artifacts, installers, archives, disk images, and signed manifests, prefer the file workflow and record the filename, byte size, algorithm, and full 128-character SHA-512 hex value together.
An expected SHA-512 value is useful only if it came from a source you already trust. A matching digest can detect accidental corruption or substitution relative to that reference, but it does not identify who published the file by itself. Obtain release checksums from the project or distribution channel you intended to use, compare the complete digest rather than a shortened prefix, and keep digital-signature or package-signing verification separate when publisher authenticity matters.
SHA-512 is intentionally fast, which is useful for integrity checks but undesirable for password databases because attackers can test guesses quickly. Password storage should use a reviewed password-hashing or key-derivation design with salts and appropriate cost parameters. HMAC-SHA-512 is also a different construction: it combines a shared secret with the message to provide keyed authenticity, whereas a plain SHA-512 digest contains no secret and is reproducible by anyone with the same input bytes.
A 512-bit digest is commonly displayed as 128 hexadecimal characters, but tools may also show Base64 or include filenames in checksum-manifest syntax. Do not compare a Base64 digest directly with a hexadecimal digest, and do not confuse SHA-512 with SHA-512/256 or another SHA-2 variant. When handing off a checksum, label the algorithm explicitly and preserve the full value so a second tool can independently reproduce the result.
WebToolArc