SHA Hash Generator

Generating a SHA hash computes a fixed-length cryptographic digest of any text entered, across 13 algorithms spanning the SHA-1, SHA-2, and SHA-3 families. There is no length limit on the input beyond available browser memory, and the result displays alongside the bit length of the digest produced.

Three algorithm families are available. SHA-1 provides the original 160-bit digest. SHA-2 includes SHA-224, SHA-256, SHA-384, SHA-512, SHA-512/224, and SHA-512/256, each producing a fixed-length digest ranging from 224 to 512 bits. SHA-3 covers SHA3-224, SHA3-256, SHA3-384, SHA3-512, and the two extendable-output functions SHAKE128 and SHAKE256, whose output length is configurable to any multiple of 8 bits between 8 and 4096.

SHA-1 produces a 160-bit, 40-character hexadecimal digest. SHA-256 produces 256 bits, 64 hex characters. SHA-512 produces 512 bits, 128 hex characters. SHA3-256 also produces 256 bits but reaches it through the Keccak sponge construction rather than the Merkle-Damgard structure SHA-2 uses, a different internal design behind the same output length. The SHAKE extendable-output functions allow an arbitrary digest length, which suits key derivation or a fingerprint sized to fit a specific field rather than a fixed 224-to-512-bit output. Every other algorithm here always returns the same bit length no matter how long or short the input text is, which is what makes a digest useful as a fixed-size stand-in for data of any size.

Output defaults to lowercase hexadecimal, with uppercase hexadecimal and Base64 available as alternatives, and auto-hashing on every keystroke can be turned on for continuous feedback while typing. All computation runs locally in the browser: SHA-1 and SHA-256 use the built-in Web Crypto API, while SHA-224, SHA-512/224, SHA-512/256, and the entire SHA-3 family run through a pure-JavaScript Keccak implementation bundled in the page, so no text or hash data is transmitted to a server regardless of which algorithm is selected.

Cryptographic hashes serve as fixed-length fingerprints for arbitrary data. The following scenarios illustrate how different SHA variants apply across disciplines.

• Software Distribution: Verify downloaded files by comparing a published SHA-256 or SHA-512 checksum against a locally computed digest of the file content before installation.
• Password Storage Research: Examine how raw SHA-1 or SHA-256 digests of common passwords appear, illustrating why salting and key-stretching algorithms like bcrypt are preferred over plain SHA hashing in production systems.
• Data Deduplication: Compute SHA-256 digests of text blocks, database rows, or document fragments to detect duplicates without comparing full content. Identical hashes indicate identical inputs with negligible collision probability.
• Blockchain and Ledger Prototyping: Hash transaction payloads with SHA-256 or SHA3-256 while building proof-of-concept ledger applications. Compare the output of SHA-2 and SHA-3 families to evaluate which standard a protocol should adopt.
• API Signature Verification: Reproduce HMAC or hash-based API signatures by generating the SHA digest of a concatenated key-plus-message string. Match the result against the expected signature to debug authentication failures.
• Digital Forensics: Produce SHA-384 or SHA-512 digests of evidence text to establish chain-of-custody records. Higher bit lengths reduce collision risk in legal or regulatory contexts.
• Cryptography Education: Observe how a single-character change in the input produces a completely different digest, demonstrating the avalanche effect. Compare SHA-2 and SHA-3 output side by side to study structural differences between Merkle-Damgard and sponge constructions.
• Key Derivation Prototyping: Use SHAKE128 or SHAKE256 with a custom output length to generate key material of an exact bit size required by a symmetric cipher or protocol specification.
• Content Addressing: Assign SHA-256 or SHA3-256 hashes as unique identifiers for text snippets in content-addressable storage systems, enabling retrieval by digest rather than filename or path.