ENCODING
Base32 Encoder
Encode text to Base32 (RFC 4648).
What this tool does
Text typed or pasted on the left encodes to Base32 on the right, live, using the standard RFC 4648 alphabet — the common default most software means when it says "Base32."
Why Base32 exists alongside Base64
Base32 uses only uppercase letters and the digits 2 through 7, which means the result stays identical whether a system treats it as uppercase or lowercase, and reads cleanly in places that are picky about punctuation or case — a filesystem, a QR code, a value someone has to type by hand. This is also the format authenticator apps use for a 2FA secret key.
Privacy
Encoding happens in your browser. Nothing you type or paste is sent to a server.
FAQ
Frequently asked questions
Is my data uploaded anywhere?
No. Encoding happens locally in the browser — nothing is sent to a server.
What alphabet does this use?
The standard RFC 4648 Base32 alphabet -- uppercase A through Z and the digits 2 through 7, with = used for padding.
Why would Base32 be preferred over Base64 in some situations?
Base32 avoids characters that behave differently depending on case or that cause trouble in case-insensitive systems, filenames, or something a person has to type by hand -- at the cost of a longer result for the same data than Base64 would produce.
Is this the format used for 2FA authenticator secret keys?
Yes -- authenticator apps store a TOTP secret key as RFC 4648 Base32, which is why this specific alphabet is the standard choice rather than an arbitrary one.
Does encoding change the length of the text significantly?
Yes -- Base32 represents each 5 bits of the original data as one output character, so the result is noticeably longer than the original text, and typically longer than the same data encoded as Base64.