Base32 Encode

Encode text as RFC 4648 Base32 and keep the output easy to compare and copy

Safety note: Base32 work stays in your browser. This page uses RFC 4648-style Base32, which is the format most TOTP secrets use before they become otpauth:// URIs.

Encode text as Base32Paste text, choose whether padding matters, and get a copy-ready Base32 string

Use no padding for common TOTP-style secrets, or keep RFC padding when another system expects it.

Padding

Text input

Base32 output

What Base32 Encodes

Base32 turns raw bytes into an alphabet built from A-Z plus 2-7. That makes it more human-friendly than Base64 in some contexts, especially manual authenticator setup, but it also means the bytes only round-trip if the alphabet and padding rules stay consistent.

Encode or Decode Base32

Paste the source text and click Encode as Base32.
Toggle padding only when another system explicitly expects `=` characters at the end.
Copy the output exactly. Changing case, punctuation, or padding changes the decoded bytes.

Why Base32 Shows Up in OTP

Many TOTP secrets are stored or shared as Base32 because the alphabet avoids symbols that are awkward to type or read aloud. That same convenience is why you often need a quick Base32 check before you build an otpauth:// URI.