Input Base32: Paste the Base32 encoded string in the left textarea. The tool decodes automatically.
Choose Format: Supports Standard Base32 (RFC 4648, A-Z2-7) and Extended Hex Base32 (RFC 4648, 0-9A-V).
View Results: Results can be displayed as UTF-8 text or hexadecimal (Hex).
Copy: Click "Copy Result" to copy decoded content to clipboard.
TOTP Key Decoding: Google Authenticator and Authy use Base32-encoded shared secrets.
DNS/DNSSEC: DNSSEC domain keys (DNSKEY) are encoded in Base32 format.
Data Recovery: Recover original data from Base32-encoded strings in various systems.
Both are encoding schemes that convert binary data to text. Base32 uses 32 characters (A-Z, 2-7), encoding 5 bits per character (~60% size increase). Base64 uses 64 characters (A-Za-z0-9+/) with higher efficiency: 6 bits per character (~33% size increase). Base32's advantage is case-insensitivity (all uppercase), making it better for manual entry and voice transmission.
Base32 is commonly used for: 1) DNS (DNSSEC stores domain keys in Base32); 2) One-time passwords (TOTP/RFC 6238 shared secrets are Base32-encoded); 3) Cryptocurrency addresses (Bitcoin's Bech32 format); 4) Case-insensitive encoding environments; 5) Phone/voice transmission scenarios requiring manual input.
No. Base32 is an encoding scheme, not encryption. No key or password is needed for decoding. It simply converts data between representation formats to ensure transmission integrity, not confidentiality. For security, encrypt data before Base32 encoding.
Extremely fast. For typical Base32 strings (TOTP keys, short text), decoding completes in milliseconds. For larger encoded data (encoded files), decoding speed depends on size β typically 1-2 seconds for hundreds of KB to a few MB.
Yes. The tool automatically strips spaces, newlines, and tabs from the input string before decoding. This is especially useful for Base32 strings copied from emails, SMS, or voice transcriptions that contain formatting characters.