JBSWY3DPFQQEC3TWNFWCC===
About Base32 Encode & Decode Online (RFC 4648)
Base32 is an encoding scheme that represents binary data using a 32-character set: the uppercase letters A–Z and the digits 2–7 (RFC 4648). Because it avoids the easily-confused characters 0, 1, and 8 and is case-insensitive, Base32 is a natural fit for values people read aloud or type by hand — TOTP and 2FA secrets, DNS labels, and human-friendly identifiers.
This free Base32 encoder and decoder converts UTF-8 text — including accents, non-Latin scripts, and emoji — in both directions, using the standard RFC 4648 alphabet with "=" padding. Decoding accepts both uppercase and lowercase input and ignores whitespace.
Everything runs entirely in your browser. Nothing you paste is ever uploaded, which makes it safe to use even with sensitive values like authenticator secrets.
Features
- Encode text to Base32 and decode Base32 back to text
- RFC 4648 standard alphabet (A–Z, 2–7) with automatic "=" padding
- Full UTF-8 support — handles accents, non-Latin scripts, and emoji
- Case-insensitive decoding; clear errors on invalid input; works fully offline
How to use
- Paste your text or a Base32 string into the input pane.
- Choose Encode to convert text → Base32, or Decode for the reverse.
- Copy the result from the output pane — or clear and start again.
Frequently asked questions
How is Base32 different from Base64?
Base32 uses a 32-character alphabet (A–Z and 2–7) instead of 64, so its output is longer — about 60% larger than the input versus roughly 33% for Base64. In exchange, Base32 is case-insensitive and avoids ambiguous characters, which makes it easier to type, read aloud, and use in DNS or filenames.
Why is Base32 used for TOTP / 2FA secrets?
Authenticator secrets are often shown to users and typed in manually. Base32 is case-insensitive and excludes the look-alike characters 0, 1, and 8, which reduces transcription errors. That is why most TOTP setup keys and QR codes encode the shared secret in Base32.
Does Base32 protect my secret?
No — Base32 is a reversible representation, not a security layer, so a Base32-encoded TOTP seed is no more secret than the raw bytes. Treat the encoded value as plaintext: anyone who reads it can decode it. Keep authenticator secrets confidential and reach for a proper cipher when you need real protection.
Is my input uploaded to a server?
No. This Base32 converter is pure client-side JavaScript: the encode and decode steps run in the page itself, so even authenticator seeds you paste stay on your device and the tool keeps working with the network disconnected.
Related tools
Everything runs locally in your browser — your input is never uploaded.