Hex dump text

Nearby workflows on Toolcore

• Octal encode bytes — Show UTF-8 bytes as octal triplets. Useful when the payload needs another alphabet or escape format.
• File hex viewer — Hex dump the first 256 KB of any file with ASCII sidebar—read locally, no upload. Useful when the payload needs another alphabet or escape format.
• Base16 / hex encode — Uppercase hexadecimal encoding of UTF-8 text. Useful when the payload needs another alphabet or escape format.
• Encoding tools — Hub index: Base64 & URL, Base64url, Base32, Crockford, LEB128, ASCII85, Z85, Base58, base-36, bencode, Morse, quoted-printable, URI, Punycode/IDN, Unicode escapes, data URLs, MIME, hex, HTML entities, JWT, JSON helpers, crypto. Useful when the payload needs another alphabet or escape format.

Common use cases

• Transform sample text with hex dump text while debugging legacy email, Usenet, or protocol payloads.
• Compare output size and alphabet against Base64, Z85, or hex dumps on the same input without leaving the encoding hub.
• xxd-style dump for debugging encodings.
• When the payload also needs a sibling encoding, open the related encoding-octal page from More tools below.

Common mistakes to avoid

• Treating UTF-8 paste as raw binary

  These tools encode the UTF-8 bytes of your text unless the page states otherwise. For arbitrary byte arrays, convert from hex first.

• Mixing alphabets between encodings

  Base91, Z85, uuencode, and Base64 use different symbol sets—decode with the matching tool before re-encoding.

• Pasting secrets into shareable prefill links

  URL query parameters may appear in browser history. Use Load example for demos; avoid ?q= links for production keys.

FAQ