Encode / Decode Base32

Encode text to Base32 (RFC 4648) or decode a Base32 string to readable text, a format often used for TOTP secret keys or case-insensitive identifiers.

Example:

How it works

Base32 encodes binary data using only 32 characters (A-Z and 2-7), making it case-insensitive and easy to copy by hand — which is why it's used for secret keys in two-factor authentication apps (TOTP). This tool converts text to its Base32 representation and vice versa.

Why do we see '=' at the end of a Base32 string?

The '=' sign is a padding character used to make the output length a multiple of 8 characters, per the RFC 4648 standard. It has no special meaning and is simply ignored during decoding.

Is Base32 safer than Base64?

No, it's not an encryption mechanism but a simple reversible encoding: anyone can decode a Base32 string to recover the original data. It's chosen for readability and case tolerance, not for confidentiality.

100% local processing: encoding and decoding happen entirely in your browser via WebAssembly.