Encoding / Decoding

Base32 Encode / Decode

Convert UTF-8 text to and from RFC 4648 Base32.

RFC 4648 Base32
UTF-8 text, processed locally
Result
The result will appear here.

Base32 Encode / Decode

Convert UTF-8 text to RFC 4648 Base32 or decode it back to text. Whitespace, hyphens, and trailing = padding are accepted while decoding.

Boundaries

  • Useful for printable identifiers and common TOTP secret representations
  • Base32 is encoding, not encryption, and does not protect sensitive data

Frequently Asked Questions

Base32 or Base64 — which one should I use?
Prefer Base64: it is denser (about one-third overhead versus 60% for Base32). Two cases require Base32: TOTP two-factor secrets, which authenticator apps only accept as Base32, and human transcription scenarios, because Base32 uses only A–Z and 2–7, dropping the confusable 0, 1, 8, and 9.
Why do I get a length or padding error when decoding?
Base32 output length must be a multiple of 8, padded with = signs. The usual culprits are a dropped trailing = during transcription, or stray spaces and hyphens. This tool ignores whitespace and hyphens and repairs missing padding automatically.
Is it safe to convert my 2FA secret with this tool?
The conversion runs locally in your browser and is never uploaded. Still, a TOTP secret is equivalent to a password: clear it when you are done. Use this tool to debug and understand key formats; manage real secrets with a password manager.