How to verify a downloaded file with SHA-256

Start with a reproducible example

In text mode enter lowercase abc with no spaces or newline and select SHA-256. The digest should match below. The downloadable abc.txt contains exactly those three UTF-8 bytes for a file-mode check.

ba7816bf8f01cfea414140de5dae2223
b00361a396177a9cb410ff61f20015ad

The display wraps the digest into two lines. Remove the line break when pasting an expected digest; the resource page also includes a one-line checksum manifest.

Verify the digest’s source

Get the reference from the publisher’s official release or a trusted signed manifest. If an attacker can replace both file and digest, comparing them will not expose that substitution. Use publisher signature verification when available and verify the key’s origin.

A match does not establish safety

• A newline, encoding difference, or any changed byte can change the digest.
• On a mismatch, obtain a trusted copy rather than ignoring the difference.
• A hash is neither malware scanning nor proof of publisher identity.
• This tool accepts files up to 100 MiB and buffers the full file.