Base32

Base32, like Base64, encodes binary data as text, but uses an alphabet of only 32 characters (A-Z2-7) with no easily confused characters (0/O, 1/I). That's why Base32 shows up more often where a string might be typed by a person, not just copy-pasted.

How to use it

• Encode: enter text or pick a file to get a Base32 string per RFC 4648.
• Decode: paste a Base32 string to get the original text or file back.
• The alphabet is case-insensitive per the spec, though uppercase is the conventional way to write it.

Common uses

• Generating secrets for TOTP/2FA — authenticator apps use Base32 for the secret key specifically.
• Encoding identifiers or tokens a user might need to type by hand without confusing similar-looking characters.
• Working with formats that require Base32 instead of Base64 (some DNS records or case-insensitive file systems, for instance).

Things to keep in mind

Base32 grows data by roughly 60% (versus ~33% for Base64) — a trade-off for broader compatibility with case-insensitive systems and manual entry.

Base32hex is a separate variant of the same standard with a different alphabet (0-9A-V) that preserves sort order — it's incompatible with plain Base32.