File Hash Calculator: SHA-256, SHA-512, SHA-1 and MD5
Compute the checksum of a file and compare it with the value a publisher lists next to a download. Choose SHA-256, SHA-512, SHA-1 or MD5; the result is a lowercase hex string.
Runs in your browser: your files and text are not uploaded. Free, no account needed.
Last updated: · Reviewed by the QuickTooly Team
Which algorithm to pick
- SHA-256 (default, 64 hex characters): what most download pages, Linux distributions and package managers publish. Use it unless the publisher lists something else.
- SHA-512 (128 hex characters): same family, longer output. Use it when the published checksum is SHA-512.
- SHA-1 (40 hex characters): practical collisions have been shown, so it is not fit for security. Use it only to match an old published checksum.
- MD5 (32 hex characters): broken. Two different files can be made with the same MD5, so a match proves nothing against tampering. It still catches accidental corruption.
A checksum only shows that your file is the same as the one the hash was made from. If an attacker can change both the download and the web page that lists its hash, the two will still match. Signed checksum files (for example with GPG) protect against that; this tool does not check signatures.
How the hash is computed
The file is read in 2 MB pieces. For SHA-256, SHA-512 and SHA-1 on files up to 256 MB, the pieces are joined in memory and passed to the browser's Web Crypto API in one call, which is fast. The progress bar then reaches 90% when reading ends and jumps to 100% when the digest is ready. MD5, and any algorithm on a file larger than 256 MB, is computed piece by piece with the node-forge library. That keeps memory use low, so large files work, but it is slower, and a file of several gigabytes can take minutes.
If you switch algorithm after a result is shown, the same file is hashed again with the new one.
Comparing with a published checksum
The Verify field ignores letter case and spaces at the ends, but nothing else. Paste only the hex value. A line copied from a .sha256 or SHA256SUMS file also contains the file name, and a prefix such as sha256: is not removed, so both show a mismatch. To check from the command line instead:
- Windows (PowerShell):
Get-FileHash file.zip -Algorithm SHA256 - macOS:
shasum -a 256 file.zip - Linux:
sha256sum file.zip
Frequently Asked Questions
Why does my hash not match the published one?
Check that you picked the same algorithm (a 64-character value is SHA-256, 128 is SHA-512, 40 is SHA-1, 32 is MD5) and that you pasted only the hex digits. If both are right, the file differs: the download may be incomplete, or you have a different version or a modified copy. Download it again from the official source.
Why does the same file give a different hash after I unzip and re-zip it?
A hash covers every byte of the file. Re-compressing changes timestamps and compression details inside the archive, so the bytes and the hash change even if the contents look the same.
Can I hash several files at once?
No. The tool hashes one file at a time. Drop the next file to replace the current one.
Related Tools
- HMAC Generator - when the hash must also prove who made it, use an HMAC with a shared secret.
- Bcrypt Generator - for passwords, which need a slow salted hash rather than SHA-256.
- Certificate Decoder - shows the SHA-256 and SHA-1 fingerprints of a TLS certificate.