Encode
- Input
- Hi
- Expected output
- NBUQ====
A-Z, 2-7 alphabet.
Carregando ferramenta… / Loading tool…
text to base32 encoder
Base32 is an encoding similar to Base64, but it uses only 32 unambiguous uppercase characters (no 0/O, no 1/I/l), which makes it easier to type by hand, that's why it's the format used for TOTP authenticator secret keys like Google Authenticator.
A-Z, 2-7 alphabet.
Case-insensitive.
Select the Binary format, keep the direction on Text → Code and type your text. Each character becomes an 8-bit group (for example, 'A' becomes 01000001), separated by spaces. For the reverse, paste the binary and switch the direction to Code → Text, it works with space-separated groups or with one continuous run of bits.
It's the same format: in the TOTP protocol (RFC 6238), the binary secret key is shown to the user encoded as Base32, precisely so it's easy to type without mistakes when scanning the QR code isn't possible.
Base32 only uses 5 bits per output character (32 symbols), versus 6 bits for Base64 (64 symbols), so it needs more characters to represent the same number of bytes, about 60% overhead versus 33%.
No. Standard Base32 is defined in uppercase, but decoding accepts lowercase input too, normalizing it before processing.
All translation happens in your browser. No text is ever sent to a server, safe for passwords, tokens and sensitive data.