Encode text to Base32 or decode Base32 to text. Supports Standard (RFC 4648), Hex, and Crockford variants.
Enter your text or Base32 string
Paste the text you want to encode, or a Base32 string (like a TOTP secret) you want to decode.
Select variant and encoding options
Choose the Base32 variant (Standard, Hex, or Crockford) and whether to include padding.
Click Encode or Decode
Click Encode to convert text to Base32 or Decode to convert Base32 back to text, then copy the result.
Yes, this Base32 tool is completely free with no usage limits. Encode or decode as many strings as you need without any registration or payment required.
Yes, your data is completely secure. All Base32 encoding and decoding operations happen locally in your browser using JavaScript. No data is ever transmitted to our servers or any third party. Your sensitive information, including TOTP secrets, stays on your device at all times.
Base32 encoding is most commonly used for TOTP (Time-based One-Time Password) secrets in two-factor authentication (2FA) systems like Google Authenticator and Authy. It uses only uppercase letters A-Z and digits 2-7, making it easy to read and type manually. Base32 is also used in file systems and URLs where case-insensitivity is required.
Standard Base32 (RFC 4648) uses A-Z and 2-7, which is the most common format used by TOTP apps. Extended Hex (Base32hex) uses 0-9 and A-V, preserving sort order. Crockford Base32 uses 0-9 and A-Z but excludes I, L, O, U to avoid confusion with similar-looking characters, making it ideal for human-readable codes.
Base32 uses 32 characters (A-Z and 2-7) while Base64 uses 64 characters (A-Z, a-z, 0-9, + and /). Base32 is less space-efficient (increases size by 60% vs Base64's 33%) but is case-insensitive and easier to type manually. Base32 is preferred for TOTP secrets and situations requiring human readability, while Base64 is better for data efficiency.