devopscodepro
Language
Productized services
Infrastructure AuditRisks, costs and quick wins — mapped in two weeks.Cloud Migration & IaCTerraform, CI/CD and a zero-downtime cutover.Monitoring-as-a-ServiceAlerting, on-call and incident response.Fractional DevOpsA senior engineer in your team, part-time.
Not sure where to start? The audit answers that.Request a quote →
server-assisted · every other tool runs in your browserAll 41 tools →
Infrastructure AuditCloud Migration & IaCMonitoring-as-a-ServiceFractional DevOps
ContactLog in
Request a quote
Theme
Language
Runs entirely in your browser — nothing leaves this page.

Hash & checksum

Every digest of a text or file at once — SHA-2, SHA-3, Keccak, BLAKE2b/BLAKE3, RIPEMD-160, MD5, SHA-1, CRC-32, Adler-32 — with a checksum-match field.

Type or paste above — every digest updates as you type.
These tools show symptoms. A full infrastructure audit finds the causes — risks, cost leaks and single points of failure, mapped in two weeks.
Request a quote →

One input, every digest

Paste text or drop a file and get all fourteen digests at once: the SHA-2 family, SHA-3 and Keccak-256, BLAKE2b and BLAKE3, RIPEMD-160, the legacy MD5 and SHA-1, and the CRC-32 and Adler-32 checksums. Files are read in chunks and hashed locally — a 4 GB ISO never leaves your disk, let alone your browser.

The expected-checksum field is the reason this tool exists: paste the value from a vendor's release page and the matching row lights up, whatever the algorithm and whether it was published as hex or base64. No more eyeballing two 64-character strings.

The output switcher renders every digest as lowercase or uppercase hex, Base64, Base64URL or raw bytes — the four representations you actually meet in configs, signatures and container manifests.

Is my file uploaded anywhere?

No. The file is read with the browser's File API and hashed in JavaScript on your machine. Nothing is transmitted — you can verify with the network tab open, or offline.

Which algorithm should I use to verify a download?

Whichever the vendor published, because you need to match their value. When you have a choice, SHA-256 is the standard answer. MD5 and SHA-1 still work for accidental-corruption checks, but a signature they carry proves nothing — collisions are practical for both.

Why does Keccak-256 differ from SHA3-256?

Ethereum adopted Keccak before NIST finalized SHA-3 with different padding, so the two produce different digests for the same input. If you are checking an Ethereum address or a Solidity selector, you want Keccak-256; a FIPS-compliant system wants SHA3-256.

What are CRC-32 and Adler-32 for, if they are not cryptographic?

Error detection. They catch accidental corruption in archives and network frames — zip, gzip and PNG all embed CRC-32 — and they are fast. What they cannot do is resist a deliberate attacker: forging a file with any CRC you like is trivial.

Why is hashing a big file with SHA-3 slow?

SHA-3 in JavaScript is an order of magnitude slower than SHA-256, which browsers and CPUs optimize heavily. That is why file mode starts with the digests people actually verify downloads with, and the rest are one click away.

Related tools: HMAC generator, Encrypt / decrypt and Base64.