SHA-2 · 256 bits · Files
Calculate SHA256 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.
SHA256 returns 64 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.
SHA256 is part of SHA-2 and produces a 256-bit result: 64 hexadecimal characters. It is a common choice for verifying downloads against a trusted publisher’s checksum. Hashing is one-way, not encryption.
If a SHA256 checksum differs, first confirm the download version and platform. A checksum for a Linux archive will not match the Windows installer, even if both carry the same release number.
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.
Compare the archive or installer with a SHA256 obtained from the publisher through a trusted channel.
Read SHA256SUMS, then select the named assets locally. Each file gets its own comparison.
Hash both copies and check byte lengths. Different release versions or platforms can explain a mismatch without corruption.
| Algorithm | What differs |
|---|---|
| SHA256 | 256-bit digest: 64 hexadecimal characters. |
| SHA512 | 512-bit digest: 128 hexadecimal characters; not a padded SHA256. |
SHA256 · 0 bytes · no HMAC. Empty input is not the same as no file selected.
SHA256 Onlinee3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855Copy the SHA256 value for the same filename, release version, operating system and architecture. A correctly downloaded but different artifact will not match.
Yes. Open the manifest controls and read the local list or paste its text. Choose the referenced files locally; calculation and filename matching happen in your browser.
This tool hashes file contents only, not the filename, modification date or filesystem permissions. Manifest filename matching is a separate step.
No. SHA3-256 also has 64 hexadecimal characters and other formats may too. Check the publisher’s algorithm label rather than inferring it from length alone.
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 SHA256 reference needs 64 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.