Hash Generator (MD5, SHA-1, SHA-256, SHA-512)
Hash text or a file with every common algorithm at once. Paste an expected checksum and the tool tells you whether it matches. Files are read locally - nothing is uploaded, whatever the size.
Every algorithm in one pass
The same input is hashed with MD5, SHA-1, SHA-256, SHA-384 and SHA-512 simultaneously, so you never have to guess which one a checksum file used. SHA family digests come from the browser's WebCrypto implementation; MD5 is computed by a small local implementation because WebCrypto deliberately omits it.
Verifying a downloaded file
Pick the downloaded file, paste the checksum the publisher provided, and read the verdict. Comparison ignores case and any spaces, so you can paste a line copied straight out of a `SHA256SUMS` file. A mismatch means the file differs from the one that was published - re-download before running it.
Which algorithm should you use?
For integrity checks against accidental corruption, any of them works. For anything security-relevant, use SHA-256 or stronger: MD5 and SHA-1 are both broken against deliberate collision attacks and should never be used for signatures or certificates. And no hash is a password storage scheme - that needs bcrypt, scrypt or Argon2 with a salt.
Frequently asked questions
Is my file uploaded to compute the hash?
No. Nothing you paste leaves your browser. The page loads a small amount of JavaScript, and every calculation happens on your own machine - there is no server to send data to. The file is read with the browser's file API and hashed in memory, which is what makes it safe to verify a private archive or an internal build artefact.
Why is MD5 still offered if it is broken?
Plenty of existing systems still publish MD5 checksums, and reproducing one is often the only way to confirm you have the same file an old tool produced. It remains fine for detecting accidental corruption; it is not fine for anything an attacker could influence.
Can I recover the original text from a hash?
No. Hashing is one-way by design. What attackers do instead is guess: hash enormous lists of candidate inputs and look for a match. That is why short or common inputs are effectively reversible, and why passwords need a salt and a slow algorithm.
Do line endings affect the result?
Yes, completely. A file with CRLF line endings hashes differently from the same file with LF endings, because the bytes differ. If a checksum does not match and the content looks identical, line endings or a trailing newline are the usual explanation.