Base32 Encoder & Decoder
Encodes UTF-8 bytes using RFC 4648 Base32: A–Z and 2–7, with = padding. Decoding reverses the 5-bit groups.
About this base32 encoder & decoder
Base32 Encoder & Decoder — browser-based utility.
How this tool works
Encodes UTF-8 bytes using RFC 4648 Base32: A–Z and 2–7, with = padding. Decoding reverses the 5-bit groups.
- Paste the example into “Input”.
- Set “Second input / expression” to encode.
- Click “Run locally” and compare “Output” with the example.
Worked example
Scenario: Convert a four-byte UTF-8 text value with Base32 Encoder & Decoder
Sample input:
Processing: Encodes UTF-8 bytes using RFC 4648 Base32: A–Z and 2–7, with = padding. Decoding reverses the 5-bit groups.; Second input / expression = encode
Illustrative output:
Limits and verification
Accepts lowercase and valid unpadded groups. Invalid lengths, padding, nonzero padding bits and invalid UTF-8 are rejected; Base32hex is not supported. Unpaired Unicode surrogate characters are rejected to prevent silent replacement during UTF-8 encoding.
Examples demonstrate an expected workflow; they do not prove every input or every branch of an external specification. Check important results with an independent source before using them for money, security, compliance, safety, or irreversible file changes.
Browser processing boundary
Tool input is processed by code running in the browser and is not intentionally sent to a CZOA processing API. The page can still request ordinary site assets, analytics, or advertising when those services are enabled. Browser extensions and managed-device software remain outside this tool's control.
Relevant references
These references govern or help explain the format, protocol, or calculation used here. Listing a reference does not claim certification or complete implementation of every optional feature.
Content owner: CZOA Tools · Last reviewed: 2026-09-15 · Review methodology
How to use it
- Paste the example into “Input”.
- Set “Second input / expression” to encode.
- Click “Run locally” and compare “Output” with the example.
Frequently asked questions
Which Base32 alphabet does the converter use?+
Encoding uses the RFC 4648-style uppercase alphabet A-Z and 2-7. UTF-8 bytes are packed into five-bit groups and padding equals signs are appended to an eight-character boundary.
What did the browser fixture verify?+
The UTF-8 text foo encoded to MZXW6===, the standard padded Base32 representation.
How is decode mode selected?+
The second control is interpreted by the codec mode helper. Without an explicit choice, padded text matching the Base32 character class can select decode; otherwise it selects encode.
Does Base32 preserve arbitrary text exactly after roundtrip?+
For valid UTF-8 input and valid encoded bytes it is intended to recover the byte sequence. Invalid Base32, malformed padding, or bytes that are not valid UTF-8 produce errors rather than a successful text result.