Base32 Encode
Encode text or binary data to RFC 4648 Base32 using UTF-8, UTF-16, Hex, Base64, and other input encodings. Expand to read more.
Encode text to Base32 online
Base32 represents binary data with a restricted alphabet of letters and digits. Enter text or encoded bytes, select how the input should be interpreted, and convert the resulting bytes to the standard RFC 4648 Base32 alphabet.
Base32 is an encoding, not encryption. Anyone can decode it without a key, so it should not be used to hide passwords, tokens, or confidential data.
How to encode Base32
- Enter text or an encoded byte sequence.
- Select UTF-8 for ordinary Unicode text, or choose Hex, Base64, UTF-16, or another encoding that matches the source.
- Click Encode.
- Copy the uppercase Base32 output, including
=padding when required by the receiving format.
For example, UTF-8 text abc encodes to MFRGG===. The visible input encoding matters because Base32 operates on bytes rather than characters.
Base32 alphabet and padding
RFC 4648 Base32 uses A–Z and digits 2–7, with each character representing five bits. Digits 0 and 1 are omitted to reduce confusion with letters in human-entered values.
Output is grouped conceptually in blocks of eight characters. The final block may use = padding when the input does not fill a complete 40-bit group. Some protocols omit padding, so follow the exact convention required by the system receiving the value.
Base32 encoding FAQ
Why is Base32 longer than Base64?
Each Base32 character carries five bits, while each Base64 character carries six. Base32 therefore produces longer text but uses a more restricted alphabet.
Does Base32 preserve letter case in the original text?
Yes, because case is encoded in the original bytes. The encoded Base32 output itself conventionally uses uppercase characters.
How do I recover the original data?
Use the Base32 Decode tool. To encode a local file or URL without first converting it to text, use Encode File to Base32.