SHA3-512 hash
Compute a SHA3-512 digest of any file, on your device.
Runs on your device. The file is never uploaded.
SHA3-512 hash prints 512 bits of Keccak sponge output as 128 lowercase hex characters, twice the width of SHA3-256. A larger capacity leaves a smaller rate, so it absorbs fewer bytes per permutation than the shorter one. The row hard-codes that 512, so no other SHA-3 length can be asked for here.
Questions
How long is a SHA3-512 digest?
512 bits, printed as 128 lowercase hex characters. The tool calls hash-wasm sha3 with a fixed 512-bit size, so the length is not adjustable on this page. Drop several files at once and each returns its own digest under its own file name, with no options to set on any of them.
How does it differ from SHA-512?
Only the length matches. SHA-512 belongs to the SHA-2 family and SHA3-512 is the Keccak sponge from FIPS 202, so the two produce entirely different digests for the same file. Neither is a fallback for the other, and a checksum published for one will never verify against the other.
Is SHA3-512 slower than SHA3-256?
It processes fewer bytes per permutation, because a larger digest means a larger capacity and therefore a smaller rate in the sponge. So yes, expect more work per byte than SHA3-256 for the same input. Whether you notice depends on the file size and your machine.
Is this the same as Keccak-512?
No. Keccak-512 uses the original padding from before standardisation, and SHA3-512 adds a domain separation suffix before padding. Same permutation, same output size, completely different digests. If you are reproducing a value from software written before FIPS 202 landed, use the Keccak-512 tool on this site instead of this one.
Are my files uploaded?
No. Hashing happens in this tab through a WebAssembly build of hash-wasm inside a Web Worker. There is no account, no upload and no server involved, and the site keeps working with the network switched off after the first visit.