Encode text to standard RFC 4648 Base32
Input
Hello WorldExample output
JBSWY3DPEBLW64TMMQ======Base32 Encoder & Decoder
Encoders & Decoders100% Client-SideReady
TEXT
0 lines0 chars
0 B / 4.77 MB
Read-only
0 lines0 chars
0 B
About this tool, examples & FAQ
Encode text to Base32 or decode Base32 strings back to UTF-8 text. Supports RFC 4648 standard, Base32Hex, and Crockford alphabets with optional '=' padding and case customization. All conversions execute 100% locally in your browser.
Key facts
| Alphabets | RFC 4648 Standard, Extended Hex, and Crockford |
|---|---|
| Padding | Optional '=' trailing padding support |
| Maximum Input | 5 MB |
| Execution Deadline | 2 s |
How to use
- Paste your plain text or Base32 encoded data into the input editor.
- Select Encode or Decode operation from the toolbar.
- Choose your alphabet variant: RFC 4648 (standard), Extended Hex, or Crockford.
- Toggle padding and letter casing options according to your system requirements.
- Click Run (or press Ctrl/Cmd + Enter) to process the data locally in Web Worker memory.
- Copy or download the output result instantly.
Examples
Decode RFC 4648 Base32 to plaintext
Input
JBSWY3DPEBLW64TMMQ======Example output
Hello WorldEdge cases
Case insensitivity and padding
RFC 4648 Base32 uses uppercase letters by default. When decoding, lowercase characters are accepted and normalized automatically, and trailing '=' characters are stripped before processing.
Crockford character normalization
In Crockford Base32, visually ambiguous characters are mapped to numbers: uppercase or lowercase 'I' and 'L' are decoded as '1', and 'O' is decoded as '0'. Hyphens are ignored.
Multi-byte UTF-8 representations
Non-ASCII characters like emojis and accented letters are converted to their underlying multi-byte UTF-8 sequences before 5-bit grouping.
How it works
- Converts the input string to raw bytes using the browser's TextEncoder.
- Groups 40-bit chunks (5 bytes) into eight 5-bit values.
- Maps each 5-bit integer to the corresponding character in the chosen 32-symbol alphabet.
- Appends '=' padding characters as required by RFC 4648.
Related workflows
Base64 Encoder / Decoder
Encode UTF-8 text to standard or URL-safe Base64 and decode Base64 back to text.
Hex (Base16) Encoder / Decoder
Encode text to hexadecimal (Base16) byte strings and decode hex bytes back to UTF-8 text with customizable delimiters and prefixes.
URL Encoder / Decoder
Encode and decode URL components, query parameters, and special characters using RFC 3986 percent-encoding or form-urlencoded format.
Frequently asked questions
Why use Base32 instead of Base64?
Base32 is case-insensitive and omits symbols that require URL escaping, making it easier for human entry and ideal for Two-Factor Authentication TOTP secret keys and file systems.
What is Crockford Base32?
Douglas Crockford designed a Base32 variant for human readability that excludes I, L, O, and U to prevent accidental profanities and confusion between letters and numbers.
Are my secret keys sent to any server?
No. All encoding and decoding executes entirely inside your browser via local Web Workers. Zero tokens or inputs leave your device.
References
- RFC 4648 Section 6 — Base 32 Encoding — Official IETF specification for Base32 and Base32Hex data encoding