How to Generate & Verify File Checksums — MD5, SHA-256, SHA-1 Free

What Are Checksums and Why They Matter

A checksum is a digital fingerprint of a file or text. Feed in the same input, you always get the same hash. Change even one character, and the hash is completely different. This makes checksums perfect for verifying that a downloaded file is not corrupted or tampered with. Software distributors publish checksums alongside downloads — if your downloaded file's hash matches, the file is authentic and complete.

How to Generate a Hash

1. Open the Hash Generator
2. Enter text or upload a file
3. Choose the algorithm: MD5, SHA-1, SHA-256, or SHA-512
4. Copy the generated hash

For verifying downloads, generate the hash of your downloaded file and compare it to the hash published on the software's website. If they match, the file is clean.

Which Algorithm to Use

• MD5 — fastest, most common for quick file verification. 128-bit hash. Not collision-resistant (don't use for security), but fine for download verification.
• SHA-1 — 160-bit hash. Used in Git commit hashes. Deprecated for security but still common in legacy systems.
• SHA-256 — 256-bit hash. Industry standard for security. Used by blockchain, SSL certificates, and software signing. Use this when security matters.
• SHA-512 — 512-bit hash. Maximum security. Overkill for most uses but available when required.

Common Use Cases

• Verify software downloads — compare hash to publisher's checksum to detect corruption or tampering
• Detect file changes — hash a file, store the hash, re-hash later to see if it changed
• Deduplicate files — files with identical hashes are identical content (even with different names)
• API authentication — HMAC hashes verify API request integrity
• Password storage — passwords should be hashed (SHA-256+salt), never stored in plain text