Hashes are fingerprints, not encryption
Encryption is meant to be reversed with the right key. A hash is not. It is designed to make a repeatable fingerprint from the input so you can compare values later.
Changing even one character changes the hash, which is why hashes are useful for spotting whether text was altered.
Use SHA-256 for modern checks
SHA-256 is widely used for checksums, integrity checks, API workflows, and technical records. Older hashes such as MD5 and SHA-1 can still appear in legacy systems, but they should not be treated as strong security choices for new work.
If a website or vendor publishes a checksum, generate the same hash from your copy and compare the two values exactly.
Keep sensitive input local
For API examples, configuration snippets, identifiers, or private text, local browser hashing avoids sending the input to a server just to calculate the result.
Do not hash passwords in a simple public webpage and treat that as password storage. Secure password storage requires salts, slow password-hashing functions, and server-side controls.