File Checksum
Hashes files of any size in a streaming pass and compares the result against a pasted expected value.
Checksums a file in the browser — SHA-256, SHA-1, MD5 and the rest — and compares the result against a published checksum. The file is read from disk into this tab and never uploaded, which is the only sane way to verify a download.
Drop files here
Any size. The file is read in chunks and never loaded whole, so a multi-gigabyte ISO hashes without filling memory.
Files are read in this tab, in chunks, by a worker. Nothing is uploaded — there is no request to make, because the digest is computed here. The hash itself is safe to share: it identifies the file without revealing anything about its contents.
How to use it
Drop the downloaded file in
A large file is read in chunks so the tab stays responsive. Nothing is sent anywhere at any point.
Paste the checksum from the download page
The row that matches is highlighted. You do not have to know which algorithm was published — if it matches any of them, you will see it.
Check that it matches, not that it looks similar
A checksum differs in one character or in all of them; there is no "close". That is exactly why the comparison is done by the page rather than by eye.
Common questions
Does a matching checksum mean the file is safe?
It means the file is the one whose checksum was published. If the site publishing the checksum was compromised, both the file and the checksum changed together. A signature — GPG, minisign, a code-signing certificate — is what proves who made it; a checksum only proves the bytes arrived intact.
How big a file can it handle?
Gigabytes, in principle — the file is streamed rather than held whole. In practice the limit is browser memory pressure and your patience; a several-gigabyte ISO takes a while and works.
The site published only an MD5. Is that useless?
Not useless — it still catches a truncated or corrupted download, which is the failure you actually meet. It is useless against someone who wanted to give you a different file, because MD5 collisions are cheap to construct. Prefer the SHA-256 if both are offered.
Feed it from
Text Hash
Computes MD5, SHA-1, SHA-256, SHA-384, SHA-512 and CRC-32 of a string, with an uppercase and Base64 output option.
Data Size Converter
Converts bytes, KB, MB, GB and TB in both decimal and binary conventions, and computes transfer times.
File Encrypt & Decrypt
Encrypts any file with AES-256-GCM from a passphrase, and decrypts files it produced.
Archive Inspector
Opens a zip without extracting it and flags path traversal entries, executables, macros and zip bombs.
Next
These accept what this tool produces, so the result can go straight in.
Archive Inspector
Opens a zip without extracting it and flags path traversal entries, executables, macros and zip bombs.
Hash Identifier
Guesses which algorithm produced a hash from its length, charset and prefix, ranked by likelihood.
Text Hash
Computes MD5, SHA-1, SHA-256, SHA-384, SHA-512 and CRC-32 of a string, with an uppercase and Base64 output option.
Subresource Integrity Hash
Computes the Subresource Integrity attribute (sha256/384/512) for a script or stylesheet you paste or drop in.
Base64 Encoder & Decoder
Encodes and decodes Base64 and Base64URL for text or files, handling UTF-8 correctly.
curl to Code
Converts a curl command into fetch, axios, Python requests, Go, PHP or PowerShell.