Network & DevOps ToolkitFile Checksum & Verify
sha256sum in your browser — hash a file, or prove a download matches its published checksum.
The File tab is pre-selected — drop any file to hash it locally. Use the Verify & compare tab to paste a published checksum and get a match / no-match verdict (algorithm auto-detected).
Loading…
Verify downloads
Paste the checksum from a release page next to your downloaded ISO/installer — a mismatch means corruption or tampering.
Files never upload
Hashing streams through the browser's own crypto — a 2 GB ISO is read locally, chunk by chunk.
Beyond the basics
SHA-3, BLAKE2, CRC32, HMAC, UUIDs and JWT tools live in the tabs above when you need them.
Which algorithm should I verify with?
Whatever the publisher lists — SHA-256 is today's standard. MD5/SHA-1 still detect accidental corruption fine, but they're forgeable, so prefer the strongest checksum offered.
The checksums don't match — now what?
Re-download first (most mismatches are truncated downloads), verify you copied the full expected hash, then check you downloaded the exact file variant the checksum was published for. If it still fails, treat the file as untrusted.
How is this equivalent to sha256sum / certutil?
Identical output: sha256sum file.iso (Linux/macOS shasum -a 256, Windows certutil -hashfile file.iso SHA256) produces the same hex digest this page computes — just without opening a terminal.
Related tools
- Hash Generator — quick digests for text snippets.
- HMAC Generator — keyed signatures for webhooks.
- Base64 Encode / Decode — move digests between encodings.
🔐 Private by design: this tool runs entirely in your browser — nothing is uploaded, stored or logged.