Hash Functions: MD5, SHA-256 & More Explained

What Is a Hash Function?

A hash function takes an input of any size — a single character, a paragraph, or an entire file — and produces a fixed-length output called a hash, digest, or checksum. The same input always produces the same hash. Even a tiny change to the input produces a completely different hash. And given a hash, there is no practical way to reverse-engineer the original input.

These three properties — determinism, avalanche effect, and irreversibility — make hash functions essential to modern computing. They are used for password storage, file integrity verification, digital signatures, data deduplication, and blockchain technology.

A simple analogy: a hash function is like a fingerprint for data. Two identical documents have identical fingerprints. Change a single comma and the fingerprint is completely different. And you cannot reconstruct the document from its fingerprint alone.

Common Hash Algorithms

MD5 (Message Digest 5): Produces a 128-bit (32 hex character) hash. Released in 1991, MD5 was widely used for file checksums and password hashing. However, MD5 is now considered cryptographically broken — researchers have demonstrated practical collision attacks (creating two different inputs with the same hash). MD5 should not be used for security purposes but remains useful for non-security checksums (verifying file downloads, detecting duplicate files).

SHA-1 (Secure Hash Algorithm 1): Produces a 160-bit (40 hex character) hash. SHA-1 was the standard for digital signatures and certificates for over a decade. In 2017, Google demonstrated a practical SHA-1 collision, and browsers stopped trusting SHA-1 certificates. Like MD5, SHA-1 is no longer recommended for security applications.

SHA-256: Part of the SHA-2 family, producing a 256-bit (64 hex character) hash. SHA-256 is the current standard for most security applications. It is used in TLS/SSL certificates, Bitcoin mining, code signing, and password hashing schemes. No practical attacks against SHA-256 exist as of 2024.

SHA-512: Also part of SHA-2, producing a 512-bit (128 hex character) hash. SHA-512 is faster than SHA-256 on 64-bit processors and offers a larger hash space. It is used when extra security margin is desired or when the target platform is 64-bit optimized.

SHA-3 (Keccak): The newest SHA standard, released in 2015. SHA-3 uses a fundamentally different internal structure (sponge construction) from SHA-2. It was designed as an insurance policy — if a weakness is found in SHA-2, SHA-3 provides an unrelated alternative. SHA-3 adoption is growing but SHA-256 remains dominant.

BLAKE2/BLAKE3: Modern hash functions designed for speed. BLAKE3 is significantly faster than SHA-256 while maintaining strong security properties. It is gaining adoption in file integrity systems and content-addressable storage.

Hash Properties Explained

A good cryptographic hash function must satisfy several properties:

• Pre-image resistance: Given a hash value, it should be computationally infeasible to find any input that produces that hash. This is what makes hash functions irreversible.
• Second pre-image resistance: Given an input and its hash, it should be infeasible to find a different input that produces the same hash. This prevents forgery — you cannot create a malicious file with the same checksum as a legitimate one.
• Collision resistance: It should be infeasible to find any two different inputs that produce the same hash. This is a stronger requirement than second pre-image resistance. MD5 and SHA-1 have failed this property.
• Avalanche effect: Changing a single bit of the input should change approximately half the bits in the output. This ensures similar inputs do not produce similar hashes — there is no way to tell from two hashes whether the inputs were related.

Practical Applications

Password storage: Websites never store passwords in plain text (or should not). Instead, they hash the password and store the hash. When you log in, the entered password is hashed and compared to the stored hash. If they match, the password is correct. If the database is breached, attackers get hashes, not passwords. Proper password hashing uses specialized functions like bcrypt, scrypt, or Argon2 — not raw SHA-256 — because these add computational cost that makes brute-force attacks impractical.

File integrity: Software distributors publish SHA-256 checksums alongside their downloads. After downloading, you hash the file locally and compare. If the hashes match, the file was not corrupted or tampered with during download.

Digital signatures: When you digitally sign a document, the signing process hashes the document and encrypts the hash with your private key. The recipient decrypts with your public key and compares hashes to verify the document has not been altered and was signed by you.

Git version control: Git identifies every commit, file, and directory by its SHA-1 hash (with plans to migrate to SHA-256). This content-addressable storage means two identical files always have the same hash, enabling efficient deduplication and integrity checking across the entire repository history.

Blockchain: Bitcoin and other cryptocurrencies use SHA-256 to chain blocks together. Each block contains the hash of the previous block, creating a tamper-evident chain — altering any historical block changes its hash, which breaks the chain from that point forward.

Choosing the Right Algorithm

For security-critical applications (certificates, signatures, password hashing): use SHA-256 or SHA-3. If speed matters more than maximum security (checksums, deduplication, caching): consider BLAKE3 or SHA-256. For legacy compatibility where security is not the primary concern: MD5 checksums are still widely used for file verification. Never use MD5 or SHA-1 for new security applications.

Generate Hashes Online

Our Hash Generator computes MD5, SHA-1, SHA-256, SHA-512, and other hash values for any text input. Enter your text, select the algorithm, and get the hash instantly. The tool also supports file hashing — upload a file to compute its checksum for integrity verification.

All computation runs in your browser using the Web Crypto API. Your data is never sent to a server, making it safe for hashing sensitive information like passwords and confidential documents.