Hash generator
Generate MD5, SHA-1, or SHA-256 hashes
Enter any text — the same input will always produce the same hash.
0 characters
This tool runs entirely in your browser. Your text is never uploaded or sent to a server.
0 characters
About this tool
A cryptographic hash function takes an input of any length and produces a fixed-length output (the hash or digest) that uniquely represents the input. The same input always produces the same hash, but it's computationally infeasible to reverse the process or find two different inputs that produce the same hash. MD5 and SHA-1 are faster but no longer considered cryptographically secure for sensitive use. SHA-256, part of the SHA-2 family, remains the standard for security-sensitive applications.
Common uses
- › Generating checksums to verify file integrity
- › Hashing passwords before storage (use SHA-256 with a salt, or better, bcrypt)
- › Creating cache keys from dynamic content
- › Verifying that data hasn't been tampered with in transit
- › Generating deterministic identifiers from arbitrary strings
Example
Hello, world!SHA-256 (hex):
315f5bdb76d078c43b8ac0064e4a0164612b1fce77c869345bfc94c75894eddTechnical notes
- › Hashing is one-way — you cannot recover the original text from a hash, unlike encoding (Base64) or encryption, both of which are reversible.
- › MD5 and SHA-1 are considered cryptographically broken for security purposes (collisions have been demonstrated) and should not be used for passwords, signatures, or anything security-sensitive — use SHA-256 or stronger.
- › For password storage specifically, a plain hash (even SHA-256) is not sufficient on its own; use a dedicated password-hashing algorithm like bcrypt, scrypt, or Argon2, which are designed to resist brute-force attacks.
- › The same input in the same encoding always produces the same hash — this tool hashes the text exactly as typed, including case and whitespace.
FAQ
Is hashing the same as encryption?
No. Encryption is reversible with the right key; hashing is one-way and cannot be reversed. Hashes are used to verify data hasn't changed, not to hide it for later retrieval.
Why shouldn't I use MD5 or SHA-1 for security?
Both algorithms have known collision vulnerabilities, meaning attackers can craft different inputs that produce the same hash. They're still fine for non-security uses like checksums, but not for passwords or digital signatures.
Can I use this to hash passwords for my app?
Not directly — a general-purpose hash like SHA-256 is too fast, making it vulnerable to brute-force attacks. Use a slow, purpose-built algorithm like bcrypt or Argon2 for password storage instead.