Base32 Encoder / Decoder
Loading…
About this Tool
A dedicated developer and cybersecurity utility that bidirectionally encodes plain text into RFC 4648-compliant Base32 representation and decodes Base32 strings back into original text or binary data. Operating on 5-bit chunks (translating 40 bits of input into eight 5-bit characters), Base32 uses exclusively uppercase letters A–Z and digits 2–7. Visually ambiguous characters like 0/O, 1/I/l, and 8/B are omitted by design, making it the premier global standard for human-transcribed two-factor authentication (2FA/TOTP) keys in Google Authenticator and Microsoft Authenticator. All encoding and decoding run 100% inside your client browser memory with zero network exposure.
Processed safely on your device
Everything happens in your browser on this device. Your files are never sent to our servers—so you can use it with peace of mind.
How to Use
Enter or paste your text string or Base32 encoded sequence (e.g., JBSWY3DPEHPK3PXP) into the input box.
Choose your target operation: 'Base32 Encode' or 'Base32 Decode'.
Select your preferred output formatting, including RFC 4648 padding '=' inclusion and uppercase/lowercase casing.
Click the copy button to transfer the resulting Base32 string or decoded plain text directly to your clipboard for application config or 2FA setup.
Key Scenarios & Use Cases
Google Authenticator & TOTP Secret Key Verification
Inspect, encode, and decode 16-character or 32-character Base32 shared secrets used by two-factor authentication (2FA/TOTP) applications.
Case-Insensitive Filesystems & DNS Label Encoding
Safely store and transmit binary metadata across Windows NTFS/FAT filesystems and DNS records that do not preserve character case.
Paper Backup & Cold Storage Recovery Seeds
Prevent disastrous human transcription errors when writing down cryptographic seed phrases or master license keys on physical paper.
Legacy Email Gateways & Strict Firewall Transmissions
Transmit binary payload data across strict security filters that strip non-alphanumeric symbols (+ and /) commonly found in Base64.
Unambiguous License Keys & Promotion Codes
Generate user-facing product activation codes, vouchers, and shortened identifier tokens that customers can type without confusing '0' with 'O'.
Frequently Asked Questions (FAQ)
Base64 uses 64 characters (including lowercase, +, and /) and expands data by approximately 33%, making it efficient for web transfer but case-sensitive. Base32 uses only 32 unambiguous characters (A–Z and 2–7) with a ~60% size expansion, making it case-insensitive and vastly superior for human transcription and OTP secret keys.
RFC 4648 intentionally excluded '0' (confusable with 'O'), '1' (confusable with 'I' and 'l'), and '8' (confusable with 'B') to prevent human transcription errors when typing or reading cryptographic keys.
Base32 processes data in 5-byte (40-bit) blocks. When the input length is not an exact multiple of 5 bytes, the remaining bit positions are filled with 1 to 6 '=' padding characters. Many TOTP systems omit padding, which our tool supports.
Yes. RFC 6238 TOTP authenticators generate an 80-bit (10-byte) or 128-bit (16-byte) secret key, which is encoded into a 16-character or 26/32-character Base32 string for manual entry.
Standard Base32 uses 'A–Z' and '2–7'. Base32hex (extended hex alphabet) uses '0–9' and 'A–V' to maintain sorted collation with hexadecimal numbers. This tool provides standard RFC 4648 Base32.
Yes, 100% secure. AllThatConverter performs all operations strictly within your local browser runtime. No data is sent over the network, and the tool remains fully operational even when disconnected from the internet.