Base32 vs Base32hex

Base32 and Base32hex are both 5-bit encodings defined by RFC 4648 but they use different alphabets. As a result, strings produced by a Base32 encoder will not decode correctly with a Base32hex decoder and vice versa. Choose the variant your ecosystem expects: Base32 is common for OTP secret keys, while Base32hex may appear in some interoperability profiles.

If you control both ends, standardize on one alphabet and document it. When consuming external data, inspect the alphabet and attempt the correct decoder. Our tools can help: Base32 and Base32hex.

Related tools

Try: Base32, Base32hex, Base64

FAQ

What is the difference between the alphabets?

Base32 uses A–Z and 2–7; Base32hex uses 0–9 and A–V. The mapping of symbols to values differs, so decoders are not interchangeable.

Do both variants use padding?

Per RFC 4648, padding with = is optional for both. Many modern APIs accept unpadded input.