Security

Hash / Checksum

Compute MD5, SHA-1, SHA-256, SHA-384, SHA-512 and CRC32 of text or a file, and compare them against an expected value to verify the integrity of a download. All in your browser — nothing is uploaded.

redzilla.cl — hash

Verification

—

paste an expected value to compare

Source

Text

—

MD5 —

SHA-1 —

SHA-256 —

SHA-384 —

SHA-512 —

CRC32 —

All algorithms

Algorithm	Bits	Hash (hex)

How it works · hash, checksum and verification

1. A hash reduces any input to a fixed-size fingerprint. Changing a single bit changes the hash completely, so it works to verify integrity.

2. SHA-1/256/384/512 are computed with the browser's Web Crypto. MD5 (RFC 1321) and CRC32 (polynomial 0xEDB88320) use a built-in JavaScript implementation.

3. MD5 and SHA-1 are deprecated for security (known collisions). Use them only as a checksum; for real integrity prefer SHA-256 or higher.

4. Paste the published hash into expected value: if it matches any, it is flagged in green; if it matches none, in red.

Runs locally in your browser · no sign-up · nothing leaves your browser.

How it works

The tool computes six fingerprints of the same input: MD5 (128 bits, RFC 1321), SHA-1 (160), SHA-256, SHA-384, SHA-512 and the CRC32 checksum (polynomial 0xEDB88320). The input can be text (encoded as UTF-8 before hashing) or a file you drag in or select; the file is read locally with the browser File API and is never uploaded to any server.

The SHA family is computed with crypto.subtle.digest (Web Crypto, the browser native implementation) while MD5 and CRC32 use JavaScript implementations verified against the test vectors of their standards. If you paste an expected value (the hash published next to a download, even in md5sum or shasum format with a filename), the tool compares it case-insensitively against all six results and gives a verdict: match (file intact) or no match.

Example: verifying the integrity of a downloaded ISO image

The official site publishes the hash: SHA-256: a1b2…f9. Switch to the File tab and drag in the downloaded ISO.
Paste the published hash into the expected value field; even the hash *file.iso format works.
If the computed SHA-256 matches, the verdict turns green: the download arrived intact. You can sanity-check with a test string: the SHA-256 of abc starts with ba7816bf and its MD5 is 900150983cd24fb0d6963f7d28e17f72.

Frequently asked questions

What is the difference between a hash and a checksum like CRC32?

Both condense the input into a fixed fingerprint, but with different goals. CRC32 (32 bits) detects accidental transmission errors and is easy to forge on purpose. A cryptographic hash like SHA-256 (256 bits) is designed so that crafting another input with the same fingerprint is infeasible, which is why it is used to verify downloads and signatures.

Why are MD5 and SHA-1 considered obsolete?

Because they have demonstrated collisions: two different files can be built with the same hash. They are still useful as a quick checksum or to compare against old published hashes, but to guarantee integrity against an attacker use SHA-256 or stronger.

What if the computed hash does not match the published one?

First confirm you compared the right algorithm (a SHA-256 will never match a published MD5) and that the download finished completely. If the algorithm is correct and it still does not match, the file is corrupted or was tampered with: download it again from the official source and do not run it.

Is it safe to hash private files on this page?

Yes. The file is read with FileReader inside your browser and the hashes are computed locally with Web Crypto and JavaScript: neither the file nor the result is sent to any server. You can verify this by disconnecting from the internet after the page loads.

Was this tool useful?

Disclaimer

We take great care to keep every tool accurate and review it thoroughly; even so, we can't guarantee it is free of errors or take responsibility for how the results are used. We recommend double-checking anything critical.

Found an error? Let us know →