The MD5 of 123456 is e10adc3949ba59abbe56e057f20f883e. That exact string sits in every cracking table ever published, which is why hashing passwords with MD5 is not a security measure — it is a formality.
The numbers, side by side
| Algorithm | Output | Hex characters | Status |
|---|---|---|---|
| MD5 | 128 bits | 32 | broken — collisions are practical |
| SHA-1 | 160 bits | 40 | broken — SHAttered, 2017 |
| SHA-256 | 256 bits | 64 | fine for integrity, not for passwords |
| SHA-512 | 512 bits | 128 | same job, longer output |
Hash hello and SHA-256 returns 2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824. Change one letter and all 64 characters change — the output gives no hint about the input.
A hash is not encryption
There is no key, so there is nothing to decrypt. “MD5 decryption” sites are lookup tables and brute force, not mathematics. A hash is a one-way fingerprint, and the security question is never “can it be reversed” but “can two different inputs produce the same output.”
For MD5 the answer has been yes since 2004, and constructing collisions now takes seconds. SHA-1 fell publicly in 2017, when two different PDF files were published with the same digest.
The 16-character MD5 trap
The MD5 tool prints four values: 32 and 16 characters, lower and upper case. The 16-character form is not a different algorithm — it is the middle 16 characters of the 32-character digest, half the bits. Some old systems stored only that slice. When two systems disagree about a hash, check which substring each one took. The short form is weaker and worth replacing, not preserving.
Where each one belongs
- File integrity, cache keys, dedup, deterministic IDs: SHA-256. It is not for security use as a signature, but it is reliable for detecting accidental changes.
- MD5 or SHA-1: only as a non-security checksum where nobody has an incentive to forge it. In a production auth path, treat either as a bug report.
- Passwords: bcrypt, scrypt, or Argon2 with a per-user salt. SHA-256 is fast, which is precisely the wrong property for password storage. The bcrypt generator makes a correctly salted hash without exposing your input.
- Signatures, tokens, JWT: verification must happen server-side with a secret or public key. A hash computed in the browser proves nothing, because the client can send whatever it likes.
Both the text to hash tool and the MD5 tool run entirely in your browser — CryptoJS and a local implementation respectively, with no upload. That matters when the input is a secret.
If you have a choice, hash with SHA-256 and store passwords with bcrypt. If you inherit a system that uses MD5, do not migrate the hashes — migrate the users, by rehashing on their next login.