A checksum is useful when you want to know whether two inputs match at the byte level. Even a small edit can change the digest, which is why hidden spaces and line endings matter during a comparison.
Text Hash Generator calculates a selected digest for the text you submit. SHA256 and SHA512 are available alongside legacy checksum options.
A digest you can recognise
The SHA256 digest of abc is ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad. The input is exactly those three letters, with no extra space or newline.
If your result differs, inspect the input bytes before concluding that a hash implementation is wrong. Text copied from an editor may carry a newline or a different Unicode representation that looks similar on screen.
This tool hashes the submitted text. It is not a file upload checksum tool, and typing a filename does not hash the contents of that file.
A matching digest has a limited meaning
The digest helps compare inputs under the same algorithm. It does not tell you who created the text, whether its claims are true or whether a download came from a trusted publisher.
MD5 and SHA1 are labelled as legacy checksum choices. They should not be treated as suitable password storage. Password storage needs a purpose built password hashing process with appropriate parameters, not a fast text digest.
If you need authentication with a shared secret, the HMAC tool performs a different operation. A plain hash alone does not attach that secret.
Keep the algorithm name with the digest when you share a result. Comparing a SHA256 value with a SHA512 value is not a useful equality check, even if both were calculated from the same visible text.