Base32 Encode and Decode
Encode text to Base32 or decode Base32 to text using RFC 4648. Case-insensitive, in your browser, nothing uploaded.
Independently verified for accuracy
Calculator by Toolsloft ↗Encode text to Base32 or decode Base32 back to text, following the RFC 4648 standard. Base32 uses only the letters A to Z and the digits 2 to 7, so it survives case-insensitive systems and is easy to read aloud. Common in TOTP secret keys and some file and email encodings.
How this is calculated
Follows RFC 4648. Encoding groups the UTF-8 bytes of the text into five-bit chunks and maps each to the standard 32-character alphabet, padding the output with "=" to a multiple of eight characters. Decoding reverses that and is case-insensitive, ignoring surrounding whitespace.
How to use
- Choose encode or decode.
- Paste your text or Base32 string.
- Copy the result from the output box.
Examples
- Encode:
Hello becomes JBSWY3DP - Decode:
MZXW6YTBOI====== becomes foobar
FAQ
- How is Base32 different from Base64?
- Base32 uses a smaller alphabet of 26 letters and 6 digits, so it is case-insensitive and easier to type or read aloud, at the cost of longer output than Base64.
- Why does the output end in equals signs?
- The "=" characters are padding that round the output up to a multiple of eight characters, as required by RFC 4648. They carry no data.
- Is my text uploaded anywhere?
- No. Encoding and decoding run entirely in your browser, so nothing is sent to a server.