Neatbo.

Binary byte differences

Locate exact differing offsets and both hexadecimal byte values in two local binary files.

Browser-local processingInputTwo binary filesOutputHex offsets / JSON / CSVUp to 10 MiB per file · File limit: 2
  1. 1Add input
  2. 2Review and run
  3. 3Get your result

Tool input and files are processed in this browser without being uploaded.

Your input

Inputs are kept temporarily in this tab when switching tools. Refreshing or closing clears them; large results may need to be regenerated.

⌘ / Ctrl + Enter to run

or drag and drop them here

Files stay on this device. Your originals stay unchanged.

Up to 10 MiB per file · File limit: 2

    Preparing the tool…

    Before you start

    Compare arbitrary bytes at the same offsets, including empty files and missing tail bytes. The complete JSON and CSV list every difference; the on-screen table previews the first 200. Inputs are never decoded as text.

    How to use this tool

    1. Choose the left and right binary files in order.
    2. Compare same-offset bytes and inspect hexadecimal offsets and the two values.
    3. Download complete JSON/CSV to review all differences. Reduce the files if the complete report exceeds its limit.

    Supported inputs and limits

    Exactly two files up to 10 MiB each and 20 MiB total; at most 100,000 differences and 20 MiB per complete report. A larger difference report is rejected rather than silently truncated.

    Comparison uses equal offsets. It does not realign inserted or deleted blocks. Offsets are zero-based hexadecimal; a missing side is null in JSON and missing in CSV. Both empty files compare equal.

    Worked example

    Example input

    Left bytes: 00 90 00 11; right bytes: 00 91 00 10.
    Example options
    {}

    Example output

    Offset 0x1: 90 → 91; offset 0x3: 11 → 10; 2 differences.

    When something does not work

    Choose exactly two files within the byte budget. If more than 100,000 bytes differ, compare smaller files or regions; no partial complete-report claim is returned.

    Frequently asked questions

    Does it understand a file format or character encoding?

    No. It compares raw bytes and reports their hexadecimal values.

    How are inserted bytes handled?

    The files are compared at equal offsets, so an insertion can cause later bytes to differ. It does not compute an insertion-aware alignment.

    Will a long comparison omit differences?

    No. The preview is bounded, but downloadable reports are complete. Exceeding the full-report budget fails explicitly.

    Documentation & further reading

    Related tools