Base32 Decode

Decode Base32 safely and inspect the exact bytes it really represents

Safety note: Encode or decode RFC 4648 Base32 with explicit padding and alphabet handling. This format is used by many TOTP secrets before they become otpauth:// URIs.

Decode RFC 4648 Base32Paste Base32, strip out spacing or hyphens automatically, and confirm what bytes it really decodes to

This decoder accepts uppercase or lowercase input and ignores spaces or hyphens before decoding.

Base32 input

Decoded text

What Base32 Encodes

Base32 turns raw bytes into an alphabet built from A-Z plus 2-7. That makes it more human-friendly than Base64 in some contexts, especially manual authenticator setup, but it also means the bytes only round-trip if the alphabet and padding rules stay consistent.

Encode or Decode Base32

Paste the Base32 string and click Decode Base32.
Use the decoded hex output when the payload is binary or not clean UTF-8 text.
Copy the output exactly. Changing case, punctuation, or padding changes the decoded bytes.

Why Base32 Shows Up in OTP

Many TOTP secrets are stored or shared as Base32 because the alphabet avoids symbols that are awkward to type or read aloud. That same convenience is why you often need a quick Base32 check before you build an otpauth:// URI.