SHA256 OnlineVerify a legacy release
Select the artifact named by an older MD5SUMS list. Prefer a stronger publisher-supplied digest when one is available.
Legacy compatibility · Files
MD5 File Checksum
Calculate MD5 for one or many files. Verify a GNU or BSD checksum list without uploading files.
Input No upload
or drop files here · up to 100 · 2 GiB eachFiles stay on this device.
Output Your result · MD5
Ready to calculate
0 / 0 bytes processed
Browser-local hashing. Inputs masked in Clarity.
No account. No uploads. Just your browser.
MD5 versus SHA256
| Algorithm | What differs |
|---|---|
| MD5 | 128-bit legacy digest; broken collision resistance. |
| SHA256 | 256-bit SHA-2 digest; use for new integrity workflows with a trusted reference. |
Verify MD5 files in three steps
- 1
Select the actual files
Choose up to 100 files, each at most 2 GiB. The file contents are read locally.
- 2
Read the calculated checksum
MD5 returns 32 lowercase hex characters. Copy digest preserves the whole output.
- 3
Compare a trusted release list
Read a local manifest or paste a trusted expected value. Review each filename and any missing entries.
MD5 file workflows
Check a local copy
Compare the MD5 of the original and copied bytes to diagnose accidental changes, not malicious tampering.
Review a batch manifest
Load the .md5 list as reference text, not as the file whose digest you intend to check.
Details that affect your MD5 result
How MD5 works
MD5 produces a 128-bit result: 32 hexadecimal characters. Use it to compare legacy checksum lists, not to authenticate a download or store passwords. MD5 has known collisions, so a matching digest does not establish authenticity.
A typical .md5 list contains a digest, two spaces, and the exact filename. Select MD5 before reading that list. SHA256 and MD5 values cannot be compared to each other.
Verify MD5 files
Choose or drop files and calculation starts automatically. Each file is read sequentially in 2 MiB chunks inside a background worker. Up to 100 files and 2 GiB per file are accepted. Cancel terminates the active worker.
Paste a trusted expected digest to compare directly. With no expected value, Not compared yet is not a verification success. Every batch row includes the complete digest, byte count and comparison outcome.
Read a MD5 checksum manifest
Open manifest options to read a local list or paste GNU digest–filename lines or BSD ALGORITHM (filename) = digest lines. Verify selected files runs the comparison again with the list. The filename is matched exactly, including spaces and relative folders.
Duplicate names, invalid digest lengths, mixed algorithms and unsupported lines block manifest verification. Missing files and files not listed are displayed; no basename-only guessing or silent success is used. Lists are limited to 1 MiB and 100 entries.
Private file handling and practical limits
Hashing runs in browser memory with no upload endpoint. Microsoft Clarity runs on this page, with the entire tool workspace masked, including filenames, digests and manifests. Google Analytics runs only on the four information pages. A local report can be copied or downloaded. See Privacy for details.
The 2 GiB ceiling is not a promise about every phone. If a device struggles, cancel and use a system checksum utility. A matching value proves only equality with the reference digest, not safety or publisher identity.
Known MD5 result: empty input
MD5 · 0 bytes · no HMAC. Empty input is not the same as no file selected.
d41d8cd98f00b204e9800998ecf8427eMD5 file checksum FAQ
When should I choose an MD5 file checksum?
Choose it when your trusted source publishes MD5 for that exact artifact. Do not choose MD5 merely because its output is shorter.
Does an MD5 match make a download trustworthy?
No. MD5 has broken collision resistance, and a checksum supplied by an attacker can match an attacker’s file. Verify the source and use stronger published digests where available.
Why does a .md5 file not match when I hash it?
The .md5 document is a list of reference digests and filenames. Read it as a manifest, then select the referenced files; hashing the list itself checks different bytes.
Can I compare MD5 and SHA1 file values?
No. Their algorithms and lengths differ. Use the MD5 value from the release’s reference list, or switch tools to match the algorithm it names.
What happens after selecting files for MD5?
Files are hashed automatically and sequentially. The result says calculated until an expected digest is supplied; Match or Mismatch describes a comparison, not just a completed calculation.
How should I prepare a MD5 checksum manifest?
Use GNU digest followed by a filename, or a BSD algorithm (filename) = digest line. Each MD5 reference needs 32 hex characters. Malformed lines and duplicate names block verification.
Why is a file missing from my MD5 batch?
Names must match exactly, including spaces and relative paths. A selected file not in the manifest is reported separately and is not silently treated as a verified match.
Can I export my MD5 batch results?
Download report saves a local text report with filenames, byte counts, digests and comparison states. Keep that report private if its filenames or checksums are sensitive. No report is uploaded.