Base32 Decoder
Decode RFC 4648 Base32 back to text, or to a binary file when the content is not text.
Paste or drop
Paste text below, or drop a file instead.
Choose an output
Decode RFC 4648 Base32 back to text, or to a binary file when the content is not text.
About Base32 Decoder
Paste RFC 4648 Base32 and this tool decodes it back to the original bytes. If the result is valid UTF-8 text, it is shown as text; otherwise you get a binary file to download.
When it helps
- Checking the raw bytes behind a TOTP secret from an otpauth:// URI.
- Decoding a Base32 identifier or token from an API to see what it contains.
- Verifying that a Base32 encoder in your own code produces the expected output.
Tips
- Input is case-insensitive. Spaces, hyphens and = padding are ignored, so grouped secrets like JBSW Y3DP or JBSW-Y3DP decode correctly.
- Most TOTP secrets are random bytes, not text, so expect a binary file rather than readable output for those.
- The digits 0, 1, 8 and 9 are not part of the alphabet. If you see an error about them, the string was probably mistyped, or it uses a different variant such as base32hex or Crockford.
Good to know
Quick answers about base32 decoder in your browser.
The input contains a character outside A to Z and 2 to 7. The error shows the character and its position, so you can check for a mistyped 0 instead of O or 1 instead of I.
No. Padding is ignored, so Base32 with or without it decodes to the same bytes.
Yes. There is no sign-up, no watermark and no limit on how many files you process.
No. Files are read and processed locally in your browser, so they never leave your device.
Related tools
Part of the Developer Utilities collection.