Contact

Tools  /  Encoding  /  Base32 Decoder

Base32 Decoder

Decode a Base32 string back to text.

What this tool does

A Base32 string pasted on the left decodes back to its original text on the right, live, using the standard RFC 4648 alphabet.

Case and padding don't have to match exactly

Because RFC 4648 Base32 uses only uppercase letters, input is read case-insensitively, so lowercase or mixed-case text decodes the same as its uppercase form. Trailing = padding characters are also handled automatically rather than needing to be exactly correct.

What happens with invalid input

Base32 only permits the letters A through Z and the digits 2 through 7. A character outside that set — including 0, 1, 8, and 9, which RFC 4648 Base32 deliberately does not use — is reported clearly rather than silently producing a wrong result.

Privacy

Decoding happens in your browser. Nothing you paste is sent to a server.

Frequently asked questions

Is my data uploaded anywhere?
No. Decoding happens locally in the browser — nothing is sent to a server.
Does the input need to be uppercase?
No -- decoding reads the standard RFC 4648 alphabet case-insensitively, so lowercase or mixed-case text decodes the same as its uppercase equivalent.
Why does decoding fail on some pasted text?
RFC 4648 Base32 only permits the letters A through Z and the digits 2 through 7. Characters outside that set, including 0, 1, 8, and 9, are not valid in this alphabet and cannot be decoded as-is.
Does the Base32 string need its padding characters exactly right?
Trailing = padding is handled automatically, so a string missing its padding characters still decodes correctly.
Can this decode a 2FA secret key back into readable text?
A 2FA secret key is itself random binary data rather than text, so decoding it here will not produce readable output -- this tool is for Base32 that represents actual text.
Theme Accent