File Checksum
Hash a file to confirm your download is complete and unmodified.
Drop a file here
The file is read in your browser only — nothing is uploaded.
MD5 and SHA-1 are no longer safe for security purposes, but they are still what most download pages publish — and they remain fine for checking a file arrived intact.
About this tool
File checksum computes a file's MD5, SHA-1, SHA-256, SHA-384 and SHA-512 hashes so you can confirm your download matches what the publisher announced.
The question people actually arrive with isn't "what is a hash" — it's "did my download come through correctly?" So the tool has a box for the checksum from the download page and answers directly: match or no match.
The part built with extra care is reading what gets pasted in. People copy the whole line — sha256sum output with the filename after it, or a page that writes SHA256: abc…. A literal string comparison reports a mismatch on a perfectly good file. This one strips labels, filenames, spacing and capitalisation before comparing.
Files are read entirely in your browser and never uploaded. Because browsers offer no streaming digest API, the whole file has to be held in memory at once — so very large files get a warning before you start.
How to use
- 1Drop a file in, or choose one from your device
- 2Wait a moment — MD5, SHA-1, SHA-256, SHA-384 and SHA-512 are all computed
- 3Paste the checksum published on the download page into the compare box
- 4Read the verdict; if it does not match, download the file again
Frequently asked questions
- Is my file uploaded to a server?
- No. The file is read and hashed entirely in your browser, so it is safe to check files containing personal or company data.
- Can I paste a checksum with the filename after it?
- Yes. Trailing filenames from sha256sum output, a "SHA256:" prefix, and all-caps values are all handled — the extra text is stripped before comparing.
- Why is MD5 still here if it is broken?
- Because MD5 is still what a great many download pages publish. A checksum tool without it cannot answer the question people arrive with. Do not use MD5 for security — only for checking a file arrived intact.
- Does a matching checksum mean the file is safe?
- It means the file matches what the publisher announced, which proves it downloaded completely and was not altered in transit. It does not vouch for the file itself — you still have to trust the source.
- Can I hash very large files?
- Yes, but the digest needs the whole file in memory at once, since browsers offer no streaming digest API. Files over 256 MB get a warning up front and may struggle on a phone.