Calculate the MD5, SHA-1, SHA-256, SHA-384 or SHA-512 hash of any text. The hash updates as you type and is shown as a hexadecimal string in lowercase or uppercase. SHA hashes use the browser's Web Crypto API and MD5 uses a built-in implementation, so everything is computed on your device.
- Which algorithms are supported, and how long are the hashes?
- MD5 (32 hex characters), SHA-1 (40), SHA-256 (64), SHA-384 (96) and SHA-512 (128). SHA hashes are computed with crypto.subtle.digest; MD5 is not part of Web Crypto, so it is calculated by the page's own code.
- Why is my hash different from another tool's?
- The text is encoded as UTF-8 before hashing, and a single different byte changes the whole hash. Check for a trailing newline (for example from echo without -n), different line breaks (the input box uses LF, while a Windows file may use CRLF), extra spaces, or a different character encoding.
- Can I hash a file?
- Only text files. A file dropped onto the input box is read as text, so the result matches the file only if it is UTF-8 text. Images, ZIP archives and other binary files will not give their real checksum here.
- Can I use MD5 or SHA-1 for security?
- They are fine for checksums and for spotting accidental changes, but collisions have been demonstrated for both, so do not use them for signatures or anything security-related. Use SHA-256 or stronger.
- Can I hash passwords with this?
- Plain hashes are not suitable for storing passwords because they are fast to guess. Password storage should use a dedicated algorithm such as bcrypt, scrypt or Argon2 on the server.
- Can a hash be turned back into the text?
- No. Hash functions are one-way. Short or common inputs can still be found by guessing, which is another reason not to hash passwords this way.
- Is my input sent to a server?
- No. Hashing runs entirely in your browser. Note that short input is also kept in the page URL (so reloading keeps it), which means it stays in your browser history; avoid pasting secrets you do not want stored there.