Binary File Diff

Drop both files in. The tool compares every byte and tells you outright whether they are byte-for-byte identical, and it shows the SHA-256 of each file — if the two hashes match, the files are identical, which is the check most people are really after.

That is what this page is for. It gives you the same answers cmp and fc /b give — whether the files match, the offset of the first difference, and how many bytes differ — as a hex view you can scroll, with no install and no terminal.

On Linux, cmp -l a.bin b.bin lists every differing byte and cmp -s is a silent same/different check; diff reports only that binary files differ. On Windows, fc /b a.bin b.bin prints differing offsets in hex. This tool covers the same ground in the browser and adds the region summary those commands do not give you.

Matching bytes divided by the size of the larger file. Using the larger file as the denominator means a file with an extra tail cannot score 100% just because everything it shares with the shorter file matches.

Timestamps and embedded build metadata. Many formats stamp the creation time into a header, so byte-identical output requires a deterministic writer. A handful of differing bytes near offset 0 is the classic signature of that.

Not by itself. Padding, alignment, and trailing metadata all change size without changing meaning. Where the difference sits matters more than how big it is, which is why the summary reports the first differing offset and the individual regions.

There is no fixed cap — both files are read into memory in the page, so the limit is your device. The hex view stays fast on large files because it renders a window of rows around the offset you are looking at rather than the whole file.

No. Both files are read in the page and compared in memory, which also means very large files are limited by your device's memory rather than an upload cap.