Base32 Decoder
Paste Base32 and read the text.
About this tool
Padding may be present. A character outside the alphabet is rejected.
The result is text from those bytes.
How to use it
- Open this page and provide the input it asks for.
- Set the options that are visible, then use Decode Base32.
- Read the result in the panel. Copy it or download it when a file is offered. The input stays in this browser.
Limitations
- The result is text from those bytes.
Bad symbols throw, padding is only stripped
Cleanup before the bits
The decoder trims, strips trailing equals signs, and uppercases. It does not remove spaces or newlines in the middle. Each remaining character must sit in A-Z or 2-7. Any other character, including 0, 1, 8, 9, and the padding character once it is no longer trailing, fails with an error naming the alphabet mismatch. The bits are accumulated five at a time and emitted eight at a time. Leftover bits at the end are dropped rather than turned into an extra byte. The bytes are then decoded as UTF-8.
That failure mode is the opposite of the encoder. The encoder always emits legal symbols and padding. It does not reject your text. This page rejects illegal symbols loudly and accepts messy padding quietly. A string of only equals signs becomes empty after the strip and decodes to an empty string, which matches the encoder’s empty input. A missing pad on a real payload also decodes, because padding was never checked, only removed.
Round-trip losses
Encoder output round-trips for text that is valid UTF-8, which is all the encoder writes. The losses show up on inputs the encoder did not write. Interior whitespace fails the whole value. Lowercase is accepted, so case is not preserved: re-encoding writes uppercase. Extra trailing equals signs disappear. A non-UTF-8 byte sequence can decode to the replacement character rather than throwing, because the text decoder is lenient. If you needed a strict byte dump, this page is aimed at text.
Base64 padding and the base64 alphabet are not accepted. A base64 string usually contains characters this alphabet rejects, and you will get the error rather than a wrong text. That is useful. It is still not a confidentiality check. A valid base32 string is public data. Decoding it does not authenticate the sender, and it does not mean the string was a TOTP secret.
Privacy
Your input is processed in your browser and is not uploaded to UtilChain. File names, text, and results are not sent to analytics.

