decoder.tools

Hexdump & Byte Stream Parser

Render any input as a classic offset / hex / ASCII hexdump.

live · client-sideData, Radix & Stringfree · no sign-up
RAW INPUT
DECODED

Output appears here as you type — decoded on your device.

Input is processed on your device. Nothing you paste is sent anywhere.

What is the Hexdump & Byte Stream Parser?

A hexdump is a three-column view of binary data — byte offset, hexadecimal byte values, and their printable ASCII rendering — that lets you inspect raw bytes and spot structure that plain text hides.

The hexdump is the oldest and still the most useful way to look at bytes. The left column gives the offset so you can talk about a position precisely; the middle shows 16 bytes in hex; the right shows the same bytes as ASCII, with dots standing in for unprintable values. Structure jumps out: file magic numbers, null padding, repeating keys, embedded strings.

This viewer produces the same layout as xxd or hexdump -C, without installing anything or leaving the browser. It is particularly handy when you already decoded something — a Base64 blob, a hex string, an inflated stream — and now need to see whether the result starts with a recognisable signature such as PK for a zip or %PDF for a PDF.

Hexdump & Byte Stream Parser at a glance

Layout
offset | 16 hex bytes | ASCII gutter
Equivalent to
xxd, hexdump -C, od -A x -t x1z
Unprintable bytes
Shown as . in the ASCII column
Offsets
Hexadecimal, 16 bytes per row

How to use the Hexdump & Byte Stream Parser

  1. 1Paste or type the data you want to inspect.
  2. 2Read the dump: offsets on the left, hex in the middle, ASCII on the right.
  3. 3Look at the first bytes for a file signature, and scan the ASCII gutter for embedded strings.

When you would reach for it

  • Identifying an unknown blob from its magic bytes before choosing a parser.
  • Spotting null padding, alignment or a repeating XOR key in a binary.
  • Checking exactly which bytes a decoder produced, without character-set guesswork.

Hexdump & Byte Stream Parser — frequently asked questions

Last reviewed · questions or corrections: contact@decoder.tools