SHA Hash Generator and Checker
Calculate the SHA-256, SHA-384 or SHA-512 hash of text or a local file with Web Crypto, then compare it with an expected value. Nothing is uploaded.
Local calculation in your browser: neither text nor file leaves the device. A hash checks integrity, not origin.
Input
Enable JavaScript for local calculation. The guide remains accessible.
Results
Choose a source, then calculate its hash.
Hexadecimal only, any letter case, with the length of the selected algorithm.
Understanding SHA hashes
SHA-256, SHA-384 and SHA-512 (SHA-2 family, FIPS 180-4) produce a 256-, 384- or 512-bit hash, shown as 64, 96 or 128 hexadecimal digits. Changing a single byte gives a different hash.
Text is encoded as UTF-8 exactly as entered: no Unicode normalization, no space or line break removed. A precomposed “é” and “e” followed by a combining accent therefore give two different hashes. The tool hashes the text exactly as the field provides it; depending on the browser, pasted CRLF line breaks may become LF there. To check a file, select the file itself.
Examples: empty text gives SHA-256 e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855; “abc” gives ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad.
A match only proves that the bytes are identical to those that produced the expected hash. It proves neither authenticity nor safety: if a file and its hash come from the same compromised source, they can match. Check the hash through a trusted channel or a signature.
SHA is not encryption: content cannot be recovered from a hash, but short or predictable text can be guessed. To store passwords, use a dedicated algorithm (Argon2, scrypt, bcrypt or PBKDF2), never a plain SHA.
Calculated by Web Crypto (crypto.subtle.digest) in the browser, with no upload or storage by the tool. The clipboard and extensions can expose copied values.
Frequently asked questions
Why does my hash differ from another tool?
The bytes usually differ: CRLF or LF line breaks, a trailing space, an encoding other than UTF-8 or Unicode normalization. Prefer comparing the file itself.
Does a match guarantee a safe file?
No. It confirms integrity against the expected hash, not who made the file. The expected hash must come from a trusted source.
Can I use SHA for passwords?
Not directly: SHA is fast, which helps mass guessing. Use Argon2, scrypt, bcrypt or PBKDF2 with a salt.