Skip to content

Hash generator

MD5 and SHA hashes of text or files, and checksum verification.

Updated

Hash

How to generate a hash

  1. Choose Text and type, or choose File and pick any file.
  2. MD5, SHA-1, SHA-256, SHA-384 and SHA-512 appear together.
  3. Copy the one you need, or paste an expected value into Compare with to verify it.

Hash algorithms compared

AlgorithmLengthSafe for security?Typical use
MD5128 bits (32 hex)NoLegacy checksums, cache keys
SHA-1160 bits (40 hex)NoGit object IDs, older systems
SHA-256256 bits (64 hex)YesDownload checksums, signatures, blockchains
SHA-384384 bits (96 hex)YesTLS certificates, subresource integrity
SHA-512512 bits (128 hex)YesHigh-security applications

What a hash tells you

A hash is a fixed-length fingerprint of data. Change a single byte and the hash changes completely, so matching hashes mean identical data. You can't turn a hash back into the original, which is why software publishers list checksums: you can confirm a download without them sending the file twice.

Common uses

  • Checking an installer before running it. Software sites often publish a SHA-256 checksum beside each download. Pick the file, paste their value into Compare with, and run it only if it matches.
  • Confirming two files are identical. Hash both copies of a backup, export or upload and compare the results. Identical hashes mean identical files, whatever their names or dates.
  • Matching a hash in an older system. An older database or API expects the MD5 or SHA-1 of a string, for example as a cache key. Type the text and copy the hash it needs.

Questions

How do I verify a downloaded file?

Choose File, pick the download, then paste the checksum the publisher lists (usually SHA-256) into “Compare with”. A match means the file is exactly the one they published, byte for byte.

Which hash should I use?

SHA-256 for anything new: it's the standard for checksums and signatures. MD5 and SHA-1 are broken for security, since collisions can be manufactured, but they're still fine for spotting accidental corruption and matching legacy systems.

Can I use these hashes to store passwords?

No. Fast hashes like these are the wrong tool for passwords because attackers can try billions of guesses a second. Use a slow, salted algorithm such as Argon2, scrypt or bcrypt.

Why does my hash differ from another tool's?

Usually a hidden difference in the input: a trailing newline, Windows line endings or different text encoding. Text here is hashed as UTF-8 exactly as typed. Hashing the file itself avoids the problem.