Base32 Encode and Decode Online

This Base32 encoder and decoder converts ordinary Unicode text using the standard RFC 4648 alphabet of uppercase letters A through Z and digits 2 through 7. Select encode to turn UTF-8 text into portable Base32 with standard padding, or select decode to recover the original text. Decode mode validates the alphabet, padding, length, unused trailing bits, and UTF-8 result instead of silently producing damaged content.

How RFC 4648 Base32 represents text

Base32 is a binary-to-text encoding: it does not encrypt, compress, or hide information. In encode mode, the converter first represents the supplied string as UTF-8 bytes. It then reads those bytes as one continuous bit stream and divides the stream into groups of five bits.

Each five-bit value selects one symbol from the RFC 4648 alphabet, which contains the uppercase letters A through Z followed by the digits 2 through 7. Because five input bytes contain forty bits, they map exactly to eight Base32 symbols. When the final block is shorter, zero bits complete the last symbol and equals signs pad the result to an eight-character boundary.

That padding makes complete blocks easy for other implementations to recognize. The converter always emits the standard alphabet and canonical padding, so its output can be compared directly with RFC-compatible libraries in common programming languages. Unicode is handled before the bit conversion, which means accented letters, non-Latin scripts, and emoji have stable byte representations rather than being truncated to legacy character values.

Identical input and mode always produce identical output.

Decode validation and error behavior

Decode mode treats its input as RFC 4648 Base32 rather than as a loosely similar token. Letters may be uppercase or lowercase, but every data symbol must belong to A through Z or 2 through 7. An equals sign is accepted only as final padding, and its count must agree with the number of data symbols in the last block.

Lengths that cannot represent a whole number of bytes are rejected. The converter also checks unused trailing bits: RFC-compliant encoders set them to zero, while accepting nonzero bits could allow multiple spellings of the same byte sequence. After bytes are recovered, a strict UTF-8 decoder verifies that they form text, because this capability promises a string result rather than an arbitrary binary file.

Any invalid character, misplaced padding mark, impossible length, nonzero trailing bits, or malformed UTF-8 sequence returns an invalid-input error instead of partial output. Correct unpadded Base32 is also accepted when its final length is structurally valid.

Using the converter in tools and automated workflows

For a quick conversion, provide the text and choose encode or decode. Encode mode returns a padded Base32 string in the output field; decode mode returns the recovered Unicode string in that same field. Base32 is useful when a value must travel through systems that handle a limited character set, including provisioning records, human-readable setup material, case-insensitive stores, and text-only configuration.

It is commonly encountered around authenticator secrets, though encoding a secret does not protect it and access controls remain necessary. The algorithm uses no network, randomness, clock, account state, or external service, so it is suitable for repeatable builds and tests.