Base32 Encoder / Decoder
Developer
Convert text to and from Base32. Standard Base32 (RFC 4648) uses the alphabet A–Z + 2–7, which is what TOTP / 2FA seed strings are encoded with. The base32hex variant (0–9 + A–V) preserves lexicographic order, handy for filenames and DNS labels. Padding with `=` is optional on encode and tolerated on decode.
—
Output
How to use
- Pick encode or decode.
- Choose the variant — Standard (TOTP / 2FA) or Hex (Crockford-style).
- Toggle padding off if you want a clean output without trailing `=`.
Frequently asked questions
- Why not just use Base64?
- Base32 uses only A–Z and 2–7 — case-insensitive and avoids visually confusing characters like 0/O and 1/l. That makes it safer for hand-typed secrets, voice transcripts, and DNS labels.
- Is this what TOTP / 2FA apps use?
- Yes. The seed string you scan or type into Google Authenticator / Authy / 1Password is Base32-encoded with the standard alphabet. Padding is usually stripped.
- What's the difference between Standard and Hex?
- Standard (A–Z, 2–7) is the common one. Base32hex (0–9, A–V) preserves the sort order of the original bytes, which matters for things like generated filenames where you want byte-order sorting to match string-order sorting.
- Does this work on binary data?
- The input field is text — Unicode is encoded as UTF-8 first. For arbitrary binary data, paste the bytes hex-encoded into a separate tool first.
Related tools
JWT Decoder
Decode a JSON Web Token to inspect its header, claims, and expiration.
Developer00
UUID Generator
Generate random version-4 UUIDs in bulk, with copy.
Developer00
Hash Generator (SHA)
Generate SHA-1, SHA-256, SHA-384, and SHA-512 hashes from text.
Developer00
URL Encoder / Decoder
Percent-encode text for URLs, or decode encoded URLs back to text.
Developer00
Base64 Encoder / Decoder
Encode text to Base64 or decode Base64 back to text, instantly.
Developer00
JSON Formatter & Validator
Format, beautify, minify, and validate JSON right in your browser.
Developer00