Question 1

What is the difference between Base32 and Base64?

Accepted Answer

Base64 uses 64 characters (A-Z, a-z, 0-9, +, /) and is more compact (~33% overhead vs ~60% for Base32). Base32 uses only 32 unambiguous uppercase characters (no l/1, 0/O confusion), making it better suited for human typing, case-insensitive systems and contexts that restrict the character set.

Question 2

Why does Base32 avoid the digits 0 and 1?

Accepted Answer

To prevent visual confusion between zero (0) and the letter O, and between one (1) and lowercase l or uppercase I. This makes Base32 safer for manual entry — for example in 2FA authentication keys and cryptocurrency wallet seeds.

Question 3

What is padding with '='?

Accepted Answer

Because Base32 works in 5-bit groups and bytes are 8 bits, the output size is not always a multiple of 8 characters. Padding with '=' fills the result to the next multiple of 8, making the size predictable. Some implementations omit padding to save space.

Question 4

Where is Base32 used in practice?

Accepted Answer

Base32 is widely used in: TOTP/HOTP (RFC 6238/4226) — the secret key in authenticators like Google Authenticator is Base32; Tor v3 .onion addresses; IPFS CIDv1 uses Base32; encoded DNS labels; and some Bitcoin wallet seed implementations.

Question 5

What is Base32hex?

Accepted Answer

Base32hex (RFC 4648 §7) uses the alphabet '0-9A-V' instead of 'A-Z2-7'. The advantage is that lexicographic ordering of Base32hex-encoded values matches the numeric ordering of the original values — useful for DNS, NSEC3 (DNSSEC) and any context where string ordering matters.

Question 6

How do 2FA authenticators use Base32?

Accepted Answer

In the TOTP protocol (RFC 6238), the server generates a binary secret key (usually 20 bytes) and encodes it in Base32 to present to the user as a readable alphanumeric code (e.g. JBSWY3DPEHPK3PXP). The authenticator app decodes that Base32 back to the original bytes and uses it as the HMAC key.

Question 7

What is the overhead of Base32?

Accepted Answer

Base32 has ~60% overhead compared to the original data: every 5 bytes produce 8 characters. By comparison, Base64 has ~33% overhead (3 bytes → 4 characters). For large data, Base64 is more space-efficient; Base32 is preferable when human readability or alphabet restrictions are more important.

Question 8

Is Base32 a form of encryption?

Accepted Answer

No. Base32 is an encoding, not encryption. Anyone can easily decode Base32 data back to the original — there is no key or secret involved. Use Base32 for data representation, not security. For data protection, use real cryptographic algorithms such as AES, ChaCha20 or RSA.

Base32 Encoder / Decoder

A binary-to-text encoding, case-resistant with a restricted alphabet

Real-time encoding and decoding

Sources and references for this tool

Frequently asked questions

A binary-to-text encoding, case-resistant with a restricted alphabet

Real-time encoding and decoding

Sources and references for this tool

Frequently asked questions

Related tools