Micro Tools
Advertisement

Base32 Encoder

Encode text to Base32 or decode Base32 back to text, following RFC 4648 with padding. Base32 output uses only uppercase letters and digits 2 to 7.

Base32

Text to encode, or Base32 to decode.

Advertisement

How Base32 works

Base32 groups input bytes into 5-bit chunks and maps each chunk to one of 32 characters: A to Z and 2 to 7. Padding with = signs fills the final 8-character block. Because the alphabet avoids lowercase and the digits 0, 1, 8 and 9, Base32 is easy to read aloud and transcribe by hand.

Where Base32 is used

Base32 is the standard encoding for TOTP two-factor secrets, which is why authenticator app setup keys look like JBSWY3DPEHPK3PXP. It also appears in Tor onion addresses and some file sharing magnet links.

Related tools

JSON formatterFormat and validate JSON, privately. Regex testerTest regex live with highlighting. Base64 encoderBase64 encode and decode, plus URL encoder and JWT decoder.

Base32 Encoder FAQs

What is the difference between Base32 and Base64?
Base32 uses a 32-character uppercase alphabet and produces output about 60 percent larger than the input, while Base64 is more compact but case sensitive. Base32 wins when humans must read or type the value.
Is padding required?
RFC 4648 specifies = padding to a multiple of 8 characters, and this tool adds it. The decoder also accepts unpadded input, since many real world systems omit it.
Does it support Unicode text?
Yes. Input is encoded as UTF-8 bytes first, so emoji and non-Latin scripts round-trip correctly through encode and decode.
Can I decode a TOTP secret here?
You can decode the Base32 secret to raw bytes, but the output is binary and shown as text. For actual one-time codes, paste the secret into an authenticator app instead.
Is my text uploaded?
No. Encoding and decoding run entirely in your browser, so secrets and sensitive text never leave your device.
Advertisement