Check Text Hashes and Exact Input Bytes
Compare text digests only after confirming that the exact encoded input, whitespace and selected algorithm match.
Use the interactive tool ↓Identify the object you are hashing
This utility hashes the UTF-8 encoding of text in its input field. It is not a file-upload checksum tool. Pasting a filename hashes the characters in that filename, not the bytes of the file it names.
Hash Generator
Reproduce a known SHA-256 value
Select SHA-256 and enter exactly abc, with no trailing newline or spaces. The expected hexadecimal digest is:
ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015adAdd a newline and the digest changes, even though the text may appear visually similar. Copy the output from the intended algorithm row rather than assuming all displayed digests have the same length or purpose.
- Select the algorithms needed by the receiving workflow.
- Enter a harmless known test value.
- Check the exact text before comparing against another implementation.
- Copy the corresponding hexadecimal result.
Understand the available algorithms
The interface offers SHA-1, SHA-256, SHA-384 and SHA-512 through Web Crypto. They generate different digest sizes; selecting several produces several separate digests of the same input. SHA-1 is retained for compatibility checks, not a recommendation for new security designs.
An unkeyed digest is not encryption and cannot be decrypted into the source text. It is also not an HMAC, a digital signature, or a password-storage scheme with a salt and work factor. Anyone able to replace both a message and its published digest can make a new matching pair.
Diagnose a mismatch systematically
Check trailing spaces, line endings and character encoding. Two Unicode strings that look identical can have different underlying code-point sequences; this tool does not promise Unicode normalization. Confirm that the other system hashes raw text bytes rather than a JSON-quoted representation or a whole file.
The input is processed in the browser. Web Crypto requires a suitable browser context; if unavailable, the tool reports a support error. Very large pasted text still consumes memory. Use Text Diff to locate visible changes, while remembering that a visual comparison is not proof of identical bytes.