Skip to content

Hash and Checksum Generator

MD5 / SHA hashes of text or a file, plus a checksum verifier. Browser-only.

Runs locally in your browser

// digests
MD5legacy

—

SHA-1legacy

—

SHA-256

—

SHA-384

—

SHA-512

—

How it works

When you'll reach for this

Verifying a download

A release page publishes a sha256sum next to the binary. Drop the file in, pick SHA-256, and paste their value into the verify box. A green match means the bytes you got are the bytes they shipped; a mismatch means corruption or tampering, so do not run it.

Fingerprints and cache keys

Hashes give you a stable fingerprint for a config blob, a build artifact, or a cache key. SHA-256 is the modern default; MD5 and SHA-1 still show up on older download pages, so they are here for verification only. None of them belong anywhere near password storage, where bcrypt or argon2 is the right tool.

Frequently asked questions

Which hash should I use?

Use SHA-256 for integrity and checksums; it is the modern default (`sha256sum`). MD5 and SHA-1 are broken for security but still appear on download pages, so they are here for verification.

Can I verify a downloaded file?

Yes. Drop the file in, pick the algorithm the project publishes, and paste their expected checksum into the verify box. The file is read locally and never uploaded.

Is a hash the same as encryption?

No. Hashing is one-way: you cannot recover the input from the hash. Never use a raw hash to store passwords (use bcrypt/argon2 instead).

Is my data uploaded anywhere?

No. SHA hashing uses the browser Web Crypto API and MD5 runs in JavaScript, both locally. Nothing leaves your machine.

Tools are ported from DevOps Daily under the MIT license.View original

More tools

JWT Decoder

Inspect any JWT in your browser. Nothing is sent to a server.

Open tool

CIDR Subnet Calculator

Parse CIDR blocks, compute ranges, split into smaller subnets, and check whether an IP lives inside a network.

Open tool