Result
Free Base32 Encoder & Decoder
Convert text to and from Base32 encoding
Our free Base32 Encoder & Decoder converts text to Base32 encoded format and back. Base32 encoding represents binary data using a 32-character alphabet (A-Z and 2-7), making it human-readable and suitable for case-insensitive systems. All encoding and decoding happens instantly in your browser — no data is ever sent to a server.
📋 What is Base32 Encoding?
Base32 is a binary-to-text encoding scheme defined in RFC 4648 that represents binary data using an alphabet of 32 characters: uppercase letters A through Z and digits 2 through 7. Unlike Base64, Base32 uses only uppercase letters and digits, making it case-insensitive and human-friendly. Each Base32 character represents 5 bits of data, resulting in approximately 60% size expansion. Base32 is commonly used in TOTP (Time-based One-Time Passwords), secret keys for two-factor authentication (Google Authenticator), DNS records, and other systems where case sensitivity could cause issues.
🛠️ How to Use the Base32 Tool
- 1 Select 'Encode to Base32' or 'Decode from Base32' tab depending on your task.
- 2 For encoding: Enter the plain text you want to convert to Base32 in the input area.
- 3 For decoding: Paste the Base32 encoded string (characters A-Z, 2-7, and = padding).
- 4 Click the corresponding button to process the conversion instantly.
- 5 Copy the result with the 'Copy Result' button to use in your application.
✨ Key Features
Instant Conversion
Encode and decode Base32 data in real-time. No file size limits, no waiting — instant results for any input length.
Complete Privacy
All encoding and decoding runs entirely in your browser using JavaScript. Your data never leaves your device.
Simple Interface
Clean, intuitive design with separate encode and decode tabs. Paste your data, click convert, and copy the result.
🎯 Common Use Cases
🔐 Two-Factor Authentication
Base32 is the standard encoding for TOTP secret keys used in Google Authenticator, Authy, and other 2FA apps. Encode and decode TOTP secrets for authentication system development.
🌐 DNS & Network Protocols
Base32 encoding is used in DNSSEC, DNS-based authentication systems, and protocols that require case-insensitive data representation in URLs and domain names.
🔑 Secret Key Encoding
Encode cryptographic keys and secrets in Base32 format for easy sharing and storage. Base32's human-readable format reduces transcription errors compared to hex or Base64.
👩💻 Development & Testing
Encode and decode Base32 data during development. Useful for debugging TOTP implementations, testing encoded parameters, and working with APIs that use Base32.
💡 Base32 Best Practices
- Use Base32 instead of Base64 when case sensitivity could be an issue — Base32 uses only uppercase letters and digits.
- Remember that Base32 encoding increases data size by approximately 60% (8 output characters for every 5 input bytes).
- Base32 padding (=) can be removed for URL-safe applications — the decoder can infer padding from the string length.
- For TOTP secrets, always use Base32 encoding as specified by RFC 6238 and Google Authenticator.
- Don't confuse Base32 with Base64 — they are different encoding schemes with different alphabets and use cases.
- Base32 is an encoding, not encryption. It does not provide data security — anyone can decode Base32 text.
❓ Frequently Asked Questions
What's the difference between Base32 and Base64?
Base32 uses a 32-character alphabet (A-Z, 2-7) and is case-insensitive with ~60% size increase. Base64 uses a 64-character alphabet (A-Z, a-z, 0-9, +, /) and is case-sensitive with ~33% size increase. Base32 is human-friendlier and works in case-insensitive systems, while Base64 is more space-efficient.
Why is Base32 used for TOTP/2FA?
Base32 is used for TOTP secret keys because it's case-insensitive (users can enter it in any case), human-readable (no confusing characters like 0/O or 1/l), and compact enough for manual entry. The RFC 6238 TOTP standard specifies Base32 encoding for shared secrets.
Is Base32 encoding secure?
No, Base32 is an encoding scheme, not encryption. Anyone who has a Base32 string can decode it back to the original data. If you need to protect data, use encryption (AES, RSA) before encoding with Base32. Base32 is only used for data representation, not data protection.
Can I encode binary files with Base32?
This tool is designed for text-to-Base32 conversion. For binary file encoding, you would need a tool that can read binary data and apply Base32 encoding to the raw bytes. However, this tool correctly handles UTF-8 text encoding to Base32.
What characters are valid in Base32?
Base32 uses exactly 32 characters: uppercase letters A through Z (26 characters) and digits 2 through 7 (6 characters). The = character is used for padding. Digits 0, 1, 8, and 9 are intentionally excluded to avoid confusion with letters O, I/L, B, and G.