Hex dump viewer — see the bytes behind any text, hex or Base64

How to use the hex dump viewer

1. Paste into Input.
2. Set Input is to Text (UTF-8), Hex or Base64, to match what you pasted.
3. Choose Bytes per row: 8, 16 (the usual layout) or 32.
4. Read the Hex dump and the Bytes count. You can copy the dump or save it as dump.txt.

What it does and when to use it

Text that looks fine on screen can hide bytes that break things: a byte order mark, a tab where you expected spaces, a no-break space (c2 a0), a zero-width space (e2 80 8b), or a stray carriage return. A hex dump shows every byte, so these become obvious.

Developers use it to debug parsers, compare two strings that “look the same”, check what a Base64 value really contains, or confirm that a file uses the expected encoding and line endings. It is also a good way to learn how UTF-8 stores characters.

For a simple list of hex bytes without offsets, use Text to Hex. To convert Base64 straight to hex, use the Base64 to hex converter. To identify a single strange character by name, paste it into the Unicode character lookup.

How it works

1. The input becomes bytes: text as UTF-8, hex as written (spaces, colons, commas and 0x are allowed), or Base64 decoded (standard or URL-safe).
2. The bytes are cut into rows of the chosen width.
3. Each row shows the offset as 8 hex digits, two spaces, the bytes as lowercase hex with an extra space between the two halves, then the characters between bars. Bytes from 32 to 126 show as themselves; all others show as a dot.
4. A last line gives the total byte count as an offset.

This is the same layout as hexdump -C on Linux and macOS. It is built in your browser and nothing is uploaded.

Worked examples

Text “Hello, world” at 16 bytes per row:

00000000  48 65 6c 6c 6f 2c 20 77  6f 72 6c 64              |Hello, world|
0000000c

Hex input ef bb bf 48 69 0d 0a, a byte order mark, “Hi” and a Windows line ending:

00000000  ef bb bf 48 69 0d 0a                              |...Hi..|
00000007

Text with a tab, an accent, an emoji and CRLF, at 8 bytes per row:

00000000  54 61 62 09  68 65 72 65  |Tab.here|
00000008  2c 20 63 61  66 c3 a9 20  |, caf.. |
00000010  f0 9f 91 8b  0d 0a        |......|
00000016

The final offset 00000016 is hex for 22 bytes.

Limits and tips

• The dump is read-only; to change bytes, edit the hex and dump it again.
• Very large pastes make a long dump. Paste only the part you need to inspect.
• When pasting a dump back in as Hex, copy only the byte columns, not the offsets or the character column.