Hashing
SHA3-512 hash generator
SHA3-512 hashes any text you paste into the 128-character digest defined by NIST's FIPS 202 standard. Despite the matching length it is unrelated to SHA-512: it is the Keccak sponge, not the SHA-2 design. Output is lowercase hex, computed as you type, and matches openssl dgst -sha3-512 and Python's hashlib.sha3_512.
How to use SHA3-512
- Open SHA3-512 in the Toolbox101 app.
- Paste or type the text into the
Inputbox. - Read the 128-character digest in the
Outputbox; it updates as you type. - Click
Copyto put it on your clipboard.
Worked example
SHA3-512 returns the output below for this input.
Input
The quick brown fox jumps over the lazy dogOutput
01dedd5de4ef14642445ba5f5b97c15e47b9ad931326e4b0727cd94cefc44fff23f07bf543139939b49128caf436dc1bdee54fcb24023a08d9403f9b4bf0d450Check it yourself: open SHA3-512 and enter the same input.
Frequently asked questions
What is the difference between SHA3-512 and SHA-512?
Everything except the output size. SHA-512 is the 2001 SHA-2 design (Merkle–Damgård, 64-bit words); SHA3-512 is the Keccak sponge that won NIST's SHA-3 competition and was standardised in 2015 as FIPS 202. Both give 128 hex characters, but the digests never match for the same input.
Why does my result differ from another SHA-3 site?
Check which variant the other tool computes. The pre-standard Keccak-512 uses different padding and gives a different digest, and some older libraries still label it SHA-3. This tool follows FIPS 202: the empty string must give a69f73cc…cd26.
Why is the digest exactly 128 characters?
SHA3-512 output is 512 bits, or 64 bytes, and each byte is two hex characters, so the result is 128 lowercase characters whatever the input size. The empty string hashes to a69f73cca23a9ac5c8b567dc185a756e97c982164fe25859e0d1dcc1475c80a615b2123af1f5f94c11e3e9402c3ac558f500199d95b6d3e301758586281dcd26.
Is SHA3-512 more secure than SHA-512?
For realistic threats they are equivalent: both give 256-bit collision resistance and no attack on either comes close. SHA-512 is far more widely deployed; SHA3-512 is the independent fallback if you want a hash with a different design. Pick by what your ecosystem expects, since TLS and most tooling still standardise on SHA-2.