How to generate a text hash
- Paste the exact text whose UTF-8 representation you want to hash.
- Select SHA-256, SHA-384 or SHA-512.
- Select Calculate hash and review the algorithm and input-byte count.
- Copy the lowercase hexadecimal digest or download it as a text file.
An empty input is valid and has a defined digest. If you expected a document but see zero input bytes, check that the text was actually pasted before using the result.
From text to a SHA-2 digest
The tool encodes the text with TextEncoder and passes those UTF-8 bytes to the browser’s Web Crypto digest API. It does not trim whitespace, normalize accents, alter letter case or add a final newline. A different byte sequence can produce a different digest even when two strings look similar.
SHA-256 produces 256 bits, shown as 64 hexadecimal characters. SHA-384 produces 96 hexadecimal characters, and SHA-512 produces 128. Hexadecimal is just the display notation for digest bytes; it does not add encryption or a secret key.
Web Crypto requires a supported HTTPS context or localhost. An unavailable API produces an explicit error. No JavaScript imitation or external hashing service is used as a fallback.
SHA-256 example
Input
abc
Result
ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad
The input is exactly three UTF-8 bytes, without quotes or a newline. Adding a space after c changes the input and its digest. When comparing with a command-line utility, verify whether the command included a terminating newline and which text encoding it used.
Unicode and copied-text differences
A precomposed accented letter and a base letter plus a combining accent can look identical while producing different UTF-8 bytes. This tool preserves that distinction. Unpaired Unicode surrogates are rejected rather than silently hashing replacement characters. The browser textarea can normalize pasted line endings, so this is a hash of the text in the field, not a byte-for-byte file checksum.
Use the character counter to understand graphemes versus code points, and Text Diff to inspect textual differences. Cleaning whitespace before hashing intentionally changes the input; only do so if your protocol specifies that transformation.
What a hash can and cannot establish
A digest can help compare exact content when the expected digest comes from a trusted source. It does not by itself authenticate the sender, encrypt a message or prove that a downloaded file is harmless. This tool accepts text, not binary files, and does not provide HMAC, digital signatures or a checksum database.
Plain SHA-2 is not a password-storage scheme. Password storage needs a suitable salted, work-factor-based design in the application. No MD5 or SHA-1 mode is included. The 1 MiB text limit also avoids implying that the browser is streaming arbitrary large files through this interface.
For a reversible text representation, use Base64; Base64 is not encryption either. For a newly generated identifier rather than a content fingerprint, use the UUID Generator.
Processing and privacy
The operation runs in your browser. The tool does not send the material you enter to a processing server or automatically save it. Reset clears the form and result from the interface; it is not a secure-erasure guarantee for browser memory. Copy and download deliberately create copies outside the tool. The website itself still makes ordinary requests for its pages and scripts. See the privacy policy for the distinction.
Frequently asked questions
Can I reverse a SHA hash to retrieve the original text?
This tool has no reversal operation. Hashing is not reversible encoding or encryption.
Why does my command-line hash differ?
Check encoding, leading/trailing spaces, line endings and whether the command added a newline. This tool hashes the exact textarea text as UTF-8.
Can I use this as a file checksum tool?
No. Pasting text can change its representation. This page hashes text, not the original bytes of an uploaded binary file.