Base32 Encoder / Decoder
Encode text to Base32 or decode Base32 back to text (RFC 4648). Nothing is uploaded - everything runs locally.
How Base32 encoding works
Base32 rewrites binary data using 32 symbols so it survives systems that only expect letters and digits. This tool follows RFC 4648: each character carries five bits, the alphabet is A-Z plus 2-7, and the output is padded with = to a multiple of eight characters. Your text is first converted to UTF-8 bytes, so non-ASCII characters round-trip correctly. A quick check is the acceptance vector abc to MFRGG===. For everyday text handling see the text case converter, or compare notation styles on the all tools page.
Frequently asked questions
Is Base32 the same as encryption?
No. Base32 is an encoding that only changes how bytes are written, and anyone can decode it. Use it for transport or compatibility, never to protect a secret.
Which alphabet and padding does it use?
The RFC 4648 standard alphabet: letters A to Z and digits 2 to 7, five bits per character, with = padding to a multiple of eight characters. Digits 0 and 1 are not used.
Why does "abc" become MFRGG===?
Those three UTF-8 bytes are 24 bits, which split into five-bit groups and map to M, F, R, G and G; the remaining five characters are = padding.
Does it handle non-ASCII text?
Yes. Text is first turned into UTF-8 bytes and then encoded, and decoding returns UTF-8 text, so accented letters and emoji survive a round trip.
Is decoding case-sensitive?
No. Lowercase letters are accepted, whitespace is ignored and trailing padding is optional, so values copied from other tools usually decode directly.
What happens with an invalid character?
Decoding stops and reports the offending character and its position, rather than returning silently corrupted output.
Related: adjust text with the text case converter, sort values with the line sorter, format related JSON with the JSON formatter, count words with the word counter, and browse every browser-only tool on the all tools page.