Base32 encoder (RFC 4648)
Useful for two-factor secrets and file names on systems that ignore letter case.
Loading the tool…
Processing and privacy: The result is calculated inside your browser and your data is not sent to any server.
How to use it
- Enter text and add = padding.
- The result appears straight away and updates as you edit.
- Copy the result, or copy a link that keeps the same values to share it.
How it is calculated
The text becomes UTF-8 bytes, the bits are split into 5-bit groups, and each group (0 to 31) maps to a letter of ABCDEFGHIJKLMNOPQRSTUVWXYZ234567. Output is padded with = to a multiple of 8.
Example
Inputs: Add = padding = yes. Result: Base32: MZXW6YTBOI======; Bytes: 6.
foobar
MZXW6YTBOI======
Limits and caveats
- Uses the standard Base32 alphabet only, not base32hex or Crockford.
- Base32 is an encoding, not encryption; anyone can decode it.
Questions about this tool
Why is Base32 longer than Base64?
Each Base32 character carries 5 bits instead of 6, so the size grows by about 60% instead of 33%.
Why are 0, 1, 8 and 9 missing?
They were left out so 0 is not confused with O and 1 with I when people read or type the code.
Can I use it for an authenticator app secret?
Yes. TOTP secret keys are usually written as Base32, often without padding.