🔡

Base32 Encode / Decode

Encode text to Base32 or decode Base32 strings back to plain text. Supports RFC 4648 and Extended Hex (base32hex) alphabets. Everything runs in your browser —no server, no tracking.

Developer Tools Runs locally No data sent
RFC 4648 base32hex encode / decode client-side only
Alphabet
Plain Text
0 chars
→
Base32
0 chars Invalid Base32 string
💡
Base32 encodes binary data as ASCII text using 32 printable characters with = padding to a multiple of 8. RFC 4648 uses A–Z and 2-7; it avoids visually ambiguous characters like 0, 1, 8, 9. Extended Hex (base32hex) uses 0-9 and A–V, preserving sort order —useful for Crockford and NanoID variants. All processing happens entirely in your browser —nothing is sent to any server.

What is Base32?

Base32 is an encoding format that maps binary data into a restricted alphabet made of letters and digits. It is commonly used in OTP secrets, provisioning strings, and environments where case-insensitive or human-readable encodings are helpful.

How to Use Base32 Encoder / Decoder

  1. Paste the text or Base32 string you want to convert.
  2. Choose whether to encode or decode.
  3. Check whether padding or alphabet rules match your target system.
  4. Copy the converted result for use in your app or workflow.

Related Tools

📦
Base64 Encode / Decode
Encode or decode text and files to Base64
 📦
Base58 Encoder / Decoder
Encode or decode Base58 strings for Bitcoin, IPFS and more
 🔗
URL Encode / Decode
Encode or decode URL parameters and components
Understand Base32 ▾
Example
Input Hello
Output JBSWY3DP
Common Use Cases
  • Decode TOTP secret strings during MFA setup checks
  • Encode text for systems that prefer Base32 over Base64
  • Inspect RFC 4648 Base32 payloads from provisioning flows
  • Verify whether padding and alphabet variants are handled correctly
Why Use This Tool
  • Helpful for TOTP secrets, provisioning codes, and RFC 4648 compatibility checks.
  • Makes it easy to inspect padding and Base32 alphabet behavior.
  • Runs locally in the browser without sending encoded content anywhere.
Frequently Asked Questions
Why does the output end with "=" characters?

Base32 encodes data in 5-byte blocks. When the input length is not a multiple of 5, "=" padding characters are added to the output to make the total length a multiple of 8. Padding is part of the RFC 4648 standard and required by most decoders.

Is Base32 the same as Base32Hex?

No. RFC 4648 defines two Base32 variants: standard Base32 (A–Z, 2-7) and Base32Hex (0-9, A–V). They encode the same data but use different alphabets. This tool uses the standard Base32 alphabet by default.

Can I decode a TOTP secret key with this tool?

Yes. TOTP secret keys are Base32-encoded strings. You can paste them here to see the raw bytes, but note that this tool outputs decoded text —binary secrets may not display correctly as text.

Is my data stored or sent anywhere?

No. All encoding and decoding happens locally in your browser using JavaScript. Nothing is sent to a server.