Hex dump (lite)

Client

Classic hex dump with offsets from UTF-8 text.

Hex dump layout

Offset, sixteen bytes per row, and ASCII gutter are for inspection— not a full hexdump -C clone with duplicate-line folding. Processing runs in your browser—Toolcore does not need your paste for the core operation on this page.

Byte semantics follow UTF-8 in the browser; verify wire format before shipping payloads.

How to use

Paste or type in the main field, then read the output below. Use Load example when available, or open the page with ?q= / ?qb= so tickets and agents share the same input.

Loading…

Nearby workflows on Toolcore

  • Hex dump text — Classic hex + ASCII dump of UTF-8 bytes. Useful when the payload needs another alphabet or escape.
  • Hex encode & decode — UTF-8 text to hex and hex to text—strip spaces, local only. Useful when the payload needs another alphabet or escape.
  • 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.
  • 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.

Common use cases

  • Hex dump (lite) for quick local checks without uploading data.
  • Copy results into tickets, docs, or classroom notes.

Common mistakes to avoid

  • Unexpected input shape

    See the intro and how-to notes for accepted formats.

FAQ

Is processing local?

Yes—this runs entirely in your browser.

Agent prefill?

Use q or qb for the main text field when supported.

More tools

Related utilities you can open in another tab—mostly client-side.