Calculate a SHA256 or SHA512 digest of text in your browser. Compare exact input values for debugging and integrity checks.
How to use
Enter the text, select the algorithm, and generate the hash. Use the same algorithm and exact text when comparing two results.
Example
The text abc gives a 64 digit hexadecimal SHA256 digest beginning ba7816bf. Adding a space produces a different digest.
FAQ
Is hashing encryption or password storage?
No. A digest has no decryption key. Password storage needs a dedicated slow password hashing scheme with salts, not a plain SHA digest.
Related tools
A practical task
Document the text source when comparing a digest with another system. A pasted newline or different encoding explains many mismatches. Check a known vector first, then compare the exact bytes rather than repeatedly regenerating the same visible sentence.
Another useful question
Can I hash a file by pasting its filename?
No. A filename is only text. This tool hashes the entered UTF8 text, not the bytes of a file named by that text.
Settings and formats
| Field | Values |
|---|---|
| Algorithm | SHA-256 (SHA-256); SHA-512 (SHA-512) |
Details for interpreting the result
| Detail | Explanation |
|---|---|
| Hash digests | A digest summarizes exact input bytes into a fixed length value. It is not a compressed copy that can be restored. A different digest proves a difference in input, while the security meaning of a match depends on the algorithm and threat model. |
| Collisions | A collision means different inputs share a digest. Every fixed size hash has possible collisions, but practical resistance differs. MD5 has known weaknesses, so matching MD5 values cannot establish authenticity against an attacker. |
| UTF8 bytes | UTF8 encodes characters as bytes. Basic Latin letters use one byte each, while many accented letters and other scripts use more. A byte count therefore differs from a visible character count. |
| Line endings | A line break can use LF or CRLF. They look similar in an editor but contain different characters. Byte comparisons and checksums depend on the exact representation, including a final line break. |
| Similar looking text | Two strings can look identical but use different Unicode sequences. An accented letter can be stored directly or as a letter plus an accent. Visual similarity alone does not establish byte equality. |
| Encoding and encryption | Encoding changes how data is represented so another system can read it. It does not require a secret key. Encryption protects information with a key, while hashing produces a digest for a different purpose. |
| A complete byte | A byte holds a value from 0 through 255. Binary writes that value with eight digits; hexadecimal writes it with two. Leading zeros are part of that fixed width representation and must stay in place. |