Base32 Encoder / Decoder

Encode text into RFC 4648 Base32 or decode Base32 back into readable UTF-8 text.

How Base32 works

Base32 converts bytes into a text-safe alphabet. It usually turns 5 bytes into 8 Base32 characters. Padding with = is used when the final byte group is incomplete.

Type: Encoding Secret key: None Alphabet: A-Z 2-7 Padding: = Security: Not encryption

Options

Use lowercase output

Omit padding on encode

Ignore whitespace when decoding

Accept lowercase input

Wrap encoded output

Encoding uses UTF-8 bytes, then repacks them into 5-bit Base32 symbols using A-Z and 2-7.

Output stats

Mode: Encode Input chars: 0 Input bytes: 0 Output chars: 0 Output bytes: 0 Base32 chars: 0 Padding: 0 Lines: 0

Base32 is useful when text needs to avoid punctuation and mixed case, such as recovery codes, tokens, DNS-like labels, and copy-safe identifiers. It is not encryption.

Input text

Output Base32

Using This Tool: Guide & Notes Show guide

Base32 encodes bytes using a conservative alphabet, usually A-Z and 2-7, which is useful in case-insensitive or punctuation-restricted systems.

How to use it

Choose Encode to turn text into Base32, or Decode to recover UTF-8 text.
Paste input into the input box and check the output.
Use Load example to compare a known-good Base32 string.
Copy the output once padding and casing match your target format.

Options and settings

Use lowercase output changes display style, although standard Base32 is usually uppercase.
Omit padding removes trailing = characters when a system expects shorter unpadded Base32.
Ignore whitespace when decoding accepts wrapped, spaced, or pasted Base32.
Accept lowercase input lets lowercase Base32 decode without manual conversion.
Wrap encoded output breaks long output into readable lines.

Notes

Base32 is easier to carry through restricted text systems than Base64, but it is longer.
It does not hide data. It only changes how bytes are written.

Base32: The Encoding That Makes Binary Easier to Read, Copy, and Survive

How a 5-bit alphabet became a quiet helper in authenticator apps, DNS-safe strings, recovery codes, identifiers, and text-shaped software systems.

Read the article

Signal acquired

A note from the team

We build these tools because we love cryptography, encoding, and making difficult ideas easier to explore. If they've helped you, even a small coffee means the world to the project. Thank you!

Say thanks on Ko-fi