Binary Value & Endianness Inspector
Interpret one byte buffer many ways at once: integers, IEEE-754 floats, text, a Unix timestamp and IP addresses, in either byte order. 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 tool4 paragraphs
The readings are unsigned and signed integers (two's and one's complement), IEEE-754 floats (half, single and double, with the sign, exponent and mantissa broken out and explained in plain language), text (ASCII, UTF-8, UTF-16), a Unix timestamp, and IPv4 and IPv6 addresses. Each is read in both big-endian and little-endian order, and big-endian is the one networks use.
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 why every reading is shown at once instead of asking you to pick a type first. A reading that looks sensible is a good guess, not proof.
Byte order is a guess too. A buffer carries no record of the order it was written in, so both are shown and you pick the one that makes sense. The struct-template mapper is for when you already know the layout and want the fields named, with a byte order per field and bit-fields. 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.
binary-inspector-cli from the site's source with:
cargo build --release --bin binary-inspector-cliSource and licence terms