69ea.com
EN English ZH 简体中文 JA 日本語

Home › Reference › Checksum Generator

Checksum Generator

Generate MD5, SHA-1, SHA-256, SHA-384 and SHA-512 hashes from text, and compare two checksums to verify data integrity. Runs entirely in your browser.

About the Checksum Generator

This tool computes cryptographic hashes (also called checksums or digests) from text using MD5, SHA-1, or the SHA-2 family. Hashes are one-way fingerprints: the same input always produces the same hash, but you can't reverse a hash back to its input. They're used to verify that data hasn't been corrupted or tampered with — if even one bit changes, the hash changes completely. All hashing happens locally in your browser.

Supported algorithms

  • MD5 — 128-bit hash. Fast and widely supported, but not secure against deliberate collisions. Fine for non-security checksums and file identification.
  • SHA-1 — 160-bit hash. Deprecated for security uses after practical collision attacks, but still common in legacy systems and Git.
  • SHA-256 / SHA-384 / SHA-512 — The SHA-2 family. Currently considered secure and recommended for any new cryptographic use.

How to use it

  1. Type or paste text into the input box.
  2. Select an algorithm from the dropdown.
  3. Click Generate to compute the hex checksum.
  4. To verify integrity, paste another hash into the Compare field and click Verify — it tells you if they match.

Frequently asked questions

Is my text uploaded anywhere? No. All hashing runs in JavaScript on your device, including the SHA algorithms via the Web Crypto API.

Which algorithm should I use? For verifying file integrity where no attacker is involved, MD5 is fine. For any security-sensitive purpose (passwords, signatures, tamper detection), use SHA-256 or stronger.

Can I hash a file instead of text? This version hashes text only. File hashing may be added later — for now, paste the file's contents into the box.

Why are MD5 and SHA-1 considered broken? Researchers found ways to create distinct inputs with the same hash (collisions). For pure checksums this doesn't matter, but it breaks digital signatures and tamper detection — use SHA-256+ for those.