Base32 Encoder

Encode bytes of the text as Base32.

Use this tool

Result

The result appears in this panel after you run the tool.

About this tool

Padding is included. The alphabet is A–Z and 2–7.

This is encoding, not encryption.

How to use it

  1. Open this page and provide the input it asks for.
  2. Set the options that are visible, then use Encode Base32.
  3. Read the result in the panel. Copy it or download it when a file is offered. The input stays in this browser.

Limitations

Five-bit groups and equals padding

Alphabet and padding

The encoder reads UTF-8 bytes and emits the RFC 4648 base32 alphabet: A through Z and 2 through 7. Bits are taken five at a time. A leftover group is shifted and one more symbol is written. The string is then padded with equals signs until its length is a multiple of eight. An empty input therefore becomes eight equals signs, because there were no symbols and the pad still runs. The symbols are uppercase. This is not the base64 alphabet, which uses 64 symbols, includes digits below 2, includes lowercase in the usual spelling, and pads to a multiple of four. Base32 is bulkier and avoids several characters that base64 uses. Neither alphabet is a secret. Both are reversible encodings of the same bytes.

No checksum is added. A TOTP secret is often written in this alphabet, but this page does not compute a one-time code. It only spells the bytes.

What a second encode does

Encoding the already encoded text encodes those ASCII symbols as new bytes, so the second result is not a friendly restatement of the first. One encode is the representation. The decoder uppercases and strips trailing equals signs, so the padding characters are not data. They exist so a reader can see the quantum. Stripping them yourself before you decode is fine. Adding them in the wrong count is the decoder’s problem to ignore, because it strips every trailing equals sign rather than checking the count.

Not a cipher, and not base58

There is no key. Publishing the base32 string publishes the text. Use it when a protocol asks for this alphabet, including places that forbid ambiguous glyphs. Base58, on its own page, drops padding and uses a different alphabet that also omits lookalikes, and it treats leading zero bytes as the character 1. This page does not. A leading zero byte here is just another group of bits, padded at the end with equals signs. If the next system expects base64, do not send this alphabet and hope. The symbols will not decode there.

Privacy

Your input is processed in your browser and is not uploaded to UtilChain. File names, text, and results are not sent to analytics.