CV Builder

Hash Generator

Generate MD5, SHA-1, SHA-256 and SHA-512 hashes from text.

🔒 Everything happens in your browser — your text and files are never sent to a server. MD5 and SHA-1 are shown for checksum and compatibility use only; neither is safe for passwords or signatures.

What Does the Hash Generator Do?

The Hash Generator computes six widely used digests of any text or file: MD5, SHA-1, SHA-256, SHA-384, SHA-512 and CRC32. A hash is a fixed-length fingerprint — the same input always yields the same output, but even a one-character change produces a completely different hash, and the process cannot be reversed to recover the input.

Everything runs in your browser. Nothing you type and no file you choose is uploaded anywhere: the SHA family is computed with the browser's built-in Web Crypto engine, and MD5 and CRC32 in JavaScript alongside it. Results are identical to command-line tools like md5sum and sha256sum — which matters, because people paste passwords, API keys and private documents into hash tools, and none of that should ever leave your machine.

How to Generate Hashes

  1. Type or paste your text — all six digests update as you type.
  2. Or switch to Hash a file and drop in any file, of any size, to get its checksum.
  3. Copy any digest with its button.
  4. To check a download, paste the publisher's checksum into Verify against a known hash — it tells you which algorithm matched, or that none did.

What Each Algorithm Is For

  • MD5 (128-bit) — checksums, cache keys and deduplication. Broken for security, still ubiquitous for integrity checks.
  • SHA-1 (160-bit) — legacy signatures and Git object IDs. Deprecated for new security uses since practical collisions were demonstrated in 2017.
  • SHA-256 / SHA-512 — the current standard family for digital signatures, certificates, blockchain and file verification.
  • CRC32 — a fast error-detection checksum used inside ZIP and PNG files; not cryptographic at all.

Developers verify downloaded files against published checksums, generate deterministic cache keys, compare configs across servers, and produce test vectors for their own hashing code.

Frequently Asked Questions

Can a hash be decrypted back to the original text?

No — hashing is one-way by design. The only "reversal" is guessing: attackers precompute hashes of common inputs (rainbow tables), which is why short or common passwords are crackable despite hashing.

Is MD5 still safe to use?

For non-security purposes (checksums, cache keys, deduplication) MD5 remains fine and fast. For anything security-related — passwords, signatures, certificates — use SHA-256 or stronger; MD5 collisions can be created at will.

Why shouldn't passwords be stored as plain SHA-256?

Fast hashes can be brute-forced at billions of guesses per second on GPUs. Passwords need deliberately slow, salted algorithms like bcrypt or Argon2. This tool is for checksums and development, not password storage.

Do identical inputs always give identical hashes?

Yes — that determinism is the whole point. Note that an extra space or different line ending counts as a different input and completely changes the hash.