Text
Hashed as UTF-8 bytes — the encoding a server would use for a submitted string.
File
Hashed as raw bytes, so the digest matches checksums such as an Ethereum address.
No file selected.
The file is read into memory and hashed locally. It is never uploaded, stored, or written anywhere.
Digests
All four variants are produced in one pass.
Enter text on the left or choose a file to see SHA3-256, Keccak-256, SHA3-512 and Keccak-512 digests.
SHA3-256 vs Keccak-256
Same input, same sponge, one different byte — and therefore a completely different digest. Pick the one your system expects.
No input yet — nothing to compare.Standardised SHA-3 (FIPS 202). The padding differs from Keccak-256, so the digests are not interchangeable.
No input yet — nothing to compare.Original Keccak submission (pre-standardisation padding). Used by Ethereum and several other systems.
- SHA3-256 is the standardised FIPS 202 hash (padding byte 0x06). It is what most documentation means by "SHA-3".
- Keccak-256 keeps the pre-standardisation padding (0x01) and is what Ethereum uses — an Ethereum address is the last 20 bytes of this digest.
- A SHA3-256 digest will never match a Keccak-256 digest for the same input. Copy the one your system asks for.
- A hash is a one-way fingerprint, not encryption. It proves integrity, not secrecy — never hash a password you need to recover.
Runs entirely in your browser. No network request, no storage, no analytics — the input exists only until you clear it.