Text & Productivity

Cryptographic Hash Generator

Generate cryptographic hashes of any text — MD5, SHA-1, SHA-256, SHA-384 and SHA-512 — all at once and updating as you type. A hash is a fixed-length fingerprint of the input: the same text always produces the same digest, and the smallest change produces a completely different one. Everything is computed in your browser using its built-in cryptography, so the text never leaves your device.

How to use this tool

  1. Type or paste the text you want to hash into the box.
  2. All five digests appear and update instantly as you type.
  3. Press Copy on any row to put that digest on your clipboard.
  4. Use SHA-256 or stronger for anything security-related; MD5 and SHA-1 are marked “legacy” because they are no longer considered secure.
  5. Nothing is uploaded — the hashing uses your browser’s built-in cryptography.

The formula

A hash function maps input of any length to a fixed-length digest. It is deterministic (same input, same output) and one-way (you cannot recover the input from the digest). A good hash is also collision-resistant: it is infeasible to find two inputs with the same digest.

digest = H(utf8_bytes(text)) SHA-256 → 256 bits → 64 hex characters SHA-512 → 512 bits → 128 hex characters
H
The hash function — MD5, SHA-1, SHA-256, etc.
digest
The fixed-length output, shown here in hexadecimal
deterministic
The same input always yields the same digest

The text is encoded as UTF-8 bytes before hashing, so these digests match those produced by command-line tools such as sha256sum on the same input.

Worked examples

A classic test phrase

Given
“The quick brown fox jumps over the lazy dog” in MD5
Result
9e107d9d372bb6826bd81d3542a419d6

This pangram is a common hashing test. Change a single letter and the digest changes completely — an effect known as the avalanche property.

The empty string

Given
No text at all, in SHA-256
Result
e3b0c44298fc1c14…b855

Even empty input has a defined hash. This particular value is worth recognising, as it often appears where a field was left blank.

Verifying a download

Given
A checksum published next to a file
Result
Match confirms integrity

Hashing the file and comparing to the published digest confirms the file arrived intact and unaltered. This tool hashes text; a file’s checksum works the same way on its bytes.

Frequently asked questions

For anything security-related, use SHA-256 or stronger. SHA-256 is the modern default and is widely trusted. SHA-384 and SHA-512 offer larger digests for higher-assurance needs. MD5 and SHA-1 are included for compatibility with older systems and checksums, but both are broken and should never protect anything that matters.

Both have known collision attacks: researchers can deliberately craft two different inputs that share a digest, which defeats their use in signatures or integrity checks. They remain fine as fast, non-security checksums — deduplicating files, for example — but not for anything an attacker might target.

No. Hashing is one-way by design; the digest discards the information needed to reconstruct the input. So-called “hash decryption” sites simply look up precomputed hashes of common inputs — which is exactly why unique, unpredictable inputs matter for passwords.

No. The SHA hashes use your browser’s built-in Web Crypto API and MD5 runs in a small script on the page. All computation happens locally, the text is never transmitted, and there is no account or logging.

Yes. These are standard algorithms, so identical input produces identical output everywhere. The text is treated as UTF-8, so the digests also match common command-line tools like md5sum and sha256sum on the same bytes.

That is the avalanche effect, and it is intentional. A good hash function spreads any change across the entire output, so even a one-bit difference in the input flips roughly half the output bits. It is what makes a hash a reliable fingerprint.