Hash Generator and Checksum Tool

Guide & FAQ

MD5 and SHA-1 are broken for security use (collisions can be forged). Use them only to check a download against a published checksum. For anything new use SHA-256 or SHA-512. Hashing is done in your browser tab.

Guide: Hash Generator and Checksum Tool

Hash text

Type or paste text and all five hashes appear instantly: MD5, SHA-1, SHA-256, SHA-384 and SHA-512. Text is converted to UTF-8 before hashing. Use the Copy button on a row or switch to uppercase hex if your source shows it that way.

Hash a file

Open the File tab and choose any file. It is read in your browser and the hashes are calculated on your device. This is the quickest way to confirm that an ISO, installer or archive downloaded correctly.

Compare with a known hash

Paste the expected checksum into the compare box. Case and spaces are ignored. A match highlights the algorithm that produced it, and a mismatch shows the expected lengths so you can spot a wrong algorithm choice.

Choosing an algorithm

  • SHA-256 / SHA-512: current standard for integrity and signatures.
  • SHA-1 / MD5: legacy; collisions are practical, so do not rely on them for security.

Privacy

SHA algorithms use your browser's built-in Web Crypto API. MD5, which the browser does not provide, is implemented in this page. No data is sent anywhere.

FAQ

How do I verify a downloaded file?

Open the File tab, choose the downloaded file and paste the checksum published by the website into the compare box. If the matching row turns green the file is identical to the original.

Which hash should I use?

Use SHA-256 or SHA-512 for anything new. MD5 and SHA-1 are broken for security purposes because attackers can create collisions, but they are still fine for catching accidental corruption and for matching old published checksums.

Can a hash be reversed to get the original text?

No, a hash is one-way. Weak inputs such as short or common passwords can still be found by guessing, which is why passwords must be stored with a slow, salted algorithm like bcrypt or Argon2, not a plain hash.

Is my file uploaded?

No. The file is read by your browser and hashed on your device; the tool does not upload it.

Why does my text hash differ from another tool?

Hashes are computed on bytes. This tool encodes text as UTF-8. Differences usually come from a trailing newline, different line endings or a different text encoding.

Open-source licences

  • MD5 (RFC 1321), implemented from the specification for this tool: Original work, no third-party licence