Base32 Encoder and Decoder
Encode text to Base32 and decode it back in real time, using the RFC 4648 alphabet. Text is handled as UTF-8 bytes, so non-ASCII characters round-trip correctly.
FreeOnline Tool
Loading…
How to Use
- Type any text into the left "Plain text" box and the encoded Base32 appears on the right instantly.
- It works in reverse too: paste a Base32 string into the right box and the decoded text appears on the left.
- Press "Copy right side" to copy the current Base32 result.
Features
- Base32 encoding and decoding using the standard RFC 4648 alphabet (A-Z plus the digits 2-7)
- Live two-way conversion between the two panes, with "Encode" and "Decode" buttons available for manual triggering
- Encoded output is padded with "=" characters automatically
- Text is converted to UTF-8 bytes internally, so Chinese and other non-ASCII characters encode and decode correctly
- One-click copy of the Base32 result
Use Cases
TOTP and 2FA secrets
Most one-time-password tools store their shared secret in Base32, so use this to inspect or convert those key strings.
Case-insensitive transport
Move encoded text or binary data through systems that cannot preserve case or handle special symbols.
Verifying your own implementation
Compare the output of your own Base32 encoder or decoder against a reference result.
Learning how Base32 works
Watch text turn into Base32 and back to understand the alphabet and the padding rules.
FAQ
How is Base32 different from Base64?
Base32 uses only 26 letters plus the digits 2-7, so it is case insensitive and safe in systems that mangle case, at the cost of slightly larger output. Base64 is more compact but is case sensitive and includes symbols such as + and /.
Does it support Chinese and other non-ASCII text?
Yes. The text is first encoded as UTF-8 bytes and then converted to Base32, so Chinese characters, emoji and similar content encode and decode back correctly.
What happens if decoding fails?
If the string cannot be parsed, the left box shows a "decode failed" message. Check that the Base32 string is complete and contains only valid characters.
Why does the encoded output end with "="?
"=" is the Base32 padding character, used to bring the encoded length up to a multiple of 8. It is part of the RFC 4648 standard.