Skip to content

# Binary Value & Endianness Inspector

Interpret one byte buffer many ways: unsigned/signed integers (two's and one's complement), IEEE-754 floats (half, single and double, with the sign/exponent/mantissa breakdown and a plain-language explainer), text (ASCII, UTF-8, UTF-16), a Unix timestamp, and IPv4/IPv6, across big/little endianness (big-endian is network byte order), plus a small struct-template mapper with per-field byte order and bit-fields. A hex/ASCII dump sits beside the readings: pick a reading and its bytes light up; pick a byte and the reading that explains it lights up.

This is generated in browser and is not sent to pah.moi servers.

About this tool3 paragraphs

Byte swap and word swap toggles rewrite the buffer before it is read (the network-byte-order and mixed-width comparison the tool is for) and the swapped bytes are printed so the transform is visible. You can type the bytes or open a local file.

Every reading is offered at once because bytes do not say what they are. The same four bytes are a plausible integer, a plausible float, a date in 1970 and a routable address simultaneously, and nothing in them prefers one. That is the point of showing all of them side by side rather than asking you to choose a type first, and it is also why a reading that looks sensible is a hypothesis rather than an answer.

Byte order is the same kind of claim. A buffer carries no record of the endianness it was written with, so the tool shows both and lets the plausible one identify itself; the struct-template mapper is for when you already know the layout and want the fields named. It reads a file's bytes and never its meaning: it will not tell you what produced them, and a file opened here is read in the browser and goes nowhere.

Use it locally This tool has a native command line twin. Build `binary-inspector-cli` from the site's source with:

    cargo build --release --bin binary-inspector-cli

Source and licence terms