Hex Dump Viewer renders text or a whole file as a classic byte-by-byte dump: an 8-digit offset, space-separated hex byte pairs, and a matching ASCII column where non-printable bytes show as a dot. Type text directly or drop in any file, then switch the row width between 8, 16, and 32 bytes and toggle uppercase hex digits to match the format you need. It is the same layout tools like xxd and hexdump -C produce, so the output is instantly familiar for inspecting file headers, debugging binary protocols, checking magic bytes, or verifying exactly what bytes an encoding actually produced. Built for developers, reverse engineers, and anyone who needs to see the raw bytes behind a string or file. The dump is generated entirely in your browser — nothing you type or upload leaves your device.
Features
Dumps typed text or an uploaded file as hex + ASCII, side by side
Classic 8-digit offset, hex byte pairs, and a |ascii| column layout
Adjustable row width: 8, 16, or 32 bytes per line
Toggle uppercase or lowercase hex digits
Non-printable bytes render as '.' in the ASCII column, just like xxd
Copy the full hex dump output with one click
Handles any file type, not just text — images, binaries, archives
Runs entirely in your browser, so nothing is uploaded to a server
How to use the Hex Dump Viewer
Type or paste text into the input, or choose a file to load its bytes
Pick a row width of 8, 16, or 32 bytes per line
Toggle uppercase hex digits if you prefer A–F over a–f
Copy the hex dump output to paste into a bug report or terminal
Example
Input
Hi!
Output
00000000 48 69 21 |Hi!|
Each byte of "Hi!" shown as hex, with the printable ASCII column on the right.
Common errors & troubleshooting
The hex dump output looks misaligned compared to another tool's output. — Row width changes the column layout — set the width to 16 to match the common hexdump -C / xxd default, or match whatever width the other tool used.
A large file feels slow to dump. — Very large files produce very long output. Try a smaller sample of the file, or increase the row width to reduce the number of lines rendered.
The ASCII column shows dots instead of the characters you expect. — Bytes outside the printable range (0x20–0x7E) always render as '.' in the Hex Dump Viewer — this includes control characters, newlines, and most non-ASCII text bytes.
Pasted text does not match the file's original bytes. — Typed text is encoded as UTF-8 before dumping, so multi-byte characters produce more than one byte. Upload the original file instead if you need the exact source bytes.
Frequently asked questions
What does the Hex Dump Viewer actually show?
It shows the raw bytes of your text or file in the classic hex-dump layout: an 8-digit offset, each byte as two hex digits, and an ASCII column on the right where unprintable bytes are shown as a dot.
Can the Hex Dump Viewer read a whole file, not just typed text?
Yes. Choose any file and the Hex Dump Viewer reads its raw bytes with FileReader and dumps them the same way as typed text — images, binaries, and archives all work.
How is the Hex Dump Viewer different from xxd or hexdump -C?
It produces the same familiar layout — offset, hex bytes, ASCII column — directly in your browser, so you get an xxd-style dump without opening a terminal.
What row widths does the Hex Dump Viewer support?
You can switch between 8, 16, and 32 bytes per line. 16 matches the common hexdump -C default; narrower or wider rows can make specific byte ranges easier to scan.
Does the Hex Dump Viewer upload my text or file anywhere?
No. The Hex Dump Viewer runs entirely in your browser. Text you type and files you choose are processed locally and never uploaded to ArrayKit.
Why do non-printable bytes show as a dot in the hex dump?
Bytes below 0x20 or above 0x7E have no printable ASCII character, so the Hex Dump Viewer renders them as '.' in the ASCII column, matching the convention used by xxd and hexdump -C.
Related tools
Text to Binary Converter — Convert text to binary, and binary, hex or decimal back to text, in your browser.