About this tool
MD5 produces a 128-bit fingerprint, written as 32 hex characters such as 5d41402abc4b2a76b9719d911017c592. It’s broken as a security function, but still everywhere: download checksums, cache keys and ETags, database deduplication, and older APIs and file formats that require it. This tool hashes text as you type or files of any size, streaming them in chunks so even multi-gigabyte files work.
Everything is computed in your browser with WebAssembly or the Web Crypto API. Your passwords and files are never uploaded.
Don’t use MD5 for security
- Collisions are easy: two different files with the same MD5 can be created in seconds, so an MD5 checksum can’t prove a file wasn’t tampered with by an attacker.
- Never for passwords: GPUs compute tens of billions of MD5 hashes per second. Use Argon2 or bcrypt.
- For integrity against attackers, use SHA-256 or SHA-3. MD5 is fine for catching accidental corruption.
Verifying a download
- Click Hash a file (or drop the file on the text box). The file is read locally.
- Paste the checksum from the download page into Compare. Hex in any case and Base64 both work.
- A green match means the file arrived intact.
MD5 on the command line
# Linux
md5sum file.iso
# macOS
md5 file.iso
# Windows (PowerShell)
Get-FileHash file.iso -Algorithm MD5
FAQ
How do I generate an MD5 hash?
Type or paste text above, or click Hash a file. The MD5 hash appears instantly as 32 hexadecimal characters.
Is MD5 secure?
No. Practical collision attacks have existed since 2004. Use it only for non-security checks such as detecting accidental corruption or legacy compatibility.
Can MD5 be decrypted?
No: a hash can’t be reversed. But short or common inputs can be found in precomputed tables, which is why MD5 must never be used for passwords.
Why does my MD5 differ from another tool’s?
Usually because of invisible differences in the input: a trailing newline, Windows (CRLF) line endings, or a different text encoding. This tool hashes text as UTF-8.