Keccak-256 Hash Calculator

What is a cryptographic hash function?

A cryptographic hash function takes an input of any size and produces a fixed-length digest. Three properties define it: determinism (same input always gives the same output), pre-image resistance (you cannot reverse the hash to recover the input), and collision resistance (it is computationally infeasible to find two different inputs that produce the same digest).

What is Keccak?

Keccak is a family of cryptographic hash functions designed by Guido Bertoni, Joan Daemen, Michaël Peeters, and Gilles Van Assche. It won the NIST hash function competition in 2012 and became the basis for SHA-3. Unlike earlier designs such as MD5 or SHA-1, Keccak uses a sponge construction built on the Keccak-f permutation — a fundamentally different approach to hashing that avoids the Merkle–Damgård length-extension weakness. The four standard variants are Keccak-224, Keccak-256, Keccak-384, and Keccak-512, named by their output size in bits.

Are Keccak hashes safe for passwords?

No. All Keccak variants are designed to be fast, which is ideal for integrity checking but harmful for password storage — a fast hash lets attackers brute-force millions of candidates per second. For passwords, use a purpose-built slow algorithm: bcrypt, scrypt, or Argon2, all of which incorporate salting and adjustable work factors.

How does Keccalc ensure privacy?

All hashing runs entirely inside your browser using js-sha3 by emn178 — a pure-JavaScript library that computes Keccak digests locally without any network calls. No text, no file content, and no hash output is ever transmitted to any server. You can verify this by running the tool while offline — it works identically.

What output formats are available?

Hex (lowercase hexadecimal) is the most common format used in tooling and documentation. HEX is the same in uppercase. Base64 encodes the raw digest bytes as a compact string using the standard Base64 alphabet — note that the + and / characters are not URL-safe and require percent-encoding when embedded in a URL; use hex instead if URL embedding is needed. Binary shows each byte's individual bits, useful for educational and low-level inspection purposes.

What is Keccak-256?

Keccak-256 is the most widely deployed member of the Keccak family, producing a 256-bit (32-byte) digest represented as a 64-character hex string. It is the hash function used natively by Ethereum and predates the NIST standardisation of SHA-3 — importantly, Keccak-256 and SHA3-256 are not identical, differing in their padding scheme. Keccak uses a simpler 0x01 padding suffix while NIST SHA-3 uses 0x06, producing different outputs for the same input.

Where is Keccak-256 used?

Keccak-256 is the hash function at the core of Ethereum: it is used for address derivation (hashing a public key to produce a 20-byte address), transaction signing, block header commitments, and Solidity's built-in keccak256() opcode. Beyond Ethereum, it is also used in other EVM-compatible chains, the Tezos smart contract platform, and various blockchain protocols that adopted the pre-standardisation Keccak variant rather than the NIST SHA-3 finalisation.

Is Keccak-256 still secure?

Keccak-256 is considered secure against all known practical attacks. No collision has ever been demonstrated, and no pre-image attack is known. Its sponge construction provides formal security bounds and has received extensive cryptanalytic scrutiny since the SHA-3 competition began in 2007.

Can Keccak-256 be reversed or cracked?

Keccak-256 has no known mathematical inverse. Brute-forcing a 256-bit digest is computationally infeasible. For short or common inputs, precomputed rainbow tables could theoretically recover the original value — salt your data if that is a concern.

The Keccak family

The four Keccak variants share the same sponge construction and Keccak-f[1600] permutation, differing only in the capacity and rate parameters that determine digest length and security level. All four are based on the original pre-standardisation Keccak submission — not the NIST SHA-3 finalisation, which introduced a different padding suffix. If SHA-3 compatibility is required, use a SHA-3 library rather than Keccak.

Variant comparison

Algorithm	Digest	Rate	Capacity	Status	Common use
Keccak-224	224 bit · 56 hex	1152 bit	448 bit	Niche use	Constrained environments requiring a smaller digest
Keccak-256	256 bit · 64 hex	1088 bit	512 bit	Secure	Ethereum addresses, smart contracts, EVM chains
Keccak-384	384 bit · 96 hex	832 bit	768 bit	Secure	Higher-security contexts requiring a wider digest
Keccak-512	512 bit · 128 hex	576 bit	1024 bit	Secure	Maximum digest width, archival and high-security use

Which variant should I use?

Keccak-256 is the right default for almost all applications and the only choice for Ethereum compatibility. Keccak-384 and Keccak-512 offer wider digests and higher capacity for security-sensitive contexts, at the cost of slightly lower throughput. Keccak-224 should only be chosen in environments where a smaller digest size is a strict requirement.