SHA-256 hashes, checksums, and encryption are different things
Use a text digest to compare exact input, and know why it does not protect a password by itself.
A cryptographic hash produces a fixed-length digest from input bytes. It is useful when you need to compare whether two exact inputs match, but it is neither encryption nor a safe password-storage recipe on its own.
Small changes produce different digests
Open the hash generator, enter “abc”, and choose SHA-256. The hexadecimal result begins ba7816bf. Add a space or newline and generate again: the bytes changed, so the digest changes. The tool encodes text as UTF-8 before hashing and also offers SHA-384 and SHA-512.
A digest can help compare a short text value against a known published result. To check a downloaded file, however, you need a file-hashing tool that reads the exact file bytes. Pasting a filename into this text tool hashes the filename, not the file contents.
Do not confuse one-way with secret
Hashing does not hide a common password from guessing. Attackers can calculate hashes for likely passwords. Secure password storage needs a purpose-built slow, salted password-hashing method and a careful authentication design. Similarly, a plain hash does not prove who created a message; that requires an authenticated signature or message-authentication scheme.
Check every byte
If two results differ, inspect the algorithm, encoding, capitalization, whitespace, and trailing newline. The text and digest stay in your browser. Avoid placing secrets in a public screenshot even though the calculation itself is local.