Hash Generator

Cryptographic hash functions produce a fixed-size fingerprint (digest) from any input. They are used for verifying file integrity, storing passwords securely, and digital signatures. This tool generates MD5 (legacy — not recommended for security), SHA-1, SHA-256, and SHA-512 hashes. SHA-256 and SHA-512 are computed using the browser's native Web Crypto API; hashing happens entirely in your browser.

Start typing to see hashes…

What this tool does

The Hash Generator computes MD5, SHA-1, SHA-256, and SHA-512 digests from any text input simultaneously. Hashing happens entirely in your browser — SHA algorithms use the native Web Crypto API, and MD5 uses a pure JavaScript implementation. You can also hash a local file directly using the SHA-256 file input. Nothing is transmitted to any server.

How to use it

  • Type or paste text — all four hashes update live as you type.
  • Click Copy next to any individual hash, or use Copy All to get all four.
  • To verify a downloaded file: use the file input, select the file, click Hash File, and compare the SHA-256 result against the checksum listed on the download page.

Which algorithm to use

  • SHA-256 — The right choice for most use cases: file integrity, code signing, API signatures. 64 hex characters.
  • SHA-512 — Same security level, longer output (128 hex characters). Slightly faster for large inputs on 64-bit hardware.
  • MD5 — Fine for non-security checksums (verifying accidental corruption). Do not use where collision attacks are a concern.
  • SHA-1 — Deprecated. Still seen in legacy systems and some Git contexts. Avoid for new applications.

Frequently Asked Questions

Can I use this to verify a downloaded file?

Yes — use the "Hash a File" section. Select the file, click Hash File, and compare the SHA-256 result against the checksum on the download page. If they match, the file arrived intact. Any difference — even one changed bit — produces a completely different hash, making tampering or corruption immediately detectable.

Is MD5 safe for password storage?

No. MD5 is a fast hash — attackers can test billions of candidates per second against MD5-hashed passwords. Password storage requires a deliberately slow hash: Argon2 (recommended), bcrypt, or scrypt. Never use MD5, SHA-1, or bare SHA-256 for passwords.

Why do two similar inputs produce completely different hashes?

This is the avalanche effect — a core property of cryptographic hash functions. Changing even a single bit in the input flips roughly half the output bits. This is what makes hashes useful for integrity checking: any modification, no matter how small, produces a distinctly different digest.

Want the full explanation? Read the guide: MD5 vs SHA-256: Which Hash to Use and When It Matters →