Tools

Hash generator

Compute cryptographic hashes of any text right in your browser. Enter a string and get its SHA-1, SHA-256, SHA-384, and SHA-512 hex digests instantly, each in a copyable row. Hashing runs through the built-in Web Crypto API, so your input never leaves the browser: no upload, no network call, no storage.

Text to hash

Type or paste any text. All four digests update as you type. Everything is computed in your browser and nothing is ever sent anywhere.

0 characters

SHA-1

160-bit

Enter text above to compute this digest.

SHA-256

256-bit

Enter text above to compute this digest.

SHA-384

384-bit

Enter text above to compute this digest.

SHA-512

512-bit

Enter text above to compute this digest.

Why no MD5? MD5 is not available in the browser's Web Crypto API, and it is cryptographically broken: practical collisions make it unsafe for integrity or security. Prefer SHA-256 or stronger.

What is a cryptographic hash?

A cryptographic hash function maps input of any length to a fixed-size digest. The same input always produces the same output, a single changed byte produces a completely different digest, and you cannot practically reverse the digest back into the original input. That makes hashes ideal for verifying file integrity, deduplicating content, building checksums, and fingerprinting data. This tool uses the SHA-2 family (SHA-256, SHA-384, SHA-512) plus SHA-1, all provided natively by your browser.

Note that a hash is not encryption: there is no key and nothing to decrypt. And hashing alone is not a safe way to store passwords; that requires a slow, salted key-derivation function such as bcrypt, scrypt, or Argon2.

Frequently asked questions

Is my input sent to a server?: No. This tool runs entirely in your browser using the built-in Web Crypto API (crypto.subtle.digest). Nothing you type is uploaded, logged, or stored. You can even disconnect from the network and it keeps working.
Why is there no MD5 option?: MD5 is not part of the browser's Web Crypto standard, so it cannot be computed with crypto.subtle. It is also cryptographically broken (collisions can be produced cheaply), so it should not be used for integrity or security. Use SHA-256 or stronger instead.
Which SHA algorithm should I use?: SHA-256 is the sensible default for checksums, fingerprints, and general integrity checks. SHA-384 and SHA-512 offer larger digests and are common in higher-assurance contexts. SHA-1 is included for compatibility with legacy systems, but it is deprecated for security use because collisions are practical.
What encoding is used before hashing?: The text is encoded as UTF-8 bytes (via TextEncoder) before hashing, which matches what most languages and command-line tools do by default. Digests are shown as lowercase hexadecimal.
Will the same input always produce the same hash?: Yes. Hash functions are deterministic: identical input bytes always yield the identical digest. That is exactly why hashes work for verifying that a file or string has not changed.