Base32 encode / decode
Encode and decode text to Base32 (RFC 4648, A-Z 2-7 alphabet).
- Instant
- Free
- Private (processed locally)
- No sign-up
Base32, readable and unambiguous
Toggle between encode and decode, enter your text or Base32, and copy the result. RFC 4648 compliant, ideal for TOTP secrets and hand-typed keys.
-
Choose the mode
Encode (text → Base32) or decode.
-
Enter
Text or a Base32 string.
-
Copy
The result copies in one click.
Examples (RFC 4648)
| Text | Base32 |
|---|---|
| f | MY====== |
| fo | MZXQ==== |
| foo | MZXW6=== |
| foobar | MZXW6YTBOI====== |
A-Z and 2-7 alphabet, “=” padding. Case-insensitive decoding, spaces ignored. Text processed as UTF-8, nothing is sent.
Frequently asked questions
What is Base32?
An encoding that represents binary data with 32 characters: the letters A-Z and digits 2-7 (RFC 4648). Unlike Base64, it avoids ambiguous characters and is case-insensitive, hence its use for hand-typed keys.
What is the “=” character for?
It is padding. Base32 works in blocks of 8 characters (40 bits); when data doesn’t fill a block, it is padded with “=”. Example: “foo” gives “MZXW6===”.
Where is Base32 used?
For TOTP/2FA secrets (Google Authenticator), some URL identifiers, DNS, or any system that must stay readable and case-insensitive. Decoding accepts lowercase and ignores spaces.
Is my data sent anywhere?
No. Encoding and decoding happen entirely in your browser; no data is transmitted. Text is processed as UTF-8.