RFC 4648 compliant Base32 encoding and decoding — text, hex, or Base32.
Frequently Asked Questions
What is Base32 encoding?▼
Base32 represents binary data using 32 ASCII characters (A-Z, 2-7). Defined in RFC 4648, it's used in TOTP tokens, DNS zone files, and case-insensitive systems.
What is the difference between Base32 and Base64?▼
Base32 uses A-Z and 2-7 (case-insensitive), while Base64 uses A-Z, a-z, 0-9, +, /. Base32 is ~20% larger but case-insensitive.
Is this RFC 4648 compliant?▼
Yes, this tool follows RFC 4648 standard Base32 encoding with padding.
Can I convert hex to Base32?▼
Yes. Select the Hex to Base32 mode, paste your hex string, and click Convert.
What characters does Base32 use?▼
A-Z (26 letters) and 2-7 (6 digits) = 32 characters. Padding uses =.
Is my data sent to a server?▼
No. All encoding and decoding happens in your browser.
Where is Base32 commonly used?▼
TOTP/2FA tokens, Google Authenticator, DNS zone files (RFC 5155), and case-insensitive data systems.
Does it support decoding Base32 to text?▼
Yes. Select Base32 to Text mode, paste your Base32 string, and the decoded text appears.