SHA-3 Hash Generator

Keccak-based SHA3-256 and SHA3-512, the newest NIST standard, computed locally.
Client-side · verifiable
How this tool works

After the MD5 and SHA-1 breaks, NIST ran a public competition for a hash built on different principles from SHA-2. Keccak won in 2012 and became SHA-3 in 2015. Instead of the Merkle–Damgård chain that SHA-1 and SHA-2 share, it uses a sponge: input is absorbed into a 1600-bit state, permuted, and the digest squeezed out. That design is immune to length-extension attacks and would survive even if SHA-2 were broken tomorrow.

SHA-3 is not in the Web Crypto API, so this page runs it in WebAssembly, loaded on demand. Note that the Ethereum world uses Keccak-256 with the pre-standard padding, which gives different output from SHA3-256 for the same input.

Security note

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.

FAQ
Should I switch from SHA-256 to SHA-3?

Not unless a standard asks you to. SHA-2 remains unbroken and faster in hardware. SHA-3 is the insurance policy.

Why does my Ethereum hash not match SHA3-256?

Ethereum uses original Keccak-256 with 0x01 padding; the final SHA-3 standard uses 0x06. Same permutation, different padding, different output.

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.