Skip to content

Hash a text string using MD5, SHA-1, SHA-2 (224/256/384/512), SHA3-256, SHA3-512, Keccak-256 or RIPEMD-160.

Loading tool

About Hash text

Compute MD5, SHA-1, SHA-224, SHA-256, SHA-384, SHA-512, SHA3-256, SHA3-512, Keccak-256 and RIPEMD-160 digests of a text string, one algorithm or all at once, in lowercase or uppercase hex. SHA3-256 and SHA3-512 follow the FIPS 202 standard, and Keccak-256 is the variant Ethereum uses. Hashing runs entirely in your browser, so the text is not sent to a server.

Common uses

  • Compare a string's checksum with a published MD5 or SHA-256 value.
  • Generate a hash to use as a cache key or deduplication ID.
  • Check what digest your code should produce when writing tests.
  • See the same input hashed with several algorithms side by side.

FAQ

Can a hash be reversed to get the original text?
Not directly; hash functions are one-way. Short or common inputs can still be found by guessing or with lookup tables, which is why unsalted hashes are unsuitable for storing passwords.
Are MD5 and SHA-1 still safe?
Not for security. Practical collision attacks exist for both, so they should not be used for signatures or integrity against an attacker. They are still used for non-adversarial checksums and legacy compatibility.
Should I use SHA-256 to store passwords?
No. General-purpose hashes are fast, which makes brute force cheap. Use a dedicated password hashing function such as bcrypt, scrypt or Argon2.
What is the difference between SHA3-256 and Keccak-256?
They use the same Keccak permutation but different padding: SHA3-256 is the final FIPS 202 standard, while Keccak-256 is the pre-standard version that Ethereum adopted for addresses, function selectors and keccak256() in Solidity. The same input gives different digests, so pick the one your system expects.