Hash Generator - SHA-1, SHA-256, SHA-384, SHA-512 (Text & File)

SHA-1, SHA-256, SHA-384 and SHA-512 — every algorithm exposed by the browser's Web Crypto API. The digest is shown as a lowercase hexadecimal string, which is the format expected by checksum files, package manifests and HMAC tooling.

They differ in output length and design generation. SHA-256 is the modern default for integrity checks and most blockchain use. SHA-384 and SHA-512 produce longer digests that resist length-extension attacks. SHA-1 is shown for legacy compatibility but is no longer considered safe against collision attacks.

MD5 is broken: collision attacks are practical on a laptop, so it must not be used for security-sensitive work. We intentionally omit it to discourage new code from depending on it. For non-security uses like cache keys, prefer SHA-256 truncated to the size you need.

Both. Paste a string or drop a file into the input box — the tool reads the file as a binary stream and feeds it directly to the hashing API, so the digest matches the one produced by sha256sum, openssl dgst or PowerShell's Get-FileHash.

No. Cryptographic hashes are one-way functions: given a digest, there is no efficient way to recover the input. That is the entire point — integrity checks, password storage and signatures all rely on this property.

No. The Web Crypto API runs the hash inside your browser, so the input never crosses the network. That makes the tool safe for secrets, private keys and any file you would not want to upload.