SHA Hash Generator

SHA (Secure Hash Algorithm) is a family of cryptographic hash functions that turn text of any length into a fixed-length digest. Choose one of nine algorithms and the result updates as you type.

About SHA hashes:

• Any length of input produces a fixed-length digest
• The same input always produces the same digest
• Hashing is one-way: you cannot recover the original text from a digest
• SHA-256 and SHA-512 are the usual choices for signatures and integrity checks; SHA-1 is no longer recommended for security use

Digest lengths:

• SHA-1: 160 bits (40 hex characters)
• SHA-224 and SHA3-224: 224 bits (56 hex characters)
• SHA-256 and SHA3-256: 256 bits (64 hex characters)
• SHA-384 and SHA3-384: 384 bits (96 hex characters)
• SHA-512 and SHA3-512: 512 bits (128 hex characters)

FAQ:

• Q: Which algorithm is selected by default, and can I change it?
  A: SHA-256 is selected by default, so typing gives you a result right away and clearing the input clears the result. Click any other algorithm to switch and recalculate immediately. Your last choice is saved locally, so it is still selected next time.
• Q: How can I tell which algorithm produced a digest I was given?
  A: Paste the original text and click through the algorithm buttons until one matches; letter case does not matter. Length narrows it down: 40 hex characters means SHA-1, 56 means SHA-224, 64 means SHA-256, 96 means SHA-384 and 128 means SHA-512. SHA-2 and SHA3 digests of the same length cannot be told apart by length alone, so ask the other side for the algorithm name. An HMAC digest also needs the same key to reproduce.
• Q: Does the HMAC key work with all nine algorithms?
  A: Yes. Enter a key and the selected algorithm switches to HMAC; leave it empty for a plain hash. The key is treated as UTF-8 text. HMAC-SHA3 is not the same as NIST's KMAC — for API signatures, SHA-256 or SHA-512 HMAC is the safer choice, and both sides must agree on the algorithm.
• Q: Does per-line mode skip blank lines or trim spaces?
  A: Lines containing only whitespace are skipped. Every other line is hashed separately in its original order, and leading and trailing spaces are part of the hashed text.
• Q: Does Uppercase hex change the hash?
  A: No. It only changes the letter case of the text already in the result box; the digest itself stays the same. Results are recalculated when you edit the input, switch algorithms, change the HMAC key or toggle per-line mode.
• Q: Are my settings saved?
  A: Yes. The algorithm, HMAC key, uppercase hex and per-line mode are all stored in your browser and restored on your next visit.
• Q: Should I use SHA-1, SHA-256 or SHA3-256?
  A: Use whatever the other side requires — different algorithms produce completely different digests and cannot validate each other. SHA-1 is no longer recommended for security use; SHA-256 and SHA-512 are common for signature checks. SHA3 is based on Keccak, so pick it only when it is explicitly requested.

Common uses:

• Generate a digest to check whether text has been changed
• Verify API request signatures and webhook payloads
• Confirm that two copies of a message or query are identical
• Hash log lines or records one by one with per-line mode