Hash Generator
Compute MD5, SHA-1 and SHA-256 in your browser. Nothing is uploaded.
Hashes are one-way and shown for reference only. MD5 and SHA-1 are not collision-resistant and should not be used for security.
Compute MD5, SHA-1, SHA-256 and SHA-512 digests in the browser, which is the right tool for checksums and the wrong tool for storing passwords.
Which algorithm to pick
SHA-256 is the safe default for integrity checks, content addressing and signatures. SHA-512 is equally fine and marginally faster on 64-bit hardware. SHA-1 and MD5 are cryptographically broken: practical collisions exist for both, meaning two different inputs can produce the same digest.
Broken does not mean useless. MD5 and SHA-1 remain common for non-adversarial checksums — verifying a download arrived intact, deduplicating files, matching against a legacy system that only speaks MD5. The distinction is whether an attacker benefits from forging a collision.
Never hash passwords with these
A general-purpose hash like SHA-256 is designed to be fast, which is exactly wrong for passwords. Modern GPUs compute billions of SHA-256 hashes per second, so a stolen table of unsalted SHA-256 digests falls quickly to a dictionary attack.
Password storage needs a deliberately slow, memory-hard function with a per-user salt: Argon2id, scrypt, or bcrypt at a suitable cost factor. If you are auditing a system that stores raw SHA-256 of passwords, that is a finding worth reporting.
Hashing is not encryption
A hash is one-way by design: there is no key and no decrypt. Encryption is reversible with the right key. Confusing the two leads to schemes where someone stores a hash and later discovers they cannot recover the original value.
The other trap is using a bare hash as a signature. Without a secret key or a salt, anyone can compute the same digest, so a hash proves integrity against accidental corruption, not against a deliberate substitution.
Frequently asked questions
- Can I hash a file instead of text?
- This tool takes text input. For files, use your operating system: certutil -hashfile on Windows, shasum -a 256 on macOS and Linux.
- Why do two tools give different MD5 for the same text?
- Usually a trailing newline or a character encoding difference. A hash covers exact bytes, so one extra line break changes the digest completely.
- Does hashing happen locally?
- Yes, through the browser's Web Crypto API for the SHA family. Nothing is transmitted.