Skip to content
ZeroServer.tools

SHA-224 Hash Generator

Generate a SHA-224 hash from any text — or drop in a file to checksum it, and paste a known hash to verify.

Input text
13 characters
Drop a file or click to hash its bytesComputes the SHA-224 checksum from the file contents, in chunks with progress
SHA-224 Hash (224-bit)

How SHA-224 hashing works

SHA-224 is a truncated variant of SHA-256: it runs the same compression function with different initial hash values and simply drops the last 32 bits of the output, producing a 224-bit (56-hex- character) digest instead of 256-bit. It belongs to the SHA-2 family defined in FIPS 180-4 and remains cryptographically sound today, though SHA-256 is more common in practice. Because browsers' native crypto.subtle API does not implement SHA-224, this tool computes the digest with the battle-tested crypto-js library instead — entirely in your browser. Your text is never sent anywhere.

Built and maintained by Meet Shah · Last updated

What this tool is used for

  • Matching a system that specifies SHA-224 explicitly, usually for a fixed field width.
  • Producing a digest that fits a 28-byte field without truncating a longer one yourself.
  • Working through a standards exercise that contrasts the SHA-2 truncated variants.
  • Reproducing a checksum from a protocol that chose 224 bits deliberately.
  • Comparing output sizes across the SHA-2 family for a design decision.

Frequently Asked Questions

What exactly is SHA-224?
SHA-256 run with a DIFFERENT set of initial hash values, with the output truncated to 224 bits. The different IV is essential: it means SHA-224(m) is not simply a prefix of SHA-256(m), so the two cannot be confused or interchanged.
Why would anyone want 224 bits?
It matches the security level of 3DES and of 2048-bit RSA, and pairs with the NIST P-224 curve. It exists mostly so protocols standardised around a 112-bit security target have a hash of matching strength rather than an oversized one.
Is it faster than SHA-256?
No — it performs exactly the same work and only discards 32 bits at the end. Choosing SHA-224 buys a shorter digest, never speed. If output size does not matter to you, use SHA-256.
Is it vulnerable to length extension?
Only partially. Truncation withholds 32 bits of internal state from the attacker, so the classic extension attack does not work directly — but this is a side effect, not a security guarantee. Use HMAC regardless.
How long is the output?
224 bits, or 56 hexadecimal characters. It is the only SHA-2 digest whose hex length is not a power-of-two-friendly number, which makes it easy to spot in logs.
Why does SHA-224 exist?
To match the 112-bit security level of Triple-DES, so protocols pairing them are balanced. It is SHA-256 with different initial values and a truncated output, which also makes it length-extension resistant where SHA-256 is not.

Common errors and gotchas

  • Expecting it to be faster than SHA-256. It runs the same compression function and simply publishes less of the result.
  • Truncating a SHA-256 digest to 28 bytes and calling it SHA-224. The initial values differ, so the outputs differ.
  • Assuming the truncation makes it length-extension resistant in the way SHA-512/224 is. The margin is different.
  • Choosing it for new work with no field-width constraint, where SHA-256 is better supported everywhere.
  • Reading 56 hex characters as unambiguous. Other algorithms produce the same length.

Related Cryptography & Security tools

Private & free — this tool runs entirely in your browser.

IndieKitShip your Next.js startup in days.affiliate