Hash Generator

Type or paste any string and get four hash digests at once: SHA-1, SHA-256, SHA-384, and SHA-512. All computed in parallel because waiting for one at a time would be silly. Each result gets its own copy button.

Common use cases

Verifying file integrity. Download a file, hash it, compare against the published hash. If they match, the file wasn't tampered with in transit.

Generating deterministic IDs. Same input always produces the same output. Useful for content addressing, cache keys, and deduplication.

Checking password hashes. You hash passwords before storing them so that even if the database leaks, the actual passwords aren't exposed. This tool lets you see what a given string hashes to.

Things to know

When to use which algorithm. SHA-256 is the right choice for almost everything today: integrity checks, content addressing, deterministic IDs. SHA-1 still shows up in legacy systems (git uses it for commit hashes, though it's slowly migrating to SHA-256). SHA-512 produces a longer digest and works well when you need extra collision resistance or you're on a 64-bit system where it's actually faster than SHA-256. SHA-384 is a truncated SHA-512, mostly used in specific TLS cipher suites.

MD5 isn't here. That's intentional. MD5 has known collision vulnerabilities since 2004. Someone can craft two different inputs that produce the same hash. If you're reaching for a hash function in 2026, SHA-256 costs you nothing extra and doesn't come with an asterisk.

Hashing and encryption are different things. Encryption is reversible with the right key. Hashing isn't. That's the whole point. Each hash displays as a lowercase hex string, the standard representation for config files, verification scripts, and documentation.

Privacy

Runs entirely in your browser using the Web Crypto API. Your input never touches a server. There's nothing to intercept because there's nothing to send. Hash your API keys, deployment secrets, whatever. We literally can't see them.