About the Base32 Encode
Base32 encodes bytes using 32 characters: the uppercase letters A to Z and the digits 2 to 7. Because it avoids lowercase letters and the easily confused characters 0, 1 and 8, it is safe to write down, read aloud and type, which is why authenticator app secrets, some coupon codes and DNS-based identifiers use it. This tool encodes the UTF-8 bytes of your text and pads the result to a multiple of eight characters with =.
The padding rule is the part people trip over. Base32 works on 40-bit blocks of five bytes, so an input whose length is not a multiple of five leaves a partial block, and the encoder appends one, three, four or six = characters to fill the final group of eight. Many systems then strip that padding again: authenticator apps in particular expect a TOTP secret with no = at all, so delete the trailing equals signs before pasting a key into a QR generator.
Base32 costs roughly 60 percent overhead against Base64's 33 percent, a trade worth making when a person has to read the string aloud or retype it from a printed card. It is an encoding, not encryption. Reverse it with Base32 Decode, choose Base64 Encode when the string only ever travels between machines, and use Hex Encode when you want to inspect the bytes one at a time.
How to use
- Paste the text.
- Copy the Base32 output.
- Use it where a case-insensitive key is needed.
Common questions
- Which alphabet is used?
- The standard RFC 4648 alphabet: A-Z and 2-7, with = padding.
- Can I encode a TOTP secret with this?
- You can encode bytes to Base32, which is the format authenticator apps expect, though most apps generate the secret for you.
- Why is Base32 longer than Base64?
- It packs five bits per character instead of six, trading size for a smaller, unambiguous alphabet.