Base32 Converter

Encode short ASCII text to RFC 4648 Base32 with length.

What it does

Base32 spells bytes with capitals and digits 2 to 7, dodging mixed case confusion. One time codes and file names use it where Base64 plus and slash cause trouble.

The tool above reads up to 20 printable ASCII characters and prints Base32, length, and bytes. The default Hi matches the worked example, so the page opens showing JBUQ====. Type new text to update all three results.

Bits split into five bit groups indexed 0 to 31: A is 0 through 7 is 31. Here Hi bits 01001000 01101001 regroup to 01001 00001 10100 10000 for J B U Q. Four groups pad with four equals to eight chars.

Use this for short tokens and teaching. For binary safe blobs with plus and slash, use Base64 instead. For checksums use hash tools.

This page shows the alphabet, one full hand checked example for Hi, a reference table, and practice checks that run through the tool.

How to use

1. Type 1 to 20 characters.
2. Stay inside printable ASCII.
3. Read Base32 as capitals, digits, and =.
4. Read length including padding.
5. Split longer strings into chunks.
6. Decode elsewhere; this page encodes.

Formula

5 bit

One Base32 char.

=

Pad to multiple of 8 chars.

bytes

Input length.

RFC 4648 alphabet here, no lowercase output. Hex input first if starting from bytes.

Worked example

Reference table

Limits

• Printable ASCII 1 to 20 chars here.
• Encode only. No decode direction here.
• RFC 4648 basic alphabet, no hex extended.
• Long secrets split into chunks.

Common mistakes

• Expecting Base64 plus and slash here.
• Dropping = padding that decoders need.
• Feeding emoji outside ASCII.
• Reading length without padding.
• Lowercasing output that must stay upper.

Try it yourself

Quick checks. Answers sit tucked under each question.

Questions

Sources

• IETF RFC 4648
• Unicode: Character Code Charts

Related calculators