1001Ferramentas
🔢 Dev

Hexdump

View any text as a canonical hexdump (offset / hex bytes / ASCII), like Unix `hexdump -C`. Useful to inspect binary data, encoding and invisible separators. Everything in your browser.

Bytes: 0 · Linhas: 0

Quando usar?

Hexdump mostra cada byte do texto em hexadecimal lado a lado com sua representação ASCII. Útil para:

  • Detectar caracteres invisíveis (espaços não-quebráveis, marcas BOM, line endings).
  • Inspecionar encoding de UTF-8 vs Latin-1.
  • Analisar diferenças entre bytes que parecem iguais a olho nu.
  • Aprender encoding de caracteres e Unicode.

O formato segue o padrão do comando hexdump -C do Unix. Tudo no navegador.

See the bytes your editor hides

Two strings look identical but diff swears they differ; a CSV breaks the parser because of a space that is not a space; a script fails with a weird error on line one. The culprit is almost always an invisible byte: a BOM, a non-breaking space, CRLF where LF was expected. Paste the text here and see every byte in hex next to its ASCII column, in the same layout as Unix hexdump -C. Whatever is hiding shows up.

Input is encoded as UTF-8 before dumping, so accented characters take more than one byte: an 'a' with an acute accent becomes c3 a1, and an emoji can take four bytes. That is why the byte count rarely matches the character count. In the right-hand column, only printable bytes (0x20 to 0x7e) show as text; everything else becomes a dot. You can pick 8, 16, 24 or 32 bytes per line and a hex or decimal offset, handy when comparing against output from other tools.

A few patterns worth memorizing: ef bb bf at the start is a UTF-8 BOM; c2 a0 is the non-breaking space that sneaks in when you copy text from a web page; 0d 0a is a Windows line ending (CRLF), while Linux uses just 0a. The tool takes pasted text, not file uploads; to inspect a large binary, use hexdump -C or xxd in a terminal. All processing happens in your browser, and nothing you paste is sent to a server.

Frequently asked questions

Why does an accented letter show as two bytes?
Because the output uses UTF-8, where characters outside ASCII take 2 to 4 bytes. Each of those bytes shows up as a dot in the ASCII column.
Can I open a binary file?
Not directly: the input is a text box. For files, use hexdump -C or xxd in a terminal; this tool is for pasted text snippets.
How do I find an invisible character in my text?
Paste the suspicious part and look for bytes that do not match what you see: c2 a0 (non-breaking space), ef bb bf (BOM), 0d (CR) and 09 (tab) are the usual suspects.

Related Tools