Base32 Encoder / Decoder
Encode or decode Base32 text per RFC 4648 — used by TOTP authenticator secret keys.
Encoding and decoding happen entirely in your browser. Nothing here is ever sent to a server.
Output
ValidKRZHKZKNMVQXG5LSMVFWS5A=
For informational and educational purposes only — not professional or technical advice, and not a substitute for consulting a qualified professional about your specific situation. TrueMeasureKit is not liable for decisions made based on these results. See our Terms of Service.
Why Base32 exists alongside Base64
Base32 groups bits 5 at a time instead of Base64's 6, using a 32-character alphabet (A–Z and 2–7) chosen specifically to avoid visually ambiguous characters like 0/O and 1/I. That makes it longer than Base64 for the same data, but far more forgiving when a human has to read, type, or speak it aloud — which is exactly why it shows up in TOTP two-factor authenticator secret keys and some URL-shortening schemes. This implementation follows RFC 4648, the same standard authenticator apps use.
Frequently asked questions
Why do authenticator apps use Base32 instead of Base64?
Base32's alphabet (A–Z and 2–7) is case-insensitive and excludes visually ambiguous characters, which matters when a secret key has to be typed manually — TOTP secrets are commonly shared as Base32 for exactly this reason.