Base32 Encode and Decode

The standard RFC 4648 alphabet: the uppercase letters A to Z and the digits 2 to 7, with = used only for padding. It deliberately leaves out 0, 1, 8 and 9 to avoid confusion with the letters O, I and B.

Base32 packs data into groups of 40 bits, or eight characters. When your input does not fill the last group, the encoder pads the output with = so its length is always a multiple of eight, exactly as RFC 4648 specifies.

Base32 encodes five bits per character, so output is roughly 1.6 times the size of the raw bytes, before padding. That is larger than Base64, which fits six bits per character, but Base32 is easier for people to read aloud and type.

Yes. Text is converted to UTF-8 bytes before encoding, so accented characters, non-Latin scripts and emoji all round-trip correctly when you decode the result.

The canonical alphabet is uppercase. This tool outputs uppercase and expects uppercase on decode, so lowercase letters are treated as invalid characters rather than silently accepted.

Decoding rejects any character outside A to Z and 2 to 7 (the padding = is ignored). A stray space, a lowercase letter, or a digit like 0 or 1 will stop it. Remove the invalid characters and try again.

No. Base32 is an encoding, not encryption. Anyone can decode it, so it protects nothing on its own. It exists to move data safely through text-only channels, not to keep it secret.

Yes. Encoding and decoding happen locally in your browser and nothing is uploaded, so even secret keys you encode stay on your device.