UUID v7 Generator
Generate time-ordered UUID v7 identifiers that index cleanly.
Verify a download by computing its SHA-256 without uploading it anywhere.
Drop a file here, or click to choose one — it is read locally and never uploaded
The File Checksum Calculator reads a dropped file locally and computes SHA-256, SHA-1, SHA-384, SHA-512, MD5 and CRC32 at once, then compares them against whatever checksum the publisher listed.
A published checksum only helps if you actually check it, and checking usually means finding the right command for your operating system. Drop the file here instead and every common digest is computed at once: SHA-256, SHA-1, SHA-384, SHA-512, MD5 and CRC32.
The file never leaves your machine. It is read with the browser's File API and hashed locally, which matters because the files worth verifying are installers, disk images and archives you would not want to upload anywhere. Paste the checksum the publisher gave you and the tool compares it against all six, tells you which one matched, and says plainly if none did.
It is read with the browser File API and hashed in the tab, which is the only reason checking an installer this way makes sense.
You do not have to know which one the publisher used — all six are computed and the matching one is identified.
Drop in the expected checksum and the tool names which algorithm matched, or says clearly that none did.
A big image reports as it reads, rather than appearing to have frozen.
A match means the file is what that page published — not that the page is trustworthy, which is a different question.
Drag it onto the page or click to choose it. It is read locally.
All six are computed at once; a large file takes a few seconds.
Whatever the publisher listed, in any of the supported algorithms.
The tool names which algorithm matched, or says clearly that none did.
No. It is read with the browser File API and hashed in the tab. Nothing is sent to any server, which is the only reason it is sensible to check an installer this way.
Files of a few hundred megabytes work on a normal machine. Very large images may exhaust memory, since the file is read before hashing.
SHA-256 whenever the publisher offers it. MD5 and SHA-1 still appear widely but can be deliberately collided, so a match proves the file is not corrupt rather than proving it is authentic.
It means the file is exactly what that page published. If an attacker controls the page, they control the checksum too. A signature checked against a known public key is the stronger guarantee.
What people who use the File Checksum Calculator think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the File Checksum Calculator. It takes half a minute and no account.
Write the first reviewGenerate time-ordered UUID v7 identifiers that index cleanly.
Test a regular expression live, with every match and capture group shown.
Build a Content-Security-Policy header directive by directive.
Find what runs on a port, with a note on whether it should be exposed.
Generate and decode MongoDB ObjectIds, including their embedded timestamp.
Strip every optional byte from a JSON document and see what you saved.
Convert file permissions between octal, symbolic and checkboxes.
Convert between px, rem, em, pt, %, vw and vh with the right context.