43 characters · 9 words · 43 bytes (UTF-8)
Output will appear here
Click in the output to select all text
43 characters · 9 words · 43 bytes (UTF-8)
Output will appear here
Click in the output to select all text
Encode and decode text using Bitcoin-style Base58 encoding.
URL-safe Base64 encoding and decoding without padding or special URL characters.
Encode text to hexadecimal byte representation and decode hex back to ASCII.
Obfuscate text using the ROT13 letter rotation algorithm.
This Base32 tool encodes text into RFC 4648-compliant Base32 format and decodes Base32 strings back to plain text, instantly in your browser. Base32 uses a restricted 32-character alphabet (A-Z and 2-7) that avoids visually ambiguous characters, which makes it popular for things that get typed or spoken by hand — TOTP two-factor authentication secrets, DNS-safe identifiers, and filesystem-friendly names are the most common uses you'll run into. Developers implementing 2FA/TOTP flows, sysadmins decoding authenticator app secrets, and anyone working with case-insensitive encoding needs will find this converter useful. Encoding and decoding both run entirely as JavaScript in your browser — no text, including sensitive TOTP seeds, is ever uploaded or logged on a server. There's no signup and no limits, and conversions happen instantly as you type. If you need standard Base64 instead, this platform has a dedicated Base64URL tool as well. Scroll down to encode or decode your Base32 string right now.
Base32 is commonly used for TOTP/2FA secret keys, DNS labels, filesystem names, and any context where a case-insensitive, human-typeable encoding is preferred over Base64.
Base32's alphabet avoids visually similar characters (like 0/O and 1/I/l) and is case-insensitive, making it easier for people to read, type, and transcribe accurately by hand.
No, Base32 is a reversible encoding scheme, not encryption — anyone can decode it back to the original data without a key.
Base32 encoding expands data by roughly 60%, since it uses 8 output characters to represent every 5 bytes of input.
Yes, TOTP secrets used by Google Authenticator and similar apps are standard Base32-encoded strings following RFC 4648.
Yes, standard Base32 pads output with '=' characters so the encoded length is a multiple of 8, though some implementations omit padding.
The standard alphabet is uppercase, but most decoders, including this one, accept lowercase input for convenience.