SHA Hash Generator

Generate SHA-1, SHA-256, SHA-384, and SHA-512 hashes using browser-native Web Crypto.

SHA Hash Generator

Client-side

About this tool

The SHA Hash Generator computes cryptographic hash digests using the browser's built-in Web Crypto API — no external library, no server round-trip. Enter any text and instantly receive the SHA-1, SHA-256, SHA-384, and SHA-512 hashes in hexadecimal format.

SHA (Secure Hash Algorithm) functions are one-way: given any input, they produce a fixed-length fingerprint. Even a single character change produces a completely different hash. This property makes SHA-256 and SHA-512 the standard for data integrity verification, digital signatures, password hashing salts, and API request signing (via HMAC).

This tool uses SubtleCrypto.digest(), the W3C Web Crypto standard implemented natively in all modern browsers. Because it calls the browser's own cryptographic primitives — the same ones used by TLS — there is no risk of a buggy third-party library introducing weaknesses. Open your browser's Network panel while computing a hash: you will see zero outbound requests. Your input never leaves the browser.

Note: SHA-1 is cryptographically broken for collision resistance and should not be used for security applications. It remains useful for non-security checksums and legacy compatibility.

FAQ

What is the difference between SHA-256 and SHA-512?

Both are secure. SHA-256 produces a 256-bit (64-character hex) digest and is faster on 32-bit systems. SHA-512 produces a 512-bit (128-character hex) digest and is faster on 64-bit hardware. For most applications, SHA-256 is the right default.

Can I reverse a SHA hash to get the original text?

No. SHA functions are one-way by design. There is no algorithm to reverse them. Brute-force dictionary attacks against common inputs (like passwords) are possible, which is why passwords should use bcrypt or Argon2 instead of raw SHA.

Is SHA-1 safe to use?

Not for security purposes. SHA-1 is vulnerable to collision attacks (two different inputs producing the same hash). It was deprecated in 2011. Use SHA-256 or SHA-512 for any new security-sensitive applications.

Does the hash change if I add a space at the end?

Yes, any difference in input — including whitespace — produces a completely different hash. This is the avalanche effect and is a fundamental property of cryptographic hash functions.