Base32 Encoder/Decoder

How to Use Base32 Encoder/Decoder

1. Choose the mode: click Encode to convert text to Base32, or Decode to convert Base32 back to text.
2. Select the variant: RFC 4648 (A-Z, 2-7) for standard Base32, or Extended Hex (0-9, A-V) for the hex alphabet variant.
3. Type or paste your text (encode mode) or Base32 string (decode mode) into the input field. The tool processes your input automatically with a 200ms debounce.
4. View the result in the output field. The output is read-only and can be copied or downloaded.
5. Use the Copy button to copy the output to your clipboard, or Download to save it as a text file.
6. Click Swap to move the output into the input field and switch modes — handy for round-trip testing.
7. Click Load Example to try the tool with sample data.
8. Click Clear to reset both input and output fields.

Base32 vs Base64

Both Base32 and Base64 serve the same fundamental purpose — encoding binary data as text — but they make different trade-offs between size efficiency and human usability. Understanding these differences helps you choose the right encoding for your use case.

• Alphabet size:Base32 uses 32 characters (A-Z, 2-7), while Base64 uses 64 characters (A-Z, a-z, 0-9, +, /). Base32's smaller alphabet makes it more human-friendly and easier to transcribe.
• Size overhead: Base32 expands data by approximately 60% (8 chars per 5 bytes), while Base64 expands data by only ~33% (4 chars per 3 bytes). Base64 is more space-efficient.
• Case sensitivity: Base32 is case-insensitive — uppercase and lowercase letters are equivalent. Base64 is case-sensitive, meaning a and A represent different values. This makes Base32 safer in environments where case folding may occur.
• Visual ambiguity: Base32 deliberately excludes 0, 1, O, and I to reduce confusion. Base64 includes all alphanumeric characters plus + and /, which can be harder to read manually.
• Use in URLs and DNS: Base32 is naturally URL-safe and DNS-safe since it contains no special characters. Base64 requires URL-safe variants (Base64url) that replace + and /.

Common Use Cases

• TOTP / HOTP Authentication — Time-based and HMAC-based one-time password algorithms (like Google Authenticator) use Base32 to encode secret keys.
• DNSSEC — DNS Security Extensions use Base32 Extended Hex to encode NSEC3 hashed owner names in zone files.
• Secret sharing — Systems that share secret keys via human-readable formats (like backup codes or recovery keys) often use Base32 for its readability.
• Crockford Base32 — A popular variant used for checksums and human-readable identifiers, designed to minimize transcription errors.
• Peer-to-peer protocols — Some P2P systems and content-addressable networks use Base32 to encode hashes and identifiers in a case-insensitive format.
• License keys & serial numbers — Software licensing systems often use Base32 (or variants) to generate human-readable keys that are easy to type and communicate over the phone.

Features

• Full Unicode support — correctly encodes and decodes emoji, CJK characters, accented letters, and all UTF-8 text
• Dual mode — switch between Encode and Decode with a single click
• Two variants — toggle between RFC 4648 standard and Extended Hex alphabet
• Auto-processing — output updates automatically as you type (200ms debounce)
• Base32 validation — real-time indicator shows whether your input is valid Base32
• Copy to clipboard — one-click copy of the output for instant use
• Download output — save the result as a text file
• Swap input/output — instantly swap the result into the input and switch modes for round-trip testing
• Load example — try the tool instantly with built-in sample data
• 100% client-side — your data never leaves your browser; no server processing
• Dark mode support — seamless experience in both light and dark themes