How to Use the Base32 (RFC 4648) & Crockford Base32 Encoder / Decoder
-
1
Choose between Encode (Text to Base32) or Decode (Base32 to Text).
-
2
Select alphabet standard: Standard RFC 4648 (A-Z, 2-7) or Crockford Base32 (omits I, L, O, U to prevent visual confusion).
-
3
View instantaneous encoding with optional padding `=` characters.
Practical Example & Use Case
Common Real-World Scenario
Decoding an authentication seed secret string (`JBSWY3DPEHPK3PXP`) used to configure Google Authenticator or 1Password 2FA.
Technical Notes & Limitations
Browser Engine Architecture
Strictly adheres to RFC 4648 5-bit block specifications with padding support.
Frequently Asked Questions
Why is Base32 used for 2FA instead of Base64?
Base32 uses only uppercase letters and digits 2-7, avoiding case-sensitivity mistakes and eliminating visually ambiguous characters like '1', 'l', '0', and 'O'.