Hex Dump Viewer
The exact bytes behind your text — offset, hex and ASCII columns, like hexdump -C. Invisible characters have nowhere to hide.
Reading the dump
Each row shows 16 bytes: the offset (position in hex), the hex values of each byte, and the ASCII column where printable bytes show as characters and everything else as a dot. Multi-byte UTF-8 sequences — accents, em dashes, emoji — appear as 2–4 bytes with dots.
Frequently asked questions
What bugs does a hex dump catch?
The classics: a UTF-8 BOM (ef bb bf) breaking a config parser, smart quotes (e2 80 9c) pasted from a document into code, non-breaking spaces (c2 a0) that look like spaces but aren't, and Windows line endings (0d 0a) where 0a was expected.
Why does one character show as several bytes?
UTF-8 encodes anything beyond ASCII as 2–4 bytes: é is c3 a9, the em dash is e2 80 94, and most emoji are 4 bytes. What looks like 15 characters can easily be 20+ bytes.
Can I dump a file?
This tool inspects pasted text. For binary files use hexdump -C file (macOS/Linux) or Format-Hex file (PowerShell) — the output format matches what you see here.
Last updated: 2026-07-13