SHA-3 (Keccak) Hash Generator (Free)

Free tool: calculate the SHA-3 hash (SHA3-224, SHA3-256, SHA3-384 or SHA3-512) of any string instantly in your browser. Standardized by NIST in 2015 as FIPS 202, SHA-3 uses a fundamentally different "sponge construction" from SHA-2, serving as an independent safety net.

Copied!

What Is SHA-3 Hashing?

SHA-3 hashing converts the string you enter into a fixed-length value. There are four output lengths — SHA3-224, SHA3-256, SHA3-384 and SHA3-512: SHA3-256 gives 256 bits (32 bytes, 64 hex digits) and SHA3-512 gives 512 bits (64 bytes, 128 hex digits). SHA-3 is the newest generation of hash function: based on Keccak, the winner of a competition decided in 2012, it was standardised by NIST in 2015 as FIPS 202. The same input always yields the same hash, while working the original string back from the hash is computationally impossible — the «one-way» property. Pick an output length and type into the input box, and this tool computes the SHA-3 hash in your browser in real time.

SHA-3's defining feature is that it uses a fundamentally different design from SHA-2 (SHA-256, SHA-512 and so on), called a «sponge construction». Should some vulnerability ever be found in SHA-2, SHA-3 is thought unlikely to be affected because the design principle differs — which is why it is positioned as cryptographic «insurance». The calculation happens entirely inside your browser; the string you enter is never sent to a server.

How to Use the SHA-3 Hash Calculator

  1. Enter the string you want hashed Type into the input box whatever you want a hash for — a password, the contents of a file, and so on.
  2. Read the SHA-3 hash Choose an output length (SHA3-224, SHA3-256, SHA3-384 or SHA3-512) and the SHA-3 hash appears in real time as a hexadecimal string as you type. The default is SHA3-256 (64 hex digits).
  3. Copy it if you need to Press «Copy» and the hash currently shown goes to your clipboard, ready to paste straight into test code or a comparison.

Tips for getting more out of it

  • SHA-3 is based on the Keccak algorithm selected through a NIST competition (2007–2012) and was standardised in 2015 as FIPS 202. Like SHA-2, it has four output lengths, and this tool lets you switch between them.
  • While SHA-2 uses a Merkle–Damgård construction, SHA-3 adopts a "sponge construction" — a fundamentally different design philosophy. This means attacks that work against SHA-2 cannot be directly applied to SHA-3.
  • No known vulnerabilities have been found in SHA-3. However, SHA-256 has a far larger track record in production, so for systems prioritizing compatibility with existing infrastructure, SHA-256 remains the practical choice.
  • Ethereum uses its own Keccak-256 — the version of Keccak before NIST finalized the SHA-3 standard — which differs subtly from NIST SHA-3. Ethereum-specific hash computations require dedicated implementations.
  • SHA-3's bit-manipulation-based design lends itself to efficient hardware implementations (FPGA/ASIC). In software, it can be slightly slower than SHA-256.

When SHA-3 Hashing Comes in Handy

Verifying a hash function in a new system

When you are weighing SHA-3 for a system you are about to design, you can check the actual output in the browser at once and line it up against what your implementation produces.

Understanding specifications that use Keccak-family hashes

While researching a specification that adopts its own Keccak-256 — as Ethereum does — you can set the NIST-standard SHA3-256 value this tool produces beside the Keccak-256 value from the specification or your implementation and confirm that the two do not match.

As teaching material for cryptography and algorithm comparison

If you want to see how far SHA-3 and the SHA-2 family diverge for the same input, lining them up in the multi-hash calculator makes the point clearer.

Deciding between SHA-3 and SHA-256

When you are unsure whether compatibility with an existing system should push you to SHA-256, you can generate both hashes and check the format you will write into the specification. For SHA-256 use the SHA-256 hash calculator.

SHA-3 Terms Explained

SHA-3
The name of the hash function NIST standardised in 2015 as FIPS 202, based on the Keccak algorithm. Four output lengths are defined — SHA3-224, SHA3-256, SHA3-384 and SHA3-512 — and this tool can switch between all of them (SHA3-256 by default).
Keccak
The algorithm designed by a Belgian research group and chosen in NIST's SHA-3 competition. «SHA-3» is what it is called after NIST's standardisation; Keccak itself refers to a broader concept that predates it.
Sponge Construction
SHA-3's design approach, in which input data is «absorbed» into an internal state and output is «squeezed» out to whatever length is needed. It differs from the Merkle–Damgård construction that SHA-2 adopts — a structural difference that makes attacks on SHA-2 hard to carry over.
Collision Resistance
The property that makes it hard for two different inputs to produce the same hash. No practical collision-finding attack has been found against SHA-3 to date, so it can be used safely for digital signatures and tamper detection.
How It Differs from SHA-2
SHA-2 (SHA-256, SHA-512 and so on) and SHA-3 have similar names but are entirely separate lines of algorithm with quite different internals. NIST did not seek a replacement for SHA-2 but an alternative should SHA-2 ever be broken.
One-Way Hash Function
A function for which computing the output from an input is easy, but working the input back from the output is computationally impossible. SHA-3 has this property too, but because it is fast to compute it is weak against brute-force and dictionary attacks, so dedicated algorithms such as Argon2id or bcrypt are recommended for storing passwords.

FAQ

Both are secure today. SHA-256 is the practical choice for compatibility with existing systems, while SHA-3 is a good option for new designs that benefit from an independently designed algorithm.

No — Ethereum adopted Keccak before the NIST standard was finalized. The two differ in their padding rules, so the same input produces different hash values. Ethereum-specific computations require a dedicated Keccak implementation.

No. SHA-3 is a one-way hash function, meaning it is computationally infeasible to reverse a hash back to the original input, which makes it well suited to data integrity checks. However, because it is fast to compute, attackers can hash huge lists of likely passwords and compare them, so for storing passwords dedicated algorithms such as Argon2id or bcrypt are recommended.
Tool-kun

Side Note — The Birth of Keccak and the NIST Competition: Five Years to Crown the Next Standard

In November 2007, as collision attacks on SHA-1 began to look increasingly realistic, NIST announced the "SHA-3 Competition." Sixty-four algorithms were submitted from around the world. After approximately five years of evaluation, in October 2012 Keccak — designed by a Belgian team (Joan Daemen, Gilles Van Assche, Guido Bertoni, Michaël Peeters) — was selected, and after some details such as the padding were adjusted it was formally standardised as FIPS 202 in August 2015. Daemen had previously co-designed AES (Rijndael), making this a remarkable "double crown" in modern cryptography.

What makes the SHA-3 competition fascinating is that NIST was not seeking a replacement for SHA-2, but rather insurance against SHA-2 being broken. SHA-2 has remained secure to this day, so SHA-3 is positioned as a parallel standard. The fundamental difference in design means attacks against SHA-2 cannot be directly applied to SHA-3.

Keccak's "sponge construction" models data processing as absorbing input and then squeezing out however many output bits are needed. This design has also been extended into SHAKE128 and SHAKE256 — extendable-output functions (XOFs) that can produce arbitrary-length output — opening new possibilities in cryptographic design.