Hash Generator
Compute MD5, SHA-1, SHA-256, SHA-384 and SHA-512 hashes of any text instantly. Useful for checksums, integrity checks and fingerprinting — all in your browser.
About this tool
A hash function turns any input into a fixed-length string of characters — its digest. The same input always produces the same digest, but you cannot reverse a digest back into the original. This hash generator computes the most common algorithms: MD5, SHA-1, SHA-256, SHA-384 and SHA-512, using the browser's native Web Crypto API (with a bundled implementation for legacy MD5).
What hashes are used for
- File and data integrity — compare a downloaded file's checksum against the published one to confirm it wasn't corrupted or tampered with.
- Deduplication and fingerprinting — identify identical content by its digest.
- Verification — confirm two values match without storing the original.
Don't use MD5 or SHA-1 for security
MD5 and SHA-1 are cryptographically broken — collisions can be manufactured. They are fine for non-security checksums, but use SHA-256 or stronger for anything involving trust, and never hash passwords with a plain hash (use bcrypt, scrypt or Argon2).
Choosing an algorithm
For integrity and general use, SHA-256 is the modern default — fast, widely supported and secure. SHA-384 and SHA-512 offer longer digests. MD5 and SHA-1 remain useful only for matching legacy checksums.
Frequently asked questions
Hashes verify integrity (confirming a file or message hasn't changed), fingerprint and deduplicate data, and underpin digital signatures. A hash is a one-way fixed-length fingerprint of the input.
No. Hash functions are one-way by design. Attackers can only guess inputs and compare digests, which is why weak or unsalted hashes of predictable data (like short passwords) can still be cracked by brute force.
Not for security. MD5 is broken — attackers can craft two different inputs with the same digest. It is acceptable for non-security checksums and legacy compatibility, but use SHA-256 or stronger when trust matters.
No. Passwords should be protected with slow, salted algorithms designed for the job — bcrypt, scrypt or Argon2 — not fast general-purpose hashes like SHA-256 or MD5.