Hash a line of text with MD5, SHA-1 and SHA-256 side by side. The digests update as you type, and nothing is sent to a server.
Runs in your browser — nothing is uploaded
MD5 and SHA-1 are fine for checksums and deduplication, but they are broken for security purposes. Use SHA-256 or a dedicated password hash such as bcrypt or Argon2 for passwords.
A hash function turns any input into a fixed-length fingerprint. The same text always produces the same digest, and even a one-character change produces a completely different one. Developers use hashes to verify downloads, build cache keys, detect duplicate records and create test fixtures.
MD5 produces 128 bits and SHA-1 produces 160 bits. Both are still useful for checksums and deduplication, but collisions can be deliberately constructed, so they must not be used for signatures, certificates or password storage. SHA-256 produces 256 bits and is the usual choice for integrity checks.
The three digests are computed from the UTF-8 bytes of your text, which matches how most languages and command-line tools hash the same string. Comparing the output with sha256sum or md5sum on your machine is a quick way to confirm that two systems agree.
For security, no. Researchers have produced MD5 collisions, meaning two different inputs with the same digest, so it must not protect passwords, signatures or certificates. It remains acceptable for non-adversarial uses such as detecting accidental corruption or generating cache keys.
Do not use any of these plain hashes for passwords. Use a password-specific algorithm such as bcrypt, scrypt or Argon2, which are deliberately slow and salted. A fast hash like SHA-256 lets an attacker test billions of guesses per second on a GPU.
Usually the bytes differ. A trailing newline added by an editor, a different character encoding, or Windows line endings change the input and therefore the digest. Compare the exact bytes, for example by hashing the file itself rather than a copy pasted into a text box.
No. The digests are calculated in your browser with JavaScript. The page does not send your input to a server, so you can hash internal strings or secrets without exposing them.
Compute the SHA-256 of the downloaded file with sha256sum on Linux, shasum -a 256 on macOS, or Get-FileHash on Windows, then compare the 64-character hex string with the value published by the project. This page is best for short text; large files should be hashed with a command-line tool.
Lowercase hex is the convention used by most libraries and command-line tools, so the digests line up with what you will see elsewhere. Hex is a readable way to write the raw bytes; the underlying digest is the same regardless of case.