Hash Compare Tool
Comparing two 64-character hashes by eye is error-prone. Paste both, and the tool compares them as bytes: it ignores upper and lower case, spaces, colons and prefixes such as “sha256:”, understands a hex value and a Base64 value for the same hash, and shows exactly where two hashes first differ.
- Runs in your browser
- No sign-up
- Free to use
How to use Hash Compare Tool
- Paste the first hash, for example from a download page.
- Paste the second hash, for example from your own calculation.
- Read the verdict.
- If they differ, look at the first difference and the lengths.
Hash Compare Tool features
Byte comparison
Compares the actual values, not the text formatting.
Format tolerant
Case, spaces, colons and algorithm prefixes ignored.
Hex and Base64
Recognises the same digest in different encodings.
First difference
Marks the position where the hashes diverge.
Strict mode
Untick the option to compare exact text.
Private
Nothing is sent anywhere.
When to use Hash Compare Tool
- Confirming a download matches the published checksum.
- Comparing hashes from two different tools.
- Checking a signature against an expected value in Base64.
- Spotting a truncated or mistyped hash.
Hash Compare Tool FAQ
Why not just compare the text?
Because the same hash can be written in upper or lower case, with spaces or colons every two characters, with a prefix, or in Base64. Comparing bytes avoids false mismatches.
What does “lengths differ” mean?
The hashes have different sizes, so they come from different algorithms, for example MD5 and SHA-256, or one was cut short when copied.
Can a hex and a Base64 hash be equal?
Yes. They are two encodings of the same bytes. The tool decodes both before comparing.
Does a match prove a file is safe?
It proves the file matches the hash. Whether that means safe depends on the algorithm and on whether the expected hash came from a trusted source.
Is the comparison timing-safe?
Yes, bytes are compared in constant time, though this matters only on servers.
Is anything sent?
No. The comparison runs in your browser.
Small differences, big consequences
The last step of verifying a download is comparing two long strings, and it is where people make mistakes. Eyes skip characters; publishers format hashes differently; tools output upper or lower case. A comparison that understands those variations and checks every character removes the risk.
Comparing as bytes is the key. The tool removes formatting, decodes hexadecimal or Base64 into raw bytes, and checks that both byte sequences are identical. Two values that look different on screen can be the same hash, and two that look almost identical can differ in a single character in the middle.
When hashes do not match, the details help. Different lengths mean different algorithms or a truncated copy. Equal lengths with a single differing character suggest a typing mistake. Completely different values mean the file is not the one the publisher hashed, perhaps an incomplete download or a different version.
A match is only as meaningful as the source of the expected hash. Take it from the publisher’s official site over HTTPS or from a signed release file, not from the same place you downloaded the file from if that place is untrusted.