Skip to content
English
All tools

Categories

Developer ToolsEncoding & DecodingJSON & DataHash & ChecksumText ToolsDate & TimeNetwork ToolsFile ToolsMarkdown & Diagrams

Hash Verifier

Paste the checksum you were given, drop the file, and see whether they match.

Processed locally in your browser

Options

What is Hash Verifier?

When a project publishes a checksum with a download, comparing it with the hash of your copy tells you whether the file is byte-identical to the one that was hashed. Doing it by eye on a 64-character string is error-prone, so this tool does the comparison for you.

Paste the expected hash (case, spaces and prefixes such as "sha256:" are ignored, and lines from checksum files work too). The algorithm is detected from the length: 8 hex characters for CRC32, 32 for MD5, 40 for SHA-1, 64 for SHA-256 or SHA3-256, 96 for SHA-384, 128 for SHA-512. Ambiguous lengths are tried with every candidate and the tool tells you which one matched. Instead of a file you can hash typed text.

How does it work?

  1. Paste the expected hash in the first field. Leave the algorithm on Auto-detect or force one.
  2. Drop the file to check (or type text in the optional second field to hash text instead).
  3. Press Verify. You get MATCH or NO MATCH, the computed digest and which algorithm matched.

Common use cases

  • Checking a Linux ISO or an installer against the checksum on the download page.
  • Confirming that a file copied to a USB drive or a server was not corrupted.
  • Comparing the SHA-256 in a signed release note with the artifact you built.
  • Testing that a string still hashes to the value stored in a database or config.

Examples

Paste the checksum you were given, drop the file, and see whether they match.

Privacy

Hash Verifier runs entirely in your browser. The text or files you provide are processed on your device and are not uploaded, logged or stored on our servers.

Limitations

A matching hash does not prove a file is safe or genuine: it only shows the file equals whatever produced the expected hash. Get the reference from a trusted source that is separate from the download (for example a signed release page), because an attacker who replaces the file can replace a checksum on the same page.

Frequently asked questions

What does NO MATCH mean?

The computed hash differs from the expected one: the file is different or corrupted, you picked the wrong algorithm, or the expected value belongs to another file. Re-download and try again.

Why are two algorithms tried for a 64-character hash?

SHA-256 and SHA3-256 both give 64 hex characters, so length alone cannot tell them apart. Both are computed and the matching one is reported.

Is my file uploaded to check the hash?

No. The file is read and hashed locally in chunks by your browser; nothing leaves your device.

Related tools

More tools in Hash & Checksum →