Get MD5, SHA-1, SHA-256 and SHA-512 hashes of any text as you type.
Text is converted to UTF-8 bytes before hashing, which is what Python, Node.js, PHP and the command line normally do, and the result is shown as lowercase hex. If your hash doesn't match another tool, the input almost always differs: a trailing space, a final newline (echo adds one unless you use echo -n), or Windows line endings, where each line break is two characters.
SHA-1, SHA-256 and SHA-512 use the browser's built-in Web Crypto. MD5 isn't part of Web Crypto, so it runs from a small built-in implementation that gives the standard result. This tool hashes text; to check a downloaded file, use your system's sha256sum or certutil command.
SHA-256 is the sensible default for checksums and signatures. MD5 and SHA-1 are fine for spotting accidental changes but are broken for security, because collisions can be made on purpose. None of these should be used to store passwords: they are fast, which helps attackers guess. For passwords use a slow hash such as bcrypt, which the Bcrypt Hash Generator creates.
No. A hash is one-way. Short or common inputs can still be guessed by trying many candidates, which is why passwords need a slow hash with a salt.
The input bytes differ, usually because of a trailing newline, spaces or line-ending style. The same bytes always give the same hash.
Not for security. It's fine as a quick checksum against accidental corruption, but use SHA-256 when tampering matters.
No. All four hashes are calculated in your browser.
OneClickly is a set of 119 free tools for PDFs, images, text, everyday math and code. They run in your browser, so the files and text you work with stay on your device.