MD5 Checksum Calculator
Calculate MD5 checksum verification time for files based on size and hashing throughput.
About MD5 Checksum Calculator
MD5 produces a fixed 128-bit digest, always rendered as 32 hexadecimal characters by `md5sum`, regardless of input length. While the output format is simple and fast to compute, MD5 has been cryptographically broken since 2004 — collision attacks that find two different inputs producing an identical digest are practical and fast on ordinary hardware, which makes MD5 unsafe for anything where an adversary could choose or influence the input (passwords, signatures, certificate fingerprints, license keys). It remains fine only for non-adversarial integrity checks such as detecting accidental file corruption.
Formula
Output format
MD5 output = 128 bits = 32 hexadecimal characters, fixed regardless of input size
Worked example
With the default values below, MD5 Checksum Calculator returns Illustrative Hex Digest (not cryptographic) of 28a9cd136ffb308245af7df3ccf06665. Change any input above and every figure here is recalculated in your browser.
Inputs used
- Input Text
- hello world
- Intended Use Caseone of Non-security file integrity / dedup check, Security-sensitive (auth, signatures, certificates)
- Non-security file integrity / dedup check
Results
- Illustrative Hex Digest (not cryptographic)
- 28a9cd136ffb308245af7df3ccf06665
- Collision Risk Warning
- MD5 remains acceptable for non-adversarial use cases like detecting accidental corruption, deduplication, or checksums where no attacker controls the input, but it should never be relied on where an attacker could deliberately craft a colliding input.
- Output Size (bits)
- 128
- Hex String Length (characters)
- 32
Step by step
- 1Values used
- 2Output format
- 3Illustrative Hex Digest (not cryptographic)= 28a9cd136ffb308245af7df3ccf06665
- 4Collision Risk Warning= MD5 remains acceptable for non-adversarial use cases like detecting accidental corruption, deduplication, or checksums where no attacker controls the input, but it should never be relied on where an attacker could deliberately craft a colliding input.
- 5Output Size (bits)= 128
- 6Hex String Length (characters)= 32
Assumptions and limits
- The result is derived only from the 2 inputs listed above. Anything not among them is not part of the calculation.
- In particular, this calculator does not take inflation, tax, fees or charges or compounding frequency into account.
- Figures are rounded for display to whole numbers, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.
How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.
Frequently Asked Questions
Why is MD5 considered broken but still exists on Linux systems?
MD5 is broken specifically as a *cryptographic* hash — collisions are practical to engineer. It remains present because it's still useful for cheap, non-adversarial tasks (checksumming large file sets for accidental corruption, legacy protocol compatibility) and removing it would break backward compatibility, not because it's still considered secure.
Can MD5 collisions be exploited in real attacks?
Yes — demonstrated real-world exploits include forging rogue CA certificates (2008) and crafting two different files/documents with matching MD5 sums for social-engineering or malware-signing evasion. This is why MD5 is disallowed in TLS certificate signing and most modern security standards.
What should I use instead of MD5 for password hashing?
Never use any general-purpose hash function (MD5, SHA-256, SHA-512) alone for passwords — use a dedicated slow, salted password-hashing algorithm like bcrypt, scrypt, or Argon2, which are specifically designed to resist brute-force and GPU/ASIC cracking.