Base32hex encode (lite)

Client

Base32hex encode UTF-8 bytes.

Base32hex encode

RFC 4648 base32hex (0-9A-V) for UTF-8 bytes—distinct from Crockford or standard base32 alphabet pages. Processing runs in your browser—Toolcore does not need your paste for the core operation on this page.

UTF-8 in the browser—verify wire format before shipping.

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

  • Base32 encode & decode — RFC 4648 Base32 for UTF-8 text—A–Z234567 alphabet with padding; encode or decode in the browser. Useful when the payload needs another 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 escape format.
  • Hex encode & decode — UTF-8 text to hex and hex to text—strip spaces, local only. Useful when the payload needs another escape format.
  • Base64 & URL encoder — UTF-8 Base64 encode/decode and URL component encode/decode in one workspace—paste, transform, copy. Useful when the payload needs another escape format.

Common use cases

  • Base32hex encode (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.