What is Base32 encoding used for?

Base32 encoding converts binary data into human-readable ASCII text using only uppercase letters A-Z and digits 2-7. It is primarily used for TOTP/2FA secret keys (Google Authenticator, Authy), encoding data that needs to be typed manually, case-insensitive data transmission, QR code generation for authentication, DNS records (DNSSEC), and file integrity checksums. Unlike Base64, Base32 avoids ambiguous characters like 0/O and 1/I, making it perfect when codes need to be read aloud or manually entered.

How do I encode text to Base32?

Simply paste or type your text into the input field and the tool will automatically convert it to Base32 format. The encoder handles all character types including special characters, Unicode, emojis, and multi-byte characters using UTF-8 encoding. The resulting Base32 string uses only A-Z and 2-7 characters with equals sign padding, making it safe for manual entry. The encoding happens instantly in your browser without any server uploads, ensuring complete privacy.

Can I encode files to Base32?

Yes! Click the "File" button to upload any file type (images, PDFs, documents, binaries). The tool will convert the entire file content to Base32 format. This is useful for encoding files in human-readable format, creating checksums, transmitting binary data through text-only channels, or embedding file data in text documents. Large files may take longer to process due to browser memory limitations, and Base32-encoded files are approximately 60% larger than the original due to encoding overhead.

Why is Base32 used for TOTP and 2FA codes?

TOTP (Time-based One-Time Password) standards like RFC 6238 specify Base32 encoding for secret keys because users often need to manually enter these secrets when setting up two-factor authentication. Base32 alphabet (A-Z, 2-7) is completely unambiguous—there is no confusion between 0/O, 1/I/l, or uppercase/lowercase letters. When you scan a QR code for Google Authenticator, Authy, or similar apps, the secret is Base32-encoded. If QR scanning fails, you manually type the Base32 string, making human-friendliness critical. This is why TOTP uses Base32 instead of the more compact Base64.

What characters are valid in Base32?

Valid Base32 characters are uppercase letters A through Z (26 characters) and digits 2 through 7 (6 characters), totaling 32 characters. The padding character is equals sign (=). Base32 intentionally excludes 0, 1, 8, and 9 to avoid visual confusion with letters O, I, B, and g. The RFC 4648 standard defines this alphabet. Some variants exist (like Crockford Base32 which uses 0-9, A-V excluding I, L, O, U), but standard RFC 4648 alphabet is most common and used by this tool. Output is always uppercase with padding to multiples of 8 characters.

Why does Base32 output have equal signs at the end?

The equals signs (=) are padding characters that make the Base32 string length a multiple of 8 characters. Since Base32 uses 5 bits per character and bytes are 8 bits, sometimes padding is needed to represent the exact data length. For example, encoding "Hello" produces "JBSWY3DP" with no padding, but "Hi" produces "JBSQ====" with four padding characters. The padding ensures decoders can determine where the data ends. Some implementations omit padding (it is technically optional per RFC 4648), which is why decoders should handle both padded and unpadded Base32 strings.

Is Base32 encoding secure or a form of encryption?

No! Base32 is an encoding method, not encryption. It provides absolutely no security or protection. Anyone can easily decode Base32 strings back to the original data using free tools. Base32 is designed for data representation and compatibility, not confidentiality. Never use Base32 alone to hide sensitive information like passwords or API keys—it offers zero security. If you need to protect data, use proper encryption algorithms like AES-256 or RSA. Base32 is often used after encryption to encode encrypted binary data as human-readable text for transport, but the encoding itself provides no security whatsoever.

Is my data safe when using this Base32 encoder?

Yes! All encoding happens entirely in your browser using JavaScript. Your data never leaves your device and is not uploaded to any server. The tool processes everything locally on your computer or mobile device, ensuring complete privacy. Once you close or refresh the page, all data is cleared from browser memory. This client-side approach is secure for encoding sensitive data like TOTP secrets or credentials, though remember that Base32 encoding itself does not encrypt or protect data from anyone who intercepts the encoded string.

How do I use the encoded Base32 for Google Authenticator?

To set up Google Authenticator with your Base32-encoded secret: 1) Open Google Authenticator app, 2) Tap the plus icon to add an account, 3) Select "Enter a setup key", 4) Enter your account name, 5) Paste the Base32 string (without spaces) as the key, 6) Select "Time based" for the account type, 7) Tap Add. The app will immediately start generating 6-digit codes. Most authenticator apps expect secrets between 16-32 characters (80-160 bits of entropy). Shorter secrets are less secure but easier to type manually if needed.

What is the difference between Base32 and Base64 encoding?

Base32 uses 32 characters (A-Z, 2-7) while Base64 uses 64 characters (A-Z, a-z, 0-9, +, /). Base32 is case-insensitive and more human-friendly since it avoids ambiguous characters like 0/O and 1/I. However, Base32 produces larger output—about 60% overhead compared to Base64's 33% overhead. Base32 is preferred for TOTP secrets, spoken codes, manual entry, and URLs where case-sensitivity causes issues. Base64 is more efficient for general data encoding, file attachments, APIs, and situations where compactness matters more than human readability. Choose Base32 when humans need to read or type the encoded data.

Free Base32 Encoder Online

Encode text and files to Base32 format instantly. Perfect for generating TOTP/2FA secrets and human-readable data encoding. 100% free, secure, and works in your browser.

EncodeDecode

Text to encode

File

Base32 encoded result

Other Base32 tools

Base32 Decoder•File to Base32•Base32 to File