SHA-512 Hash Generator
SHA-512 is SHA-256’s bigger sibling: 80 rounds over 1024-bit blocks with 64-bit words, producing 128 hex characters. Because modern CPUs are 64-bit, it is often faster than SHA-256 for large inputs despite the longer output. SHA-384 is the same computation with a different starting state and the output truncated, which also protects it from length-extension attacks.
You will find SHA-512 in:
- Linux
/etc/shadowas the$6$crypt scheme (with thousands of rounds) - TLS cipher suites and certificate signatures
- HMAC-SHA512, JWT HS512, and the seed derivation used by cryptocurrency wallets
Both variants use crypto.subtle.digest() for text and a streaming WebAssembly hasher for files.
What leaves your browser
Text is hashed in memory with the Web Crypto API; files are read in chunks with the File API and hashed in WebAssembly. There is no upload endpoint on this page. Open DevTools → Network and hash something: no request appears.
Is SHA-512 more secure than SHA-256?
Both are unbroken. SHA-512's larger state gives more margin against future attacks, but 256 bits already exceeds what any conceivable computer can brute-force.
When should I choose SHA-384?
When a protocol or compliance profile (such as CNSA) asks for it, or when you want SHA-512 speed with resistance to length-extension attacks.
Can a hash be decrypted?
No. Hashing is not encryption; there is no key and no inverse function. The only way to find an input is to guess candidates and compare hashes, which is exactly why password hashes must be slow.
Why does the same text give a different hash on another site?
Usually a trailing newline, different line endings, or a different text encoding. Hash the exact bytes and the results agree everywhere.