Base32 Encoder & Decoder

Encode and decode RFC 4648 Base32 strings and 2FA TOTP secret keys to plain text or hex with instant client-side conversion.

Base32 RFC 4648 & TOTP Codec

Standard 32-character binary encoding for 2FA authenticator seeds and DNS labels

Standard / Alphabet

Data Format

Equals (=) Padding

Presets

Source (TEXT)29 chars

Base32 Output48 chars

JBSWY3DPEBLW64TMMQQSAU3UNFWGK43UEBJWKY3VOJUXI6I=

Case-Insensitive Binary-to-Text Encoding

Base32 plays a critical role in modern cybersecurity and identity infrastructure. By mapping binary data to an unambiguous subset of 32 characters, Base32 enables secure cross-platform transmission across case-insensitive file paths, legacy mail systems, and time-based authenticator apps.

Applications

✓
2FA Authenticator Seed Recovery & Inspection
Decode raw Base32 secret keys used by Google Authenticator, Authy, and 1Password when generating Time-based One-Time Passwords (TOTP).
✓
Case-Insensitive File Systems & DNS Records
Encode binary hashes into characters compatible with case-insensitive systems like Windows FAT/NTFS and DNS domain label specifications.
✓
Cryptographic SAS & Fingerprint Displays
Display short authentication strings using Crockford's Base32 alphabet to prevent reading errors over voice calls.
✓
Microcontroller & Embedded Protocol Payloads
Transmit packed byte structures over 7-bit ASCII serial lines without parity or delimiter collision issues.

Key Capabilities

✓

RFC 4648 Standard Compliant

Full support for standard Base32 (A-Z, 2-7) with optional `=` padding control matching authenticator standards.

✓

Crockford & Base32Hex Support

Seamlessly toggle to Douglas Crockford's checkable alphabet or RFC 4648 §7 Extended Hex Alphabet.

✓

Hex & Text Bi-Directional Conversion

Encode raw binary hex bytes or UTF-8 text strings directly into Base32 and vice versa.

✓

Zero-Latency Client-Side Engine

Bitwise operations execute entirely in your browser window, guaranteeing privacy for sensitive 2FA seeds.

Frequently Asked Questions

Why do 2FA apps like Google Authenticator use Base32?

Base32 uses only 32 uppercase characters (A-Z and 2-7). It excludes digits 0, 1, 8, and 9 to eliminate visual confusion with letters O, I, B, and g. This makes manual entry of 2FA backup keys foolproof.

What is the difference between Base32 and Base64?

Base64 uses 64 characters (A-Z, a-z, 0-9, +, /), packing 6 bits per character. Base32 uses 32 characters, packing 5 bits per character. While Base32 produces roughly 20% longer strings than Base64, it is case-insensitive and contains no punctuation marks.

What does the '=' character mean at the end of a Base32 string?

The '=' character is a padding character. In RFC 4648, Base32 encodes data in 40-bit chunks (5 bytes into 8 Base32 characters). If the original data is not a multiple of 5 bytes, '=' signs pad the output to an exact multiple of 8 characters.

Are TOTP 2FA secret keys safe to decode here?

Yes, our implementation executes 100% inside your local web browser using client-side JavaScript. No keys, secrets, or inputs are logged or sent across the network.