admin@likeapro.dev: ~/hash — zsh

// admin tools · 02

Hash everything

Checksum files and text with MD5, SHA-1 and the SHA-2 family, then paste a published hash to prove your download is intact. Files never leave this tab.

// runs locally — nothing is uploaded

algorithms
queue empty
FILE local only · 0 bytes sent --:--:--

How it works

What it does

Calculates MD5, SHA-1, SHA-256, SHA-384 and SHA-512 checksums for files or text, then compares the result with a published checksum. Use it to confirm a download hasn't been corrupted or tampered with. Files are read and hashed in your browser — they are never uploaded.

How to use it

  1. Pick the algorithms and an output format: lowercase hex, uppercase hex or base64.
  2. Drop one or more files into --file. They queue and hash in order, with a progress bar for large files. Or type into --text to hash a string live, encoded as UTF-8.
  3. Paste the expected checksum into compare. It accepts hex, base64, a sha256sum-style hash  filename line or a BSD-style SHA256 (file) = … line. The matching row lights up with ✓ MATCH, or the tool reports a mismatch.

The algorithms

SHA-256
256-bit SHA-2 digest. The standard for checksums, package registries and signatures.
SHA-384 · SHA-512
Longer SHA-2 variants. SHA-384 is common in Subresource Integrity (integrity="sha384-…") attributes.
SHA-1
Legacy. Practical collisions have been demonstrated. Fine for detecting accidental corruption, not for security.
MD5
Legacy / non-cryptographic. Collisions are trivial to create. It's here because many old download pages still publish MD5 sums.

How it works

SHA digests use the browser's WebCrypto crypto.subtle.digest. WebCrypto doesn't include MD5, so MD5 is a small JavaScript implementation of RFC 1321 that hashes incrementally. Files are read in 4 MB chunks. Because WebCrypto has no streaming digest, the whole file must sit in memory once for SHA. Very large files (over about 500 MB) may strain the tab, and the limit is about 2 GB. For anything bigger, use sha256sum, shasum -a 256 or certutil -hashfile locally.

Checksum comparison is case-insensitive and done in constant time.

FAQ

Why doesn't my hash match the one on the website?

Check you picked the same algorithm (the digest length is a clue: MD5 is 32 hex characters, SHA-1 40, SHA-256 64). Then check you downloaded the same file version. For text, an invisible trailing newline changes the hash, so try the trim trailing newline option.

Can I hash a password with this?

You can compute the digest, but never store passwords as plain SHA or MD5 hashes. They are designed to be fast, which makes guessing cheap. Use bcrypt, scrypt or Argon2. The htpasswd tool generates bcrypt hashes.

Is my file uploaded?

No. The file is read with the browser's File API and hashed on your device. You can disconnect from the network and it still works.