Base32 Encoder / Decoder
Encode or decode text and binary data using Base32 (RFC 4648). Client-side, instant, no sign-up.
Base32 Encoder / Decoder
Encode UTF-8 text to Base32 (RFC 4648) or decode Base32 back to plain text. Base32 uses only uppercase letters and digits 2–7, making it safe for case-insensitive systems.
Input
Output
Output will appear here…FAQ
What is Base32 used for?▼
Base32 is used in TOTP (two-factor authentication secret keys), IPFS content identifiers (CIDv1), Onion addresses in Tor, and anywhere case-insensitive encoded data is needed.
Is Base32 the same as Base64?▼
No. Both are binary-to-text encodings, but Base32 uses 32 characters (A-Z, 2-7) while Base64 uses 64. Base32 is 20% less efficient but handles case-insensitive environments better.
Does this support non-ASCII characters?▼
Yes. Input text is first converted to UTF-8 bytes, then Base32-encoded. Decoding reconstructs the original UTF-8 string.
Frequently Asked Questions
What is Base32?
Base32 is a binary-to-text encoding scheme using 32 ASCII characters (A–Z and 2–7), defined in RFC 4648. It is more human-readable than Base64 and safe in case-insensitive file systems.
When is Base32 used?
Base32 is used in TOTP/HOTP codes (Google Authenticator), Crockford encoding, and case-insensitive file systems. Its alphabet avoids visually ambiguous characters like 0, 1, O, and I.
Is Base32 the same as Base64?
No. Base32 uses a 32-character alphabet producing ~20% more overhead than Base64, but it is safe in case-insensitive contexts and avoids special characters like + and /.