Workflow & Usage
- Paste or type your input text into the left textarea.
- Use the Encode / Decode toggle inside the input area to switch modes.
- Select the required Base32 variant.
- Optional controls:
- Batch by newline — process one value per line
- Trim lines — ignore leading and trailing whitespace (batch mode)
- Strip padding — remove trailing ’=’ characters from encoded output
- Wrap @ 76 — insert line breaks every 76 characters (encode mode only)
- View the result instantly on the right and copy with one click.
Errors are reported per line, so invalid values do not break the entire batch.
Supported Base32 Variants
RFC 4648 (Standard)
- Alphabet:
A–Z 2–7 - Uses
=padding - Most widely supported Base32 variant
RFC 4648 (No padding)
- Same alphabet as standard Base32
- Padding characters are omitted
- Commonly used in URLs and compact identifiers
Base32hex (RFC 4648)
- Alphabet:
0–9 A–V - Preserves lexicographic ordering
- Used in some storage and indexing systems
Use Cases
- Encoding binary data for text-only channels
- QR codes and OTP secrets
- API tokens and identifiers
- File-safe and case-insensitive encodings
- Batch conversion during debugging or data cleanup
Tips & Best Practices
- Always confirm which Base32 variant your system expects.
- Padding may be required or forbidden depending on the protocol.
- Wrap output only when explicitly required by downstream systems.
- Base32 output is larger than Base64 but easier to read and transcribe.
How It Works
- Input text is encoded as UTF-8 bytes
- Data is processed in 5-bit chunks
- Characters are mapped using the selected Base32 alphabet
- Padding and line wrapping are applied only when enabled
- Decoding validates characters against the chosen variant
- All processing runs locally in your browser
