SHA-2 · 512 bits · Files
Calculate SHA512 for one or many files. Verify a GNU or BSD checksum list without uploading files.
Ready to calculate
0 / 0 bytes processed
Browser-local hashing. Inputs masked in Clarity.
No account. No uploads. Just your browser.
Choose up to 100 files, each at most 2 GiB. The file contents are read locally.
SHA512 returns 128 lowercase hex characters. Copy digest preserves the whole output.
Read a local manifest or paste a trusted expected value. Review each filename and any missing entries.
SHA512 is part of SHA-2 and produces a 512-bit result: 128 hexadecimal characters. Copy the entire digest; comparing only a prefix is not full verification. It is distinct from SHA512/256 and SHA384.
Some publishers distribute .sha512 files. Keep the full 128-character digest and exact filename. A 64-character SHA256 value is not a shortened SHA512 value and is rejected by this checker.
Choose or drop files and calculation starts automatically. Each file is read sequentially in 2 MiB chunks inside a background worker. Up to 100 files and 2 GiB per file are accepted. Cancel terminates the active worker.
Paste a trusted expected digest to compare directly. With no expected value, Not compared yet is not a verification success. Every batch row includes the complete digest, byte count and comparison outcome.
Open manifest options to read a local list or paste GNU digest–filename lines or BSD ALGORITHM (filename) = digest lines. Verify selected files runs the comparison again with the list. The filename is matched exactly, including spaces and relative folders.
Duplicate names, invalid digest lengths, mixed algorithms and unsupported lines block manifest verification. Missing files and files not listed are displayed; no basename-only guessing or silent success is used. Lists are limited to 1 MiB and 100 entries.
Hashing runs in browser memory with no upload endpoint. Microsoft Clarity runs on this page, with the entire tool workspace masked, including filenames, digests and manifests. Google Analytics runs only on the four information pages. A local report can be copied or downloaded. See Privacy for details.
The 2 GiB ceiling is not a promise about every phone. If a device struggles, cancel and use a system checksum utility. A matching value proves only equality with the reference digest, not safety or publisher identity.
Use the full 128-character publisher reference for the selected archive or installer.
Download a local report instead of selecting only one wrapped line of a long SHA512 digest.
Batch processing reads one file at a time in chunks; it does not combine the files into a single SHA512.
| Algorithm | What differs |
|---|---|
| SHA512 | 512-bit SHA-2 digest, displayed as 128 hex characters. |
| SHA256 | 256-bit SHA-2 digest, displayed as 64 hex characters. |
SHA512 · 0 bytes · no HMAC. Empty input is not the same as no file selected.
SHA256 Onlinecf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3eExactly 128 hexadecimal characters. Include leading zeroes and the whole reference, not the first display line.
No. SHA256 and SHA512 are different algorithms. Recalculate the original file with the algorithm printed next to the trusted reference.
No. File mode reads sequential 2 MiB chunks in a local worker. It supports up to 2 GiB per file, although device resources can impose lower practical limits.
There is no universal browser speed guarantee. Hardware, browser and input size affect timings. Choose the algorithm required by your reference rather than an assumed speed ranking.
Files are hashed automatically and sequentially. The result says calculated until an expected digest is supplied; Match or Mismatch describes a comparison, not just a completed calculation.
Use GNU digest followed by a filename, or a BSD algorithm (filename) = digest line. Each SHA512 reference needs 128 hex characters. Malformed lines and duplicate names block verification.
Names must match exactly, including spaces and relative paths. A selected file not in the manifest is reported separately and is not silently treated as a verified match.
Download report saves a local text report with filenames, byte counts, digests and comparison states. Keep that report private if its filenames or checksums are sensitive. No report is uploaded.