Generate SHA-1, SHA-256, SHA-384, and SHA-512 hashes from text or files using the browser's native Web Crypto API. Nothing is uploaded.
This hash generator computes cryptographic digests of any text or file using your browser's native Web Crypto API, producing SHA-1, SHA-256, SHA-384, and SHA-512 hashes side by side in a single pass.
A cryptographic hash function turns any input — a short string or a multi-gigabyte file — into a fixed-length hexadecimal digest. The same input always produces the same digest, but even a one-byte change yields a completely different result, which is exactly what makes hashes useful for verifying that data has not been altered. This tool hashes text as UTF-8 bytes, so the digest you see here will match any other correctly implemented SHA function fed the identical byte sequence. For files, it reads the raw bytes directly, giving you the same checksum a publisher would list next to a download. SHA-1 is included because it is still widely encountered, but it is shown clearly marked as deprecated for security work, while SHA-256 is flagged as the recommended modern default. People use it to:
Everything runs locally through Web Crypto — your text and files are hashed in the browser and nothing is ever uploaded to a server, so even sensitive inputs stay entirely on your device.
Use SHA-256 for anything new — it's the modern security standard. SHA-1 is broken for security but still common for cache keys. For password storage use bcrypt, scrypt, or Argon2, not raw SHA.
No. The Web Crypto API hashes the bytes locally — your file never leaves the browser.
Trailing newlines, BOMs, or different encodings (UTF-8 vs UTF-16) change the bytes that get hashed. Make sure both sides hash the exact same byte sequence.
They are all members of the SHA-2 family and differ mainly in digest length: SHA-256 produces a 256-bit hash, SHA-384 a 384-bit hash, and SHA-512 a 512-bit hash. SHA-384 and SHA-512 use 64-bit internal operations, which can be faster on 64-bit hardware and offer a larger output. For most purposes SHA-256 is plenty; choose SHA-512 when a longer digest is specifically required.
No, not for security purposes. Both MD5 and SHA-1 have practical collision attacks, meaning two different inputs can be forced to share a hash, so they should never be used for signatures, certificates, or password handling. SHA-1 is offered here only for compatibility with older systems and non-security checks. Use SHA-256 or SHA-512 for anything that needs to resist tampering.
Hashing creates a compact fingerprint of data that changes completely if even one byte changes. Publishers list a file's SHA-256 checksum next to a download so you can hash the file you received and compare the two values — if they match, the file arrived intact and untampered. Hashes are also used for cache keys, deduplication, and content fingerprinting.
No. Cryptographic hashes are one-way functions, so there is no operation that turns a digest back into the original text or file. Attackers only recover inputs by guessing — trying candidates and hashing them until one matches — which is why short or predictable inputs are weak. The digests this tool produces cannot be decrypted; they can only be regenerated from the same input.