Base32 Encoder

Base32, Crockford and more

Herramienta Base32

Codifica y decodifica datos usando diferentes variantes de Base32

Variante Base32

Usar padding

Mayúsculas

Agrupar cada 8 chars

Entrada (texto/archivo)

Texto a codificar

Arrastra un archivo aquí o haz clic para seleccionar

Resultado (Base32)

Base32 Encoder: Alphanumeric Encoding Compatible with URLs and File Names

Base32 encodes binary data using only 32 characters (A-Z and 2-7), avoiding case-sensitive characters and confusing ones like 0/O and 1/I/L. Ideal for use cases requiring case insensitivity: DNS, filenames, TOTP secrets, phone codes.

Compared to Base64 (which uses 64 characters), Base32 is longer but more robust: it works with case-insensitive protocols and is easier to transcribe manually. Google uses it for 2FA secret sharing.

Our encoder implements the standard RFC 4648. Everything runs in your browser — no data sent to servers. Compatible with text and files.

How does it work?

1
Select mode
Choose 'encode' to convert text/file to Base32 or 'decode' to reverse the process.
2
Enter input
Paste the text or upload the file you want to convert.
3
Copy the result
The encoded output appears immediately. Copy to clipboard with one click.

Frequently Asked Questions

When should I use Base32 instead of Base64?

Use Base32 when you need case insensitivity (DNS, some old email systems), when the data will be transcribed manually (2FA secrets, verification codes) or in filesystems that don't distinguish case.

How much space does Base32 take vs Base64?

Base32 uses ~60% more space than Base64 (each 5 bytes → 8 chars vs each 3 bytes → 4 chars in Base64). Base64 is more efficient in space but less robust.

Why doesn't Base32 use I, L, O, and 1?

Actually, RFC 4648 does use I and O, but excludes 0, 1 and 8 to avoid confusion. Base32hex variants (used by others) exclude the confusing ones. Both variants are supported by our tool.