Base32 Encoder/Decoder
Convert text and bytes using RFC 4648 Base32 encoding
Enter text to encode
RFC 4648 Base32 with optional padding and lowercase output. File conversion is capped at 16 MB for responsiveness.
About Base32 Encoder/Decoder
Encode and decode data using Base32, a binary-to-text encoding that uses a 32-character alphabet (A-Z and 2-7). Base32 is widely used for TOTP/HOTP secrets in two-factor authentication, DNS labels, and any context where case-insensitive, human-readable encoding is needed. Unlike Base64, Base32 avoids characters that can be confused in certain fonts or input methods. This tool supports both padded and unpadded output, uppercase and lowercase modes, and runs entirely in your browser with no server-side processing.
How to Use Base32 Encoder/Decoder
- Enter text in the input field or paste a Base32-encoded string.
- Select Encode or Decode to perform the conversion.
- Toggle padding and case options to match your requirements.
- Copy the output using the copy button.
Base32 Encoder/Decoder FAQ
When should I use Base32 instead of Base64?
Base32 is ideal for case-insensitive systems, manual human entry, and contexts like OTP secrets where avoiding ambiguous characters matters. Base64 is more space-efficient when those constraints do not apply.
Does this support padded and lowercase output?
Yes. You can output padded or unpadded Base32 and choose between uppercase (standard) and lowercase formats.
What is Base32 commonly used for?
Base32 is used for TOTP/HOTP secret keys in authenticator apps, Crockford encoding, DNS labels, file names on case-insensitive file systems, and encoded tokens where readability matters.
How does Base32 differ from Base32hex?
Standard Base32 uses A-Z and 2-7. Base32hex uses 0-9 and A-V, which preserves sort order of the encoded data — useful for database indexing.
Is my data sent to a server?
No. All encoding and decoding happens locally in your browser. Your data stays on your device.