biodiff1.2.1

Biodiff places two binary files side by side in a hexadecimal diff view, aligning similar regions so corresponding bytes can be inspected and changes can be spotted directly. Developed by 8051Enthusiast, this open-source Windows System Tools utility is aimed at developers, technical analysts, and others investigating low-level file content. Its alignment engine draws on bioinformatics algorithms from wfa2 or rust-bio, libraries commonly used for DNA-sequence alignment, which distinguishes it from conventional byte-by-byte comparisons.

The unaligned view lets each file move independently as contiguous byte segments, while the aligned view lines up corresponding bytes and pads gaps where one file has missing data. Users can choose binary, octal, decimal, or hexadecimal byte displays, combine ASCII with hexadecimal, or use braille and Roman-numeral representations; right-to-left mode, ASCII and bar columns, and horizontal or vertical splits are also configurable. Row density can be adjusted with [, ], and 0, while pressing = determines the width automatically by detecting repetitions in visible or selected bytes; searches accept text, regular expressions, and hexagex.

In an interactive comparison, opening biodiff with two file paths starts in an unaligned side-by-side hex view, and F3 or 3 aligns the files block by block after the views are positioned over similar content. F4 exposes alignment settings for whole-file global comparison, while selecting bytes on one side and pressing F3 performs semiglobal alignment to locate that region as a pattern in the other file. Global alignment uses quadratic time and space and generally performs poorly above 64 kB, whereas the banded algorithm is faster with slightly lower accuracy.

The comparison can print directly in a terminal with biodiff --print file_a file_b, and small files can use -gglobal for whole-file rather than blockwise alignment. Current version 1.2.1 supports x64 systems running Windows 8 or later or Windows Server 2012 or later; configuration dialogs use the cursive library. Advanced users can also run the program from its source with cargo run --release -- file_a file_b.