piapia123
en

Byte Sequence Parser

Web

Everything runs locally in your browser — nothing is uploaded

Input
Drop a file here to load its contents
Output

Read a "byte string" as actual bytes and print it in another notation: four input formats (hex, decimal, Base64, binary) and five outputs. Input accepts `48 65 6C 6C 6F`, `0x48656c6c6f`, comma- or newline-separated forms and more. Beyond the bytes, you get the byte count and the UTF-8 text when it decodes — often the real answer to "what is this?". An odd number of hex digits (such as `486`) is always an error; nothing is padded or truncated. Everything runs locally in your browser — the data never leaves the device.

Features

  • Four input formats: hex, decimal, Base64, binary
  • Five output formats: hex, decimal array, UTF-8 text, Base64, binary
  • Hex accepts 0x / \x prefixes and spaces, colons, commas or hyphens as separators
  • Decimal accepts bracketed lists; binary is grouped eight bits per byte
  • Base64 accepts data-URL prefixes and the URL-safe - and _
  • Adjustable bytes per line (1–32)
  • Reports the byte count and any decodable UTF-8 text
  • Odd-length hex, out-of-range decimals and bad bit counts are all reported clearly

How to use

  1. Pick the input format (hexadecimal by default)
  2. Paste the byte string into the box
  3. Choose an output format; the result updates as you type
  4. Use the copy button on a row to take just that value

FAQ

Why does hex `486` fail instead of becoming `0486` or `48`?
An odd number of hex digits can only mean the input was cut short. Padding a zero or dropping the last digit both produce a byte sequence that looks fine but is already wrong — you would only notice when it fails somewhere else. So the tool refuses, and lets you see which digit is missing.
Can I mix 0x prefixes with spaces?
Yes. `0x48 0x65 0x6C`, `0x48656c6c6f`, `48 65 6C` and `48,65,6c` are all accepted, and they can be mixed. The prefixes and separators are stripped for you — there is no need to clean the input first.
Why is the UTF-8 text row empty or flagged?
Not every byte sequence is text. The bytes of an image, key or archive are not valid UTF-8, and forcing them through it would only show replacement characters. The tool says plainly that the bytes are not valid UTF-8 rather than handing you mojibake.
Is my data uploaded anywhere?
No. Parsing and conversion happen entirely in JavaScript in your browser, with no network requests. The input never reaches a server, and it works offline.

Related tools

Hex Converter

Encoding

Convert between hexadecimal and text, accepting 0x, \x, spaces and colons, with UTF-8 byte counts shown. Runs in your browser.

Bitwise Calculator

Convert

Ten bitwise operations: AND, OR, XOR, XNOR, NAND, NOR, NOT, shifts and bit reversal, with decimal, binary and hex for every result.

UTF-8 Viewer

Encoding

See a text as UTF-8 bytes, code points, percent-encoding, HTML entities and escapes side by side, with character and byte counts kept apart.

URL Parser

Web

Parse a URL into scheme, host, port, path, query parameters and fragment, with each parameter shown raw and decoded. Runs entirely in your browser.

User-Agent Parser

Web

Parse a user agent into browser, version, OS, device type and engine, and see which rules matched. Pattern matching only. Runs entirely in your browser.

HTTP Status Codes

Web

Look up an HTTP status code for its meaning, 1xx–5xx class, typical uses and common traps. Runs entirely in your browser.

← Back to all tools