Overview
Introduction
Keccak and SHA-3 are close enough that most people use the names interchangeably, and most of the time that's harmless, except when you actually need Ethereum-compatible hashes, where the difference is the entire point.
This tool computes raw Keccak-256, the pre-standardization padding Ethereum still uses everywhere, entirely in your browser, distinct from the SHA3-256 tool elsewhere in this category.
What Is Keccak Hash Calculator?
Keccak is the sponge-construction hash function family designed by Bertoni, Daemen, Peeters, and Van Assche, which won NIST's SHA-3 competition; Keccak-256 specifically refers to the 256-bit-output configuration with its original, pre-standardization padding rule.
When NIST formalized Keccak into FIPS 202 as SHA-3, they added a domain-separation suffix (the 0x06 byte) to the padding, a small but consequential change that means raw Keccak-256 and SHA3-256 produce different digests for the same input despite sharing the same permutation.
How Keccak Hash Calculator Works
Your UTF-8 text is absorbed into a 1600-bit Keccak sponge state at a 256-bit-security rate, using Keccak's original multi-rate padding (without the later-added 0x06 SHA-3 domain byte).
After absorbing all input, the sponge is squeezed to produce 256 bits of output, hex-encoded into the 64-character digest this tool returns.
When To Use Keccak Hash Calculator
Use this specifically when you need to match Ethereum's hashing: computing an address from a public key, a transaction hash, a Solidity function selector, or any other Ethereum-ecosystem value.
For any new, non-Ethereum-specific design, prefer standardized SHA3-256 (this category's dedicated tool) instead, since it's the actual NIST-standardized algorithm most other systems and auditors expect.
Often used alongside SHA3-256 Hash Calculator, SHA-3 Hash Calculator and SHAKE Hash Calculator.
Features
Advantages
- Exactly matches Ethereum and other blockchain systems built on the same pre-standardization Keccak padding.
- Shares Keccak's strong sponge-construction security properties with SHA-3, just a different padding convention.
- Computed natively in JavaScript (no WebAssembly needed), since @noble/hashes implements raw Keccak directly.
Limitations
- Not the NIST-standardized SHA-3 algorithm; using it where SHA3-256 is actually expected will produce a mismatching digest.
- The Keccak-256/SHA3-256 naming confusion is a genuine, recurring source of interoperability bugs across projects.
- Less broadly recognized outside blockchain contexts than standardized SHA3-256.
Examples
Best Practices & Notes
Best Practices
- If you're building anything Ethereum- or blockchain-adjacent, confirm explicitly whether the spec means raw Keccak or standardized SHA-3, don't assume.
- For general-purpose new work outside blockchain contexts, prefer this category's SHA3-256 tool, the actual NIST standard.
- When debugging a hash mismatch between two systems, check the padding convention (raw Keccak vs. SHA-3) before assuming either implementation is buggy.
Developer Notes
Uses @noble/hashes/sha3.js's keccak_256 export directly (not hash-wasm), since noble implements the raw, pre-standardization Keccak padding natively in pure JavaScript, distinct from the same library's sha3_256 export used elsewhere in this category. Verified by computing the digest directly against this exact dependency and cross-checking the result against widely published Keccak-256 reference values for common test strings.
Keccak Hash Calculator Use Cases
- Computing an Ethereum address or transaction hash component by hand
- Reproducing a Solidity function selector (the first 4 bytes of a Keccak-256 hash of its signature)
- Debugging a mismatch between a Keccak-256-based system and a standard SHA3-256 implementation
- Comparing raw Keccak against standardized SHA-3 output for the same input to see the padding difference firsthand
Common Mistakes
- Using this tool's output where standardized SHA3-256 was actually expected, or vice versa, they are not interchangeable.
- Assuming any tool labeled "SHA-3" computes what Ethereum calls "Keccak-256"; always confirm which padding convention a specific system actually uses.
- Expecting web3/blockchain library documentation to always clearly distinguish "Keccak" from "SHA-3"; many use the names loosely even though the digests differ.
Tips
- Run the same input through this tool and the SHA3-256 tool side by side to see concretely how the padding difference changes every output bit.
- If you're not working with Ethereum or a similar Keccak-based blockchain system, you almost certainly want the standardized SHA3-256 tool instead.