Base32 Encoder

Base32 encoding is one of those technical concepts that's useful to understand even if you don't encounter it daily. Unlike Base64 — which is far more common — Base32 uses a 32-character alphabet (A through Z, then 2 through 7) and is specifically designed to be human-readable, case-insensitive, and safe to use in contexts where certain characters could cause problems.

What is Base32 used for? It shows up in several real-world scenarios. Two-factor authentication (2FA) apps like Google Authenticator and Authy store secret keys in Base32 format — that long string of letters and numbers you sometimes see when setting up TOTP is a Base32-encoded secret. It's also used in DNS records, some file systems, and data encoding scenarios where uppercase-only output is required.

Why Base32 instead of Base64? Base64 uses both upper and lowercase letters plus + and / which can cause issues in URLs, filenames, and case-insensitive systems. Base32's alphabet is purely uppercase alphanumeric, which makes it more portable. The trade-off is efficiency — Base32 produces about 60% more output than the original input, compared to Base64's 33% overhead.

This tool follows RFC 4648, which is the standard Base32 encoding specification. It uses the standard alphabet and pads output with = characters to ensure the encoded string length is always a multiple of 8.

The encoding is done entirely in your browser using the Web Encoding API — nothing is sent to a server, and the output updates live as you type. Pair this with our Base32 Decoder if you need to go the other direction.