Rules
Online Byte Parser & Hex/Binary Converter
Paste a comma-separated list of byte values (0–255) to inspect them as a table, extract named ranges as hex, binary, string, or number using custom rules, or switch to the Converters tab for one-off hex/binary/decimal/string conversions. Handy for debugging binary protocols, inspecting serialized data, or decoding a byte array from an API response. It helps developers inspect binary payloads, protocol fields, and file-size values when raw bytes are difficult to read directly.
What is a Byte Parser?
A byte parser takes a raw sequence of byte values — the kind of data you get from a network capture, a binary file, a serialized protocol message, or a firmware dump — and lets you inspect, extract, and convert it without writing a script just to look at the numbers. Instead of manually counting offsets in a hex editor, you paste the bytes once and work with them interactively.
How to use this byte parser online
Paste a comma-separated list of byte values (each between 0 and 255) into the input box and click Parse Bytes. The table shows each byte's position, decimal value, and hex value side by side. To pull out a meaningful chunk — say, a 4-byte length field or an 8-byte header — add a rule with a start and end index and choose how to interpret it (string, number, hex, or binary); the matching bytes are highlighted directly in the table.
Converters
Switch to the Converters tab for one-off conversions that don't need the full table view: hex to bytes, bytes to hex, bytes to string, string to bytes, bytes to binary, binary to bytes, decimal to hex, hex to decimal, and multi-byte conversion in both big-endian and little-endian order.
Common use cases
- Debugging a binary network protocol by inspecting raw packet bytes
- Decoding a serialized data structure from an API or file format
- Converting a byte array from an API response into a readable string or number
- Checking endianness when a multi-byte value looks wrong after decoding
Everything runs client-side in your browser — nothing you paste is ever uploaded to a server. You can save parsed entries locally to come back to later, or work entirely without saving anything.
How to use Byte Parser for related tasks
Paste the byte representation, choose the relevant interpretation, and verify offsets carefully because an off-by-one range changes the decoded value.
Related tools: Number / Byte Formatter, Base Converter.
Frequently asked questions
Is my byte data secure when I use this tool?
Yes. All parsing and conversion happens entirely in your browser — nothing you paste is ever sent to a server. That matters if you're inspecting bytes from a real protocol capture, firmware dump, or serialized production data.
What format should I paste my bytes in?
Comma-separated decimal values (e.g. 72, 101, 108, 108, 111), each between 0 and 255. Use the Converters tab if your data starts out as a hex string or binary text instead of decimal bytes.
How do I extract a specific range of bytes?
After parsing, add a rule with a start and end index — the tool extracts that range and converts it to hex, binary, string, or number, and highlights the matching columns in the byte table.
Can I convert a large number spread across multiple bytes?
Yes — the Converters tab includes multi-byte conversion in both big-endian and little-endian order, for turning a sequence of bytes into a single decimal or hex value and back.
What causes an incorrect byte conversion?
Endianness, hexadecimal versus decimal input, and incorrect start or end offsets are common causes; confirm the input representation first.