Hash Generator & Checksum Verifier
Calculate SHA-256, SHA-512, SHA-3, MD5, SHA-1, BLAKE3 and CRC32 hashes for files of any size or plain text, then verify them against a published checksum — all inside your browser.
Input
Drop a file here or click to browse
Any size — read in chunks, never uploaded
Hashes
Choose a file or switch to Text.
No hashes yet
Results for each selected algorithm will appear here.
Verify a checksum
Paste the expected hash from the download page. Case, spaces and colons are ignored; the algorithm is detected automatically.
How to verify a file checksum
Add your file
Drop the downloaded file (ISO, installer, archive, firmware…) onto the drop zone. It is read in 4 MB chunks, so multi-gigabyte files work without filling memory.
Pick the algorithm the publisher used
Most projects publish SHA-256. Select it (and any others you need) and click Calculate.
Paste the published checksum
Paste the expected value into Verify. A green match means the file is byte-for-byte identical to what the publisher hashed.
Which hash algorithm should you use?
A cryptographic hash turns any input into a fixed-length fingerprint. Change a single bit and the hash changes completely, which makes hashes ideal for detecting corruption or tampering.
| Algorithm | Output | Status | Use it for |
|---|---|---|---|
| SHA-256 | 64 hex | Secure | The default for downloads, packages and signatures |
| SHA-512 / SHA-384 | 128 / 96 hex | Secure | When a vendor or protocol requires them; fast on 64-bit CPUs |
| SHA3-256 / SHA3-512 | 64 / 128 hex | Secure | Standards requiring FIPS 202 SHA-3 |
| BLAKE3 | 64 hex | Secure | Very fast integrity checks of large files |
| SHA-1 | 40 hex | Broken (collisions) | Legacy mirrors and Git object IDs only |
| MD5 | 32 hex | Broken (collisions) | Detecting accidental corruption only |
| CRC32 | 8 hex | Not cryptographic | ZIP/PNG checks and quick error detection |
Note: some online tools label Keccak-512 as “SHA-3”, which produces different output. This generator implements the standardised FIPS 202 SHA-3, matching sha3sum, OpenSSL and Python’s hashlib.
Calculate a checksum on the command line
# macOS / Linux
shasum -a 256 file.iso # or: sha256sum file.iso
# Windows PowerShell
Get-FileHash .\file.iso -Algorithm SHA256
# Windows Command Prompt
certutil -hashfile file.iso SHA256Frequently asked questions
Are my files uploaded?
No. Files are read directly by your browser with the File API and hashed with WebAssembly on your device. Nothing is sent to a server, so it also works for confidential files.
Is there a file size limit?
No practical limit. Files are streamed in 4 MB chunks and every selected algorithm is updated incrementally, so memory use stays flat even for files larger than your RAM.
How do I generate a SHA-256 hash of text?
Switch to the Text tab and type or paste your text. The SHA-256 (and any other selected) hash updates as you type. Text is encoded as UTF-8, matching echo -n "text" | sha256sum.
Is MD5 or SHA-1 still safe?
Not for security. Both have practical collision attacks, meaning an attacker can craft two different files with the same hash. They are still fine for spotting accidental corruption, but prefer SHA-256 to confirm authenticity.
Why doesn’t my hash match?
Check that you selected the same algorithm the publisher used, that the download finished completely, and that you are comparing against the checksum for the exact file version. For text, invisible differences like a trailing newline or Windows line endings change the hash.