Hexdump viewer

What is a Hexdump Viewer?

A hex dump shows data byte by byte: an offset column, the bytes in hexadecimal and a printable ASCII representation. It is the classic way to see what a file or string really contains, including invisible characters that editors hide. This viewer renders text in the same layout as the Unix xxd and hexdump -C tools.

How to use it

  1. Paste or type text.
  2. Read the dump: offset, 16 bytes per row in hex and the ASCII column.
  3. Look for unexpected bytes.

Example

The text Hi there! followed by a Windows line break dumps as:

00000000: 4869 2074 6865 7265 210d 0a    Hi there!..

The 0d 0a at the end is CR LF; non-printable bytes are shown as dots in the ASCII column.

What hex dumps help you find

  • Byte order marks: EF BB BF at the start of a UTF-8 file can break CSV headers, shell scripts and JSON parsers.
  • Line ending problems: stray 0D bytes cause errors like bad interpreter when Windows files run on Linux.
  • Non-breaking spaces: C2 A0 looks like a space but is not, so string comparisons fail.
  • Zero-width characters: E2 80 8B is a zero-width space, invisible in editors but present in data copied from web pages.
  • Smart quotes: E2 80 9C and E2 80 9D instead of a plain quote.

Command-line equivalents

  • xxd file.txt
  • hexdump -C file.txt
  • Format-Hex file.txt in PowerShell

Frequently Asked Questions

What are the columns in a hex dump?

The offset of the first byte in the row, the bytes in hexadecimal, and their printable ASCII representation.

Why are some characters shown as dots?

Bytes that are not printable ASCII, such as line breaks and multi-byte UTF-8 sequences, are displayed as dots.

How do I spot a UTF-8 BOM?

Look for EF BB BF at offset 0.

Why does my script fail with bad interpreter?

The file probably has Windows CR LF line endings. A hex dump shows 0d 0a at the end of each line.