Base32 Encoder / Decoder
Convert text to and from Base32 with the RFC 4648 alphabet, optional = padding stripped, and full UTF-8 support.
How to Use
- Choose a mode
Encode converts text to Base32; decode goes the other way. The input stays put when you switch, which makes reverse verification quick.
- Fill in and read out
Encoding lets you keep or strip = padding; decoding ignores spaces, newlines and padding so multi-line content pastes cleanly.
- Feed back or copy
Click 'Output → input' for an immediate round-trip check, then 'Copy output' to take the result.
FAQ
Base32 or Base64?
Base64 is shorter (about 33% overhead) versus roughly 60% for Base32. But Base32 uses only uppercase letters plus 2–7, with no confusable 0/O or 1/I/l, which suits hand-copied codes, case-insensitive storage and TOTP secrets.
What are the trailing equals signs?
Padding that rounds the total length up to a multiple of 8. It carries no data and decoding works without it, though strict validators check the multiple.
Why does Chinese expand so much?
A Chinese character takes 3 bytes in UTF-8, and Base32 turns every 5 bytes into 8 characters — roughly a 4.8× expansion. That is the encoding's own overhead, not a tool defect.
What if the decoded output is garbled?
It means the original bytes were not UTF-8 text — binary or another charset. The tool says so and switches to hex, so what you see is the real byte sequence rather than mojibake.