How to use Base32 Encoder / Decoder
- 1
Select Encode or Decode mode.
- 2
Paste your text or Base32 string.
- 3
Copy the converted output.
Encode text to Base32 or decode Base32 strings back to plain text. Uses RFC 4648 standard. Perfect for users needing a base 32 decoder.
Select Encode or Decode mode.
Paste your text or Base32 string.
Copy the converted output.
It is commonly used for two-factor authentication (2FA) shared secrets, as it avoids ambiguous characters like 1, l, 0, and O.
Base32 is a way to represent arbitrary binary data using only 32 printable characters: the uppercase letters A–Z and the digits 2–7.
You're probably more familiar with Base64, which uses 64 characters (A–Z, a–z, 0–9, +, /). So why would you want a smaller alphabet with fewer characters?
Because Base32 makes fewer assumptions about the environment it's used in.
Base64's characters include +, /, and =, which have special meanings in URLs, file systems, and programming languages. You need to use URL-safe variants of Base64 fairly often. Base32's alphabet — only uppercase letters and digits — has no special meaning in virtually any context. It's case-insensitive too, which means JBSWY3DP and jbswy3dp decode to the same thing.
Every Base32 character represents exactly 5 bits of binary data (because 2⁵ = 32). To encode, you:
Since bytes are 8 bits, encoding 5 bytes (40 bits) requires exactly 8 Base32 characters (40 ÷ 5 = 8). When the input isn't a multiple of 5 bytes, padding characters (=) are added to reach a multiple of 8 output characters.
Example: Encoding the word Man:
M a n
77 97 110 (ASCII decimal)
01001101 01100001 01101110 (binary)
Combined: 010011010110000101101110
Grouped: 01001 10101 10000 10110 1110
As Base32: J V Q W 4
Result: JVQW4 (with padding: JVQW4===)
| Factor | Base32 | Base64 |
|---|---|---|
| Characters used | A-Z, 2-7 | A-Z, a-z, 0-9, +, / |
| Case sensitive? | No | Yes |
| URL safe by default? | Yes | No (needs variant) |
| Efficiency | 80% of raw size | 75% overhead vs raw |
| Common uses | OTP, checksums, DNS | Email attachments, JSON/HTTP |
Choose Base32 when:
Choose Base64 when:
If you've ever set up two-factor authentication (2FA) and scanned a QR code, or seen a st...
Looking for a more detailed deep-dive and advanced tips?
Read Full Article on our BlogYour data never leaves this device. All processing is handled locally by JavaScript.
Encode text to RFC 4648 Base32 format or decode it back to plain text.