About the SHA3-224 Hash Generator
SHA3-224 is the shortest member of the SHA-3 family standardised in FIPS 202. It emits 224 bits, written as 56 hexadecimal characters, and is built on the Keccak sponge construction rather than the Merkle Damgard chain used by SHA-1 and SHA-2. The sponge absorbs the message into a 1600-bit state and then squeezes the digest out of it, a design that sidesteps the length extension weakness that affects the older family.
The 224-bit size exists mainly for protocols that need a digest matching the security level of Triple DES or a 2048-bit RSA key without carrying a full 256 bits around. It offers about 112 bits of collision resistance, which is adequate for integrity checks in constrained formats but is not the size to reach for when designing something new. Note that SHA3-224 and the original Keccak-224 submission produce different digests, because NIST added a domain separation suffix before standardising.
The digest is calculated here by a WebAssembly build of Keccak, so long inputs hash quickly and nothing is transmitted. Output can be hex in either case or Base64 for headers and JSON fields. Use the Upload button to hash a file instead of pasted text. For the more widely deployed 256-bit variant see the SHA3-256 Hash Generator, and to compare a dozen algorithms side by side use the All Hash Generator.
How to use
- Paste the text you want to fingerprint into the left pane.
- Choose Base64 output if the digest is going into a header or a JSON field.
- Press Upload instead to hash the contents of a file.
- Copy the 56 character digest with the Copy button.
Common questions
- How long is a SHA3-224 hash?
- It is 224 bits, shown as 56 hexadecimal characters or 38 Base64 characters once padding is included.
- Is SHA3-224 the same as SHA-224?
- No. SHA-224 is a truncated SHA-2 variant. SHA3-224 uses the Keccak sponge and produces a completely different digest for the same input.
- Can a SHA3-224 hash be reversed?
- No. It is a one way function, though a short or common input can still be found by guessing against a dictionary.
- Does trailing whitespace change the digest?
- Yes. Every byte counts, so a trailing newline or space produces an entirely different hash.