Encoding Tools

Base32hex

Extended Hex alphabet encoder/decoder. Uses RFC 4648 "Extended Hex" alphabet: 0123456789ABCDEFGHIJKLMNOPQRSTUV.

0 chars
OUTPUT
0
Input Bytes
0
Output Chars
0
Padding Chars

How to use this tool

  1. Pick Encode or Decode using the tabs at the top of the tool.
  2. Type or paste your input in the box — the output updates live as you type.
  3. Click Copy Output to copy the result to your clipboard.
  4. Read the stats — Input Bytes, Output Chars, and Padding Chars show what is happening under the hood.
  5. Use Clear any time to reset the input.

Why this tool is helpful

RFC 4648 "Extended Hex" alphabet

Uses 0–9 A–V (instead of the standard A–Z 2–7), so encoded strings sort in natural hex-like order.

Case-insensitive

Input is uppercased automatically, so output round-trips cleanly through case-folding systems.

Hex-adjacent ordering

Digit-first ordering is handy in contexts that expect identifiers to sort numerically.

Contrast with standard Base32

See how the exact same 5-bits-per-character algorithm behaves with a different alphabet.

Understand padding

The stats reveal how = padding brings output to a multiple of 8 characters.

Stay private

Everything runs in your browser. Nothing is uploaded, logged, or sent to a server.

FAQ

What alphabet does Base32hex use?

The RFC 4648 "Extended Hex" alphabet: 0–9 then A–V (32 characters total), uppercase only.

How is it different from standard Base32?

Standard Base32 uses A–Z 2–7, while Extended Hex uses 0–9 A–V so the alphabet keeps a hex-style ordering.

What does the = padding do?

It pads the output to a multiple of 8 characters so groups of 5 input bytes map cleanly onto 8 output characters.

Is it case-sensitive?

No. Input is uppercased automatically and only 0–9 A–V are used.

Can it handle Unicode, like emoji?

Yes. Text is encoded as UTF-8 before conversion, and decoding reverses back to the original text.

Does any of my data leave my browser?

Never. All conversion happens locally in JavaScript.