What alphabet does this use?

RFC 4648 Base32 — uppercase letters A through Z and digits 2 through 7. Each output character represents 5 bits of input data.

When should I use Base32 instead of Base64?

Use Base32 when the environment is case-insensitive (e.g., DNS, file systems on Windows/macOS), or when you need an alphabet that avoids confusing characters like 0/O and 1/l.

What does the padding (=) do?

RFC 4648 requires padding to make the output length a multiple of 8. Some systems (e.g., certain TOTP libraries) strip padding; toggle it off if needed.

Is my input sent to a server?

No. All encoding is done in JavaScript in your browser. No data is transmitted anywhere.

What character encoding is used for the input?

Input text is encoded as UTF-8 bytes before Base32 encoding. Multibyte characters (accented letters, CJK, emoji) are supported.

Base32 Encoder

Name: Base32 Encoder
Availability: InStock
Author: Nham Vu

Encode any text to standard Base32 (RFC 4648) right in your browser — no server, no upload.

Input Text

Include padding =

Input: 0 bytes

Base32 Output

Input bytes

Output chars

Expansion

—

Copied!

Summary

Encode any text to standard Base32 (RFC 4648) right in your browser — no server, no upload.

How it works

Type or paste your text into the input box.
The Base32-encoded output updates instantly as you type.
Toggle "Include padding" to add or remove trailing = characters.
Click "Copy Output" to copy the encoded string to your clipboard.
Use "Clear" to reset both fields.

Use cases

Encode secret keys for TOTP / 2FA authenticator apps.
Store binary-safe identifiers in case-insensitive environments.
Encode data for DNS labels that cannot contain Base64 characters.
Embed short binary payloads in QR codes or NFC tags.
Test Base32 decoding logic during backend development.
Generate human-readable encoded tokens without mixed-case confusion.

Frequently Asked Questions

Last updated: 2026-06-09 · Reviewed by Nham Vu