Practical example
Hash the downloaded file and compare the entire SHA-256 digest with the value published by the distributor.
Paste text, choose an algorithm, and get the hash instantly. Everything runs locally in your browser.
A hash is a fixed-length fingerprint of input data. Even a tiny change in input produces a very different output.
Hashes are useful for checksums, integrity checks, caching keys, and quick comparisons. This tool generates hashes locally in your browser.
A digest can detect changed input, but the algorithm and comparison method determine whether it is suitable for integrity or security work.
Whitespace, line endings, character encoding, and trailing newlines change the digest, so normalize only when the workflow requires it.
Prefer SHA-256 or stronger for integrity checks. Avoid MD5 and SHA-1 where collision resistance is a security requirement.
Compare downloads against a checksum obtained from an authenticated source; a digest delivered beside a modified file proves little.
Do not store passwords with a fast general-purpose hash. Use a password hashing function such as Argon2, scrypt, bcrypt, or PBKDF2.
Hash the downloaded file and compare the entire SHA-256 digest with the value published by the distributor.
A different newline, Unicode normalization form, or text encoding produces a completely different digest for visually identical text.
I use hashes for integrity checks, never plain SHA-256 for password storage; passwords need a slow salted KDF such as Argon2 or bcrypt.
You may also find these tools useful.