32 symbols · RFC 4648 · ~60% overhead
RFC 4648 Base32 with alphabet A–Z 2–7. No lowercase, no ambiguous 0/1. Common in TOTP / 2FA secret keys and DNS-safe identifiers. Type below to see which symbols your data lights up.
Text → Base32 box — the RFC 4648 encoding appears instantly in Base32 output.Copy result to copy the encoded string (the same format used by TOTP / 2FA apps).Base32 → Text and the decoded text appears below.Clear any time to reset a box and start over.Authenticator apps store their secret keys in Base32. Encode or decode one to inspect the exact bytes behind the codes.
The uppercase A–Z 2–7 alphabet survives systems that dislike lowercase or special symbols.
No 0, 1, or O lookalikes make it safer to read aloud over the phone.
Output is uppercase only, so it round-trips cleanly through case-folding systems.
Turns arbitrary bytes into a clean letters-and-digits string you can email, paste, or print.
Everything runs in your browser. Nothing is uploaded, logged, or sent to a server.
The RFC 4648 alphabet: A–Z and 2–7 (32 characters total), uppercase only.
To avoid confusion with the letters O, I, and L when transcribing by hand or voice.
They pad the output to a multiple of 8 characters so that groups of 5 input bytes map cleanly onto 8 output characters.
No. Base64 has a larger alphabet so its output is shorter, but Base32 is case-insensitive and friendlier for humans.
No. Input is uppercased automatically and only A–Z 2–7 are used.
Never. All conversion happens locally in JavaScript and nothing is sent anywhere.