Binary Record Inspector
Paste a test fixture hex dump and a field table to compare both byte orders and signed readings of the same bytes. Everything runs locally; nothing is uploaded or stored.
Source bytes and integer values
| Label | Offset | Type | Bytes | Value |
|---|
Format notes and FAQ
Types
| Type | Width | Meaning |
|---|---|---|
| u8 | 1 byte | Unsigned 8-bit |
| i8 | 1 byte | Signed 8-bit |
| u16le / u16be | 2 bytes | Unsigned 16-bit, little / big endian |
| i16le / i16be | 2 bytes | Signed 16-bit, little / big endian |
| u32le / u32be | 4 bytes | Unsigned 32-bit, little / big endian |
| i32le / i32be | 4 bytes | Signed 32-bit, little / big endian |
| u64le / u64be | 8 bytes | Unsigned 64-bit, little / big endian |
| i64le / i64be | 8 bytes | Signed 64-bit, little / big endian |
Limits
- Hex bytes: at most 4,096 bytes; field layout: at most 64 rows.
- Labels start with a letter, are at most 24 characters, and must be unique.
- Offsets start at 0; a field must not run past the end of the bytes.
- Two fields may share bytes; reading never edits the source.
- The downloaded report always uses the fixed name binary-record-inspector-report.json.
- Where does an offset start?
- The first byte is at offset zero.
- Can two fields overlap?
- Each field reads its requested bytes without editing them.