Hash text
Create SHA-256, SHA-384, or SHA-512 checksums from exact UTF-8 text and compare with an expected digest.
How it works & useful details
How to use this tool
Enter text, choose an algorithm, and calculate its checksum. Optionally compare an expected hexadecimal checksum.
Details and limits
Hashes include all UTF-8 bytes of your text, including whitespace and line endings. No normalization is performed. Empty text is valid. SHA-256/384/512 are one-way hashes, not encryption and not dedicated password-hashing functions.
Up to 100,000 UTF-16 input code units. Web Crypto runs locally after you start the operation.
About this tool
Hash text creates SHA-256, SHA-384, or SHA-512 checksums from the exact UTF-8 text you paste and can compare the result with an expected digest. It is useful for verifying configuration values, cache keys, and API signatures.
The text is hashed locally and never sent anywhere. Because hashing is exact, a trailing space or a different line ending produces a different digest, which is the most common cause of mismatches.
How to use it
- Paste the exact text you want to hash.
- Choose the hash algorithm.
- Paste the expected digest if you have one.
- Compare the computed value and check the match result.
Worked example
SHA-256("hello") = 2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824
SHA-256("hello\n") = 5891b5b522d5df086d0ff0b110fbd9d21bb4fc7163af34d08286a2e846f6be03
SHA-256("Hello") = 185f8db32271fe25f561a6fc938b2e264306ec304eda518007d1764826381969One extra newline or one capital letter produces an unrelated digest. This is the avalanche effect that makes hashes useful for detecting changes. It also explains the most common mismatch: echo hello | sha256sum hashes "hello" plus a trailing newline, while this tool hashes exactly what you typed.
Hashes are not encryption
A hash is one-way: you cannot recover the text from the digest. But short or predictable inputs can be found by guessing, since an attacker simply hashes candidates until one matches. That is why fast hashes like SHA-256 are unsuitable for storing passwords. Password storage needs a deliberately slow, salted algorithm such as Argon2, scrypt, or bcrypt.
Good uses for text hashes include comparing configuration snippets, creating stable cache keys, checking that a copied API payload is unchanged, and computing the hash values used in Content-Security-Policy source expressions (after Base64-encoding the raw digest).
Frequently asked questions
Does capitalization matter in the digest?
Hex digests are case-insensitive, and the comparison normalizes case so 0A and 0a match.
Why does my digest differ from another tool?
Usually a difference in line endings, trailing whitespace, or encoding. Confirm the exact bytes that were hashed.
What is the input limit?
Up to 100,000 characters of text.
Does the tool normalize line endings?
No. Windows (CRLF) and Unix (LF) line endings are different bytes, so they produce different hashes. That is intended: the digest reflects exactly the text you entered.