SECURITY

File Hash Checker

Calculate MD5, SHA-1, SHA-256, or SHA-512 checksums locally.

LOCAL CHECKSUMS

Hash a local file

Browser-only
Algorithm

Hashing…

Hashing runs entirely in your browser — files are read locally and never uploaded. Use SHA-256 to verify downloads against the checksum on the publisher’s site; MD5/SHA-1 are fine for non-security integrity checks.

Your file stays on this device and is never sent to NAB Tools.

File hash calculator guide

A file hash is a fixed-length digest calculated from a file’s bytes. Comparing hashes can help detect changed or corrupted downloads, but it does not establish whether a file is safe or who published it.

This tool computes MD5, SHA-1, SHA-256, and SHA-512 checksums locally in your browser. It reads the whole file into memory, so very large files may exceed your device’s available memory; nothing is uploaded.

Verifying a download

A publisher may provide a checksum (usually SHA-256) for a download. Compute the file’s SHA-256 here and compare the full value with the publisher’s value. A match is strong evidence that the bytes are the same; it does not prove the file is safe or establish who published it. If an attacker can replace both the download and the checksum on the same page, both may match while being untrustworthy. Prefer a checksum delivered through an authenticated channel or a verified digital signature.

Use SHA-256 or SHA-512 for security-sensitive comparisons. MD5 and SHA-1 have known collision weaknesses and should not be trusted to detect deliberate tampering; they can still detect accidental changes.

Which algorithm when?

  • SHA-256 — the modern standard for download verification, certificates, and Git.
  • SHA-512 — a longer variant; used when a 512-bit output is needed.
  • MD5 — legacy; still seen in old systems and as a fast cache key, but cryptographically broken.
  • SHA-1 — deprecated since 2017 (real collisions demonstrated); avoid for security.

How hashes help compare files

A hash is a fixed-length digest of a file’s bytes. A mismatch shows that the files differ; a matching SHA-256 digest is extremely strong evidence that their bytes match, though a hash comparison is not a mathematical proof of identity or a safety check.

This tool reads the whole file into browser memory before hashing it with Web Crypto (or a local MD5 implementation). Large files may exceed the memory available to your browser; for those, use a local command-line hashing tool. The file is not sent to a server.

Frequently asked questions

What is a file checksum?

A hash of a file’s entire contents — a fixed-length string that changes if any byte changes. Used to verify downloads and detect corruption or tampering.

How do I verify a downloaded file?

Compute its SHA-256 here and compare it with a checksum obtained through an authenticated source. A match is strong evidence that the bytes match, but does not prove who published the file or whether it is safe; if the download page itself is compromised, both file and checksum could be replaced.

Is MD5 safe to use?

No, not against deliberate tampering — MD5 collisions can be crafted in seconds. It is fine for accidental-corruption checks but never for security verification.

Can I hash a very large file?

This tool reads the entire file into browser memory before hashing. A large file may use too much memory or fail, depending on your device and browser; use a local command-line tool for files that do not fit comfortably in memory.

Is my file uploaded?

Never. Files are read locally and hashed in your browser — nothing is transmitted.

Privacy note: file hashing happens in your browser. Your file is not stored or uploaded.