Base32 to Text Decoder
Example
Input:
MZXW6YTBOI======
Output:
foobar
About this converter
Decoding Base32 reads the A–Z2–7 alphabet in groups of 8 characters (5 bytes), ignoring case — one of the practical reasons the encoding exists. This decoder also ignores missing padding, since TOTP secrets are frequently passed around without it. The classic sources of failure are the characters the alphabet deliberately excludes: a 0, 1 or 8 in the input means the string is not standard Base32 (it may be base32hex, a variant with a 0–9A–V alphabet used in some DNS and encoding contexts, which this page does not silently pretend to support).
Frequently Asked Questions
My TOTP secret contains spaces — will it decode?
Yes, whitespace is ignored. The secret is a Base32 string; spaces are only there for readability when you type it.
What is base32hex and why did my string fail?
A variant alphabet (0–9 then A–V) that sorts in the same order as the data. It is used in DNSSEC and some encodings; strings containing 0, 1, 8 or 9 are usually base32hex, not Base32.
Is a TOTP secret sensitive?
Very — it is the shared key that generates your two-factor codes. Decode it only on pages you trust (this one runs locally), and never share it.