Checksum Calculator
Check that a downloaded file is the one published.
FREE - NO SIGN-UP - RUNS ON YOUR DEVICE
The file is read on this device
- 4algorithms
- 1file at a time
- 0uploads
- Freeno sign-up
Checksum Calculator at a glance
- Input
- One file and an algorithm
- Output
- A hex digest to compare
- Algorithms
- MD5, SHA-1, SHA-256, SHA-512
- Method
- crypto.subtle, plus local MD5
- What a match proves
- The bytes match, nothing more
- Price
- Free
- Account needed
- None
- Where processing happens
- On your device
How to use Checksum Calculator
- 1
Choose the file
Pick the file you downloaded.
- 2
Match the algorithm
Use the algorithm the publisher named.
- 3
Compare end to end
Read every character, not the first few.
Frequently asked questions
What does a matching checksum actually prove?
That the file holds the same bytes that produced the published digest. It says nothing about who wrote the file, so the checksum needs to come from a source you already trust.
The digests differ. What now?
Download the file again. A single wrong character means the bytes differ, which is usually an interrupted download, and occasionally a file that is not the one you meant to get.
Which algorithm should I choose?
The one printed beside the download. MD5, SHA-1, SHA-256 and SHA-512 all produce different digests for the same file, so they cannot be compared across.
Is the file uploaded to be checked?
No. It is read inside this browser tab and the digest is worked out there. Nothing leaves the device and nothing is stored.
Before you trust a match
Choose the file, pick the algorithm the publisher used, and read the digest. You compare it by eye against the published string; nothing about the file is sent away.
- Take the published checksum from a different place than the download itself where you can, such as signed release notes.
- A checksum finds a damaged download quickly, which is the job it does best.
- MD5 and SHA-1 still appear beside downloads; they catch damage, and cannot rule out a file built to collide on purpose.
- Text and files hash differently, so paste text only when the checksum was made from text.
Full specification
| Input | One file chosen from this device, or pasted text, and the algorithm the publisher used. |
|---|---|
| Output | The hexadecimal digest, ready to set beside the published string. |
| Algorithms | MD5, SHA-1, SHA-256 and SHA-512. Pick the one that matches the checksum you were given. |
| Method | crypto.subtle handles the SHA family; MD5 is local JavaScript kept for checksums. |
| What a match proves | That the bytes are the ones that were hashed. Not that the publisher is genuine, or that the checksum page is. |
| Price | Free. Supported by clearly labelled ads outside the working area. |
| Account needed | No. |
| Where processing happens | In your browser tab. Your input is never uploaded. |
Keep going with the same files
All developer tools: Developer tools on SPOTTOOLS