About this SHA3-512 generator
SHA3-512 is the 512-bit hash of the SHA-3 standard (FIPS 202), written as 128 hexadecimal characters. It is built on the Keccak sponge, which works differently from SHA-1 and SHA-2, so it is not affected by weaknesses found in those designs. Its longer output gives a larger security margin than SHA3-256, at the same 512-bit size as SHA-512; use it when a specification asks for SHA3-512 or as an independent check next to SHA-512. Hash text or a whole file here and paste a published checksum into Expected hash to confirm your copy is exact. Browsers have no built-in SHA-3, so this page uses its own implementation on your device.
How to generate a SHA3-512 hash
- Add text or a file. Type or paste text, press an example, or press Hash a file to hash a file’s exact bytes.
- Pick the format. Lowercase hex is the usual format; choose uppercase hex or Base64 if your system expects it. Paste an expected hash to compare.
- Press Generate SHA3-512 hash. The hash appears below, with a match or no-match message when you pasted an expected hash.
- Copy the hash. Press Copy hash, or copy it in another format from the list.
Frequently asked questions
Is SHA3-512 the same as Keccak-512?
No. They share the same sponge, but SHA-3 adds a different padding byte, so the hashes differ. Older libraries that implemented Keccak before the standard was final give different results.
How is SHA3-512 different from SHA-512?
They are unrelated designs: SHA-512 belongs to the SHA-2 family, while SHA3-512 uses the Keccak sponge. Both give 512-bit hashes, but the same input never produces the same value.
What is the SHA3-512 hash of an empty input?
It is a69f73cca23a9ac5c8b567dc185a756e97c982164fe25859e0d1dcc1475c80a615b2123af1f5f94c11e3e9402c3ac558f500199d95b6d3e301758586281dcd26. Leave the input empty and press the button to see it.
How long is a SHA3-512 hash?
Always 512 bits: 128 hexadecimal characters, or 88 characters in Base64, whatever the input size.
Why does my SHA3-512 differ from another tool?
Every byte counts. Text is hashed as UTF-8 with LF line breaks, including spaces and a final line break, so a trailing space or a Windows line break elsewhere changes the hash. Also check that the other tool is not computing the pre-standard Keccak-512.