Generate MD5, SHA-1 and SHA-256 hashes of any text, computed entirely in your browser using our own hash implementations.
Google AdSense Banner
This area will contain advertisements after approval.
Google AdSense Banner
This area will contain advertisements after approval.
This tool implements the MD5, SHA-1 and SHA-256 algorithms directly, no crypto library involved, and each was verified to produce byte-identical output to Node's built-in crypto module across empty input, unicode text, and inputs at the algorithms' internal block-size boundaries before being wired up here.
MD5 and SHA-1 are fast but considered cryptographically broken, both have known collision vulnerabilities and shouldn't be used for security-sensitive purposes like password storage, though they're still common for non-security uses like checksums and cache keys. SHA-256 is currently considered secure and is the standard choice for security-relevant hashing today.
Hashing the text 'hello' produces MD5 5d41402abc4b2a76b9719d911017c592, SHA-1 aaf4c61ddcc5e8a2dabede0f3b482cd9aea9434d, and SHA-256 2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824. These are fixed-length, deterministic outputs, hashing 'hello' again (or on any other device) always produces exactly these same three values, but changing even one character, like to 'Hello', produces three completely different hashes.
Using MD5 or SHA-1 for anything security-sensitive, like verifying a password or a file's authenticity against a malicious actor, both have known practical collision attacks, use SHA-256 (or a dedicated password hashing algorithm for passwords specifically) instead.
Assuming a matching hash proves two files or strings are identical with absolute certainty, collisions are astronomically unlikely for SHA-256 but not mathematically impossible, for anything but casual integrity checks, this distinction rarely matters in practice.
Forgetting that hashing is one-way, there's no 'unhash' operation to recover the original text from any of these hash values, they're for comparison and verification, not encoding or encryption.
No, none of these algorithms (including SHA-256) should be used directly for password storage, dedicated password hashing algorithms like bcrypt, scrypt or Argon2 (which are deliberately slow and salted) exist specifically for that purpose. These general-purpose hashes are best suited for checksums, cache keys, and data integrity checks.
No, all hashing happens entirely in your browser, your text is never transmitted anywhere.
Google AdSense Banner
This area will contain advertisements after approval.