How is Base32hex different from standard Base32?

Both pack 5 bits per character, but Base32hex uses the alphabet 0 to 9 followed by A to V, whereas standard Base32 uses A to Z then 2 to 7. The hex variant is chosen so that encoded strings keep the same sort order as the binary data they represent.

Why does sort order matter?

Because the alphabet is in ascending byte-value order, sorting the encoded text gives the same sequence as sorting the original bytes. Systems that store or compare encoded keys, such as DNSSEC NSEC3 hashes, depend on this property to walk records in order.

Where is Base32hex actually used?

Its best-known use is DNSSEC NSEC3 records, where ordered hashes of domain names prove that a name does not exist. It also appears in some identifier schemes that want case-insensitive, sortable, URL-safe tokens.

Is the padding the same as standard Base32?

Yes. The equals sign pads the output to a multiple of 8 characters and carries no data. Decoding ignores padding and whitespace, so you can paste wrapped or padded strings directly.

What happens with invalid input when decoding?

Any character outside the 0 to V alphabet is rejected and the tool names the offending character. Because the alphabet stops at V, letters W through Z are invalid here even though they are valid in standard Base32.

Base32Hex Encoder and Decoder

Base32hex is the extended-hex variant of Base32 from RFC 4648. It encodes the same 5-bits-per-character data, but with an alphabet that preserves sort order, which makes it the format behind DNSSEC NSEC3 records and similar order-sensitive keys.

How it works

Encoding is identical to standard Base32 except for the symbol table. Bytes are read as a bit stream and chopped into 5-bit groups, each mapped through the extended-hex alphabet:

alphabet = 0123456789ABCDEFGHIJKLMNOPQRSTUV   (index 0..31)
emit one character per 5 bits, zero-fill the last group
pad with '=' to a multiple of 8 characters (optional)

Because index 0 maps to 0 and the values climb monotonically through the digits and then the letters, the lexical order of two encoded strings matches the numeric order of the bytes they encode.

Example and tips

The text Gera Tools encodes to 8TIN4O90AHNMUR3J in Base32hex (compare the standard-Base32 result, which uses a different alphabet). Reach for Base32hex specifically when you need encoded values to sort correctly as plain text; for a general-purpose, widely-supported encoding, standard Base32 is the safer default because more libraries decode it out of the box.