Encoding
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.
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.
Decode the Base32 secret from your authenticator setup to verify it matches your backup record.
Base32 is safe where capitalization may be lost — license keys, printed codes, and voice transfer.
Encode and decode Base64 with full Unicode support. URL-safe mode included.
Percent-encode and decode URLs and query parameters, component or full-URL mode.
Encode and decode Punycode (IDN) domain names — convert Unicode domains to xn-- form and back.
Escape quotes, backslashes, and newlines so text can be embedded safely inside a JSON string.
Looking for something else? Browse all tools