Base32 Encoder & Decoder – Handle RFC4648, Crockford & Z-Base32
Encode secrets, OTP keys, and config tokens with your preferred Base32 alphabet, padding, and line-break options for human-readable or URL-safe strings.
Base32 Encoder/Decoder
Encode text to Base32 or decode Base32 to text
lightbulbPopular Use Cases
Encode TOTP secrets for 2FA authentication apps
Encode data for URLs without special characters
Encode text for QR codes and barcode systems
Encode hash values and checksums in Base32 format
Encoded Base32 will appear here
Example Inputs
Hello, World!
JBSWY3DPEBLW64TMMQ======
{
"user": "john",
"role": "admin"
}Keyboard Shortcuts
keyboardShow shortcutsexpand_more
Related tools
Show moreShow more
› About this tool · FAQ
Stop wrestling with Base32 encoding formats! Encode and decode text using Base32 with RFC 4648, Crockford, Extended Hex, and Z-Base32 variants. Free online tool with custom formatting, padding options, and case handling. Works offline in your browser.
How do I encode Base32 online?
Paste your text into the encoder, select your preferred variant (Standard RFC 4648, Crockford, Extended Hex, or Z-Base32), configure padding and formatting options, then click Encode. The Base32 encoded result appears instantly.
How do I decode Base32?
Switch to Decode mode, paste your Base32 encoded string, select the correct variant that was used for encoding, and click Decode. The tool automatically handles padding and whitespace removal to decode your Base32 data back to text.
Is this Base32 encoder free?
Yes, completely free with no limits on encoding or decoding. No signup required, no watermarks, and unlimited usage. All processing happens in your browser for complete privacy.
What Base32 variants are supported?
Standard RFC 4648, Extended Hex (base32hex), Z-Base32, and Crockford Base32 variants are all supported. Each variant uses a different alphabet optimized for specific use cases.
When should I use Base32 instead of Base64?
Use Base32 when you need case-insensitive encoding, human-readable strings for URLs, or compatibility with systems that prefer Base32. It's also better for situations where character ambiguity (O vs 0) is a concern.
What is the difference between Base32 variants?
Standard uses A-Z and 2-7, Extended Hex uses 0-9 and A-V, Crockford excludes ambiguous characters (I, L, O) for human readability, and Z-Base32 uses a different alphabet optimized for sorting.
Why is Base32 output longer than Base64?
Base32 uses 32 characters vs Base64's 64, so it needs more characters to represent the same data (about 60% longer). This tradeoff provides better human readability and case-insensitivity.
Can I use Base32 for URLs?
Yes, Base32 is excellent for URLs because it's case-insensitive and uses only alphanumeric characters. Use Extended Hex or Crockford variants for URL-safe encoding without special characters.