What Is an MD5 Checksum? MD5 vs SHA-256 Explained
An MD5 checksum is a 128-bit fingerprint used to identify file contents. Learn how MD5 works, why it is no longer secure, how it compares with SHA-256, and calculate a checksum free.
Founder of ARCED Foundation, ARCED International, and Solutions of Things Lab (SoTLab). Built FolderManifest to help teams protect file integrity and stay audit-ready.
An MD5 checksum is a 128-bit fingerprint calculated from a file’s exact contents. It lets you compare a file with an expected MD5 value to detect accidental changes, but it cannot prove that a file is safe or authentic.
What Is an MD5 Checksum?
MD5 stands for Message Digest Algorithm 5. The algorithm turns any amount of data into a fixed 128-bit result, usually written as 32 hexadecimal characters. Identical files produce identical MD5 checksums; changing even one byte normally produces a different value.
A checksum is not encryption and cannot reveal the original file. It is a compact identifier used to compare file contents. For a practical verification workflow, see the file-integrity verification guide.
How Is an MD5 Checksum Generated?
- A checksum tool reads the file as bytes.
- MD5 processes those bytes in fixed-size blocks through its compression function.
- The final 128-bit digest is displayed as a 32-character hexadecimal checksum.
The same bytes always produce the same MD5 value, regardless of the filename or folder. Use the free checksum calculator to generate SHA-256, MD5, SHA-1, and CRC32 for one file.
What Is MD5 Still Useful For?
MD5 can still be practical when collision resistance is not a security requirement:
- Matching a file against a checksum published by a legacy system.
- Quick duplicate screening inside a trusted, non-adversarial collection.
- Detecting accidental transfer or storage errors when MD5 compatibility is required.
These uses identify accidental differences. They do not establish who created the file or whether someone crafted a collision deliberately.
Why Is MD5 Unsafe for Security-Sensitive Verification?
MD5 has practical collision attacks: two different inputs can be deliberately created with the same MD5 checksum. That makes an MD5 match insufficient for software releases, digital signatures, audit evidence, legal records, or any workflow where an attacker could modify the input.
Use SHA-256 for tamper-sensitive checks, and obtain the expected checksum from a trusted source. A digital signature provides stronger authenticity evidence than a bare checksum alone.
MD5 Versus SHA-256
| Factor | MD5 | SHA-256 |
|---|---|---|
| Output length | 128 bits | 256 bits |
| Collision security | Broken; practical attacks exist | No practical collision attack is known |
| Typical role | Legacy compatibility and trusted quick checks | Integrity and tamper-sensitive verification |
| Security-sensitive use | Do not use alone | Recommended checksum choice |
Hashing speed varies by hardware, file size, and implementation. In most file-verification workflows, storage speed also matters, so MD5’s possible speed advantage is not a reason to accept its collision weakness.
Need repeatable whole-folder verification?
FolderManifest saves local HTML reports so you can compare a folder again and document what changed.
Frequently Asked Questions
- What is an MD5 checksum?
- An MD5 checksum is a 128-bit fingerprint calculated from a file’s contents. It is normally displayed as 32 hexadecimal characters and changes when the file’s bytes change.
- Is an MD5 checksum secure?
- No. MD5 has practical collision attacks, so an attacker can create different inputs with the same MD5 value. Do not use MD5 alone for software releases, signatures, audit evidence, or other security-sensitive verification.
- What is MD5 still useful for?
- MD5 remains useful for matching legacy checksum lists and quick duplicate or transfer checks in trusted, non-adversarial workflows. Use SHA-256 when deliberate tampering is possible.
- Should I use MD5 or SHA-256?
- Use SHA-256 for downloads, backups, audit records, and tamper-sensitive verification. Use MD5 only when a legacy system requires it or when collision resistance is not part of the decision.