Hash Generator

Four digests at once — SHA-1, SHA-256, SHA-384, SHA-512 — over text you type or a file you pick, computed by WebCrypto inside your own tab. The file is read locally and never uploaded, which matters more here than on most tools: the thing you want a hash of is usually the thing you are least willing to send somewhere.

There is no MD5, deliberately

WebCrypto does not implement it, so offering MD5 would mean shipping a hand-written one. MD5 has been collision-broken since 2004, which removes the only property a generator is used for — establishing that two files are the same. Where you need to recognise an MD5 someone else produced, the Hash Identifier reads it instead.

Hex and Base64 are the same digest

Hex is what advisories, malware repositories and sha256sum print. Base64 is what a Subresource Integrity attribute wants, after the sha384- prefix. Both are shown because both get asked for, and converting between them by hand is a pointless source of error.

When a digest does not match the advisory

Usually the file genuinely differs: an archive re-compressed on the way down, a text file whose line endings were converted, a sample defanged before sharing. A hash covers bytes, not intent. Compare the byte count reported here against the one the advisory gives before concluding the hash is wrong.

abc gives SHA-256 ba7816bf…f20015ad. Hashing café covers five bytes rather than four characters, because é is two bytes in UTF-8 — the byte count is shown alongside for exactly that reason.