Base32 Encoder & Decoder
Encode text to Base32 or decode Base32 back to text. Supports RFC 4648 standard and Base32hex. 100% client-side — your data never leaves your browser.
0 chars
0 chars
🔒 100% private: All encoding and decoding happens in your browser. Your data never leaves your device.
About Base32 Encoder & Decoder
Base32 is a binary-to-text encoding scheme that uses 32 ASCII characters to represent binary data. It was defined in RFC 4648 as an alternative to Base64. The main advantage of Base32 is its case-insensitivity — all letters are uppercase, which makes it safer for systems that mangle case (like DNS, some filesystems, or human transcription). It also avoids characters that look similar (like l/1/I), which is why it is used for TOTP secrets (Google Authenticator), some 2FA systems, DNS SRV records, and Tor onion addresses. This tool encodes any text to Base32 or decodes Base32 strings back to readable text, supporting both standard Base32 (A-Z, 2-7) and Base32hex (0-9, A-V).
How It Works
- Paste or type your text in the input box to encode, or paste a Base32 string to decode.
- Click "Encode to Base32" to convert text → Base32, or "Decode from Base32" to convert Base32 → text.
- Choose a variant: Standard (RFC 4648) or Base32hex.
- Toggle padding (=) — most systems require it, but some omit it.
- The result appears instantly — copy it with one click.
✨ Key Features
- ✓Encode any text to Base32 format
- ✓Decode Base32 strings back to readable text
- ✓Standard Base32 (RFC 4648) — A-Z, 2-7
- ✓Base32hex variant — 0-9, A-V
- ✓Optional padding (=) — configurable
- ✓Case-insensitive input handling
- ✓Handles Unicode and multi-byte characters correctly
- ✓Live character counter for input and output
- ✓Instant error detection for invalid Base32
- ✓100% client-side — no data sent to any server
🎯 Common Use Cases
- →Generating or decoding TOTP (Google Authenticator) secrets
- →Working with DNS SRV records and NSEC3 hashes
- →Creating human-transcribable tokens (case-insensitive)
- →Encoding binary data for systems requiring Base32
- →Decoding Base32-encoded keys from authentication apps
- →Working with Tor .onion addresses (Base32 encoded)
- →Encoding data for some legacy email and MIME systems
- →Testing Base32 implementations during development
💡 Advanced Tips & Pro Insights
- ▸Base32 is case-insensitive — the output is always uppercase. Some implementations accept lowercase input, which this tool handles.
- ▸TOTP secrets (2FA codes) are commonly Base32-encoded without padding. The 32-character alphabet avoids letters that look like digits (no l, I, O, 0).
- ▸Base32 is 60% less efficient than Base64 (5 bytes → 8 chars, vs 3 bytes → 4 chars), but is safer for human transcription and case-insensitive systems.
- ▸The padding character "=" is required by strict RFC 4648 but often omitted in real-world usage (e.g., TOTP secrets). This tool lets you toggle padding.
- ▸Base32hex is designed so that sorting Base32hex-encoded strings preserves the sorting of the original binary data — useful for canonical representation.
Frequently Asked Questions
Is this Base32 encoder free?▾
Yes, this Base32 encoder and decoder is completely free with no signup, registration, or usage limits.
Is my data safe?▾
Yes, 100% safe. All encoding and decoding happens in your browser. Your data never leaves your device.
What is Base32?▾
Base32 is a binary-to-text encoding that represents data using 32 ASCII characters (A-Z and 2-7 in standard Base32). It is case-insensitive and avoids visually similar characters, making it ideal for human-transcribable data and case-insensitive systems.
What is the difference between Base32 and Base64?▾
Base32 uses 32 characters (5 bits per char) and is case-insensitive, producing longer output (60% larger). Base64 uses 64 characters (6 bits per char) and is more compact but case-sensitive. Base32 is safer for human transcription and case-insensitive systems.
What is Base32hex?▾
Base32hex is a variant defined in RFC 4648 that uses digits 0-9 and letters A-V (instead of A-Z and 2-7). It has the property that sorting Base32hex-encoded strings preserves the sort order of the underlying binary data — useful for canonical formats.
Why is Base32 used for TOTP secrets?▾
TOTP secrets (used in Google Authenticator, Authy, etc.) are Base32 encoded because Base32 is case-insensitive and avoids ambiguous characters (l/1, O/0). This makes them safe for manual entry and QR code generation across different systems.
Is Base32 encryption?▾
No. Base32 is encoding, not encryption. It does not provide any security — anyone can decode a Base32 string. Never use Base32 to hide passwords, secrets, or API keys.
Why does Base32 output sometimes end with "=" signs?▾
The "=" characters are padding. Base32 processes data in 5-byte groups, producing 8 characters. When input length is not a multiple of 5, padding is added to make the output length a multiple of 8. This is required by RFC 4648 but often omitted.