Base32 Encoder and Decoder
Base32 represents bytes with 32 case-insensitive characters, which makes it easy to read aloud and safe in file names and URLs. It is the format of two-factor (TOTP) secrets. Encode text as UTF-8 Base32, or decode a Base32 string back to text, or to hex when the bytes are binary.
Encode or Decode Base32
Result
Notes
Summary
How to Use the Base32 Encoder/Decoder
- Choose Encode or Decode.
- Pick the alphabet: standard RFC 4648, base32hex or Crockford.
- Type or paste the input; the result updates as you type.
- Copy the result.
About This Tool
Developers implementing TOTP or file-safe identifiers, people inspecting 2FA secrets in test setups, and students comparing Base32 with Base64.
Input: Text or Base32 · Output: Base32 or text.
Features and Limitations
Features
- Matches the RFC 4648 test vectors.
- Three alphabets including Crockford (which treats O as 0 and I/L as 1).
- Decoding ignores case, spaces and missing padding.
- Binary results are shown as hex instead of garbled text.
Limitations
- Text is encoded as UTF-8.
- Crockford's optional check symbol is not supported.
- Very long inputs (over 10 million characters) are refused.
- Results are computed in your browser; nothing you enter is sent to a server.
Example
RFC 4648 vectors: f → MY======,
foobar → MZXW6YTBOI======.
Frequently Asked Questions
Is Base32 encryption?
No. It is an encoding that anyone can reverse. Do not use it to hide secrets.
Why do TOTP secrets look like Base32?
Authenticator apps share the random secret key as Base32 because it avoids ambiguous characters and works with any letter case.
Do I need the = padding?
Padding makes the length a multiple of 8. Many systems, including TOTP URIs, omit it; the decoder accepts both.
Is my data uploaded?
No. Encoding and decoding happen in your browser.
Related Tools
More like this: all Encoding & Security tools, all Developer & Web tools or the TinySandy home page.