Decode RFC 4648 Base32 to UTF-8 text, UTF-16, Hex, Base64, or another output encoding, with or without padding. Read more

Decode Base32 online

This tool converts RFC 4648 Base32 text back to its original bytes, then displays those bytes using the selected output encoding. Choose UTF-8 when the encoded value represents ordinary text, or Hex and Base64 when you need an exact binary representation.

Decoding does not decrypt or verify the data. A Base32 string can be decoded by anyone, and successful decoding does not prove that its content is trusted or unmodified.

How to decode Base32

Paste the Base32 value into the input editor.
Choose the output encoding expected for the decoded bytes.
Click Decode.
If text output is unreadable, verify the original character encoding or inspect the bytes as Hex.

Both MFRGG=== and its unpadded form MFRGG decode to UTF-8 text abc in this tool.

Valid Base32 input

Standard RFC 4648 Base32 uses letters A–Z, digits 2–7, and optional = padding at the end. Other named schemes may use a different alphabet or ordering and are not necessarily compatible with this decoder.

Padding communicates the length of the final partial group. Some applications omit it when the byte length is known, while others require canonical padded input. Preserve the convention expected by the protocol you are using.

Base32 decoding FAQ

Why does decoded Base32 look corrupted?

The decoded bytes may be binary, use a different character encoding, or come from a different Base32 alphabet. Try Hex output first to verify the bytes without interpreting them as text.

Is Base32 case-sensitive?

RFC 4648 specifies an uppercase alphabet, although decoders may choose to accept lowercase input. For reliable interchange, use the canonical form required by the target system.