Hex Dump Viewer

View text or binary files as an xxd-style hex dump with offset addresses, hex bytes, and ASCII preview.

Input Mode

Bytes / Row

Address Format

Input Text

Presets:

Total Bytes55 B

Total Rows4

Printable ASCII98% (54)

Non-Printable1 B

xxd output format (16 bytes / row)

00000000  48 65 6c 6c 6f 20 5a 65  72 6f 53 65 72 76 65 72  |Hello ZeroServer|
00000010  20 54 6f 6f 6c 73 21 0a  57 65 6c 63 6f 6d 65 20  | Tools!.Welcome |
00000020  74 6f 20 74 68 65 20 48  65 78 20 44 75 6d 70 20  |to the Hex Dump |
00000030  56 69 65 77 65 72 2e                              |Viewer.|

What is a hex dump?

A hex dump displays a binary or text file's raw bytes in hexadecimal notation, organized in rows with an offset memory address at the left, hex bytes in the center, and an ASCII preview column on the right. It is an indispensable debugging tool for inspecting binary file headers, network protocols, executable files, and encoded payloads. The xxd format used here is compatible with classic Unix development utilities.

Built and maintained by Meet Shah · Last updated 1 August 2026

What this tool is used for

Inspecting a binary file's bytes alongside their ASCII rendering.
Finding a file's magic number to identify its real format.
Locating a string inside a binary and noting its byte offset.
Checking a header's field values at known offsets.
Comparing two files at the byte level to find where they diverge.

Frequently Asked Questions

What are the three columns?: The offset in hex, the bytes themselves in hex, and an ASCII rendering with non-printable bytes shown as dots. That layout is unchanged since Unix `hexdump` and it is why every hex viewer looks alike — the columns answer where, what, and is-it-text.
What are magic numbers?: The signature bytes at the start of a file that identify its format: `%PDF` for PDF, `PK` for ZIP and everything built on it, `\x89PNG` for PNG, `GIF89a` for GIF. Checking them is how `file` identifies a type without trusting the extension.
Why is 16 bytes per row standard?: Because it makes the offset column a clean multiple — each row starts at a multiple of 0x10, so the low digit of any address is its column position. That property is what makes it possible to read an offset off the display without arithmetic.
How do I tell text from binary?: By the ASCII column. Runs of readable characters mean text; sparse dots with structure mean binary. A UTF-16 file is the giveaway case — readable letters alternating with null bytes, which is what makes it look corrupted to a tool expecting UTF-8.
What is endianness in a dump?: The order multi-byte values are stored in. The 32-bit value 0x12345678 appears as `12 34 56 78` big-endian and `78 56 34 12` little-endian — and x86 is little-endian, so numbers in a memory dump read backwards until you expect it.

Common errors and gotchas

Reading multi-byte values without knowing the endianness, which reverses them.
Assuming the ASCII column is text, when it renders any printable byte regardless of encoding.
Trusting a file extension over the magic number, which is what actually identifies the format.
Loading a very large file into a browser tab, which can exhaust memory.
Miscounting an offset by reading the hex column as decimal.