Publisher notes · reviewed 10 September 2026
Hashes identify bytes; they do not encrypt them
SHA-256 and similar functions map input bytes to a fixed-size digest. The same input always yields the same digest. You cannot get the input back. That is not encryption, and it is not a password-storage recipe by itself.
Use and misuse
Hash a file to check it survived a download. Hash a string to compare equality without storing the string. Rainbow tables exist for common passwords, so use Argon2 or bcrypt for credentials, not raw SHA-256.
HMAC needs a key. If this page only exposes unkeyed hashes, do not treat the output as an HMAC. Encoding (Base64, hex) is not hashing.
Worked examples
Empty SHA-256
SHA-256 of an empty input is e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855. If the tool shows something else for empty input, the implementation is wrong or it hashed a newline.
Limits of this page
- Not a certificate fingerprint UI for TLS inspection.
- MD5/SHA-1 remain available in some tools only for legacy checksums; they are not collision-resistant for security.