Encoding

Base32 Encoder / Decoder

Encode text to Base32 or decode Base32 back — the alphabet behind TOTP authenticator secrets.

Encoding and decoding run locally in your browser. Nothing is uploaded, logged, or stored.

0 chars
0 chars

How to use

  1. Choose the mode: Encode (text → Base32) or Decode (Base32 → text).
  2. Paste your input text or Base32 string.
  3. Click Convert and copy the result.

What is Base32?

Base32 (RFC 4648) encodes binary data using 32 unambiguous characters: A–Z and 2–7. It is case-insensitive and avoids easily confused symbols, which makes it ideal for secrets people may need to type or read aloud. Its most famous use is the shared secret in TOTP two-factor authentication — the string behind every QR code in authenticator apps.

The decoder accepts input with or without = padding, in any case, and ignores whitespace. Invalid characters are reported as a clear error instead of silent corruption. For binary-friendly compact encoding see the Base64 tool; for API credentials see the Random Token Generator.

Examples

Inspect a TOTP secret

Decode the Base32 secret from your authenticator setup to verify it matches your backup record.

Encode for case-insensitive channels

Base32 is safe where capitalization may be lost — license keys, printed codes, and voice transfer.

Frequently Asked Questions

Is my input uploaded anywhere?+
No. Everything runs in your browser — especially important for secrets.
Is padding required for decoding?+
No. Padding (=), whitespace, and letter case are all tolerated on input.
Why not Base64?+
Base64 is denser but case-sensitive and includes +, /, and =, which are awkward to type or speak. Base32 trades ~20% size for human safety.
Which Base32 variant is implemented?+
The standard RFC 4648 alphabet (A–Z, 2–7) with = padding on encode. The extended-hex variant used in some specs is not implemented.

Related Tools

Looking for something else? Browse all tools