Encoding
Encode text to Base32
Base32 Encode writes your text with the RFC 4648 alphabet, A–Z and the digits 2–7, regrouping the bytes into five-bit values and padding with = to a multiple of eight characters. Engineers use it to make test secrets for TOTP and HOTP two-factor keys and to get an uppercase encoding that survives copy-paste without case surprises. The text is converted to UTF-8 first, so any script encodes correctly, and hi becomes NBUQ====.
How to use Base32 Encode
- Open Base32 Encode in the Toolbox101 app.
- Type or paste the text you want encoded into the
Inputbox;hiis a good test. - Read the result in the
Outputbox: uppercase letters and the digits 2–7, with=padding at the end. - Click
Copyto put the Base32 string on your clipboard, for example to feed into Base32 Decode.
Worked example
Base32 Encode returns the output below for this input.
Input
hiOutput
NBUQ====Check it yourself: open Base32 Encode and enter the same input.
Frequently asked questions
What is Base32 used for in practice?
Base32 shows up wherever a printable, case-insensitive, compact encoding is wanted: TOTP two-factor secrets are shared as Base32, magnet links can carry Base32 file hashes, and some systems print IDs in Base32 so people can read them aloud without confusing O and 0. This tool encodes text to Base32; Base32 Decode reverses it.
Why does the output end with = signs?
Standard Base32 pads the output with = to a multiple of eight characters, so hi becomes NBUQ====. Decoders do not need the padding to read the value back, and the Base32 Decode tool here accepts it with or without, but RFC 4648 includes it and some libraries insist on it. If a service wants it unpadded, delete the trailing = signs.
Why does the alphabet skip digits 0, 1, 8, and 9?
The RFC 4648 alphabet keeps the digits 2–7 and leaves out 0 and 1 so they cannot be confused with the letters O and I (or l). Twenty-six uppercase letters plus those six digits give exactly 32 symbols at five bits each. Crockford Base32 is a different alphabet that drops other letters instead.
Is Base32 the same as Base64?
No. Base32 packs five bits per character from a 32-symbol alphabet; Base64 packs six bits per character from 64 symbols. Base32 output runs about 20 percent longer but stays uppercase and unambiguous when copied by hand, while Base64 needs lowercase letters, digits, and + or / symbols.
Use Base32 Encode now
Runs in your browser. Nothing you type is uploaded.