Base32 encode & decode (RFC 4648)

Client

RFC 4648 Base32 uses the alphabet A–Z234567 and = padding. Encode UTF-8 text or decode Base32 back to text—same strict UTF-8 assumption as the Base64 workspace.

Part of encoding tools.

Workspace

Paste text, run encode or decode—the field updates in place for quick copy.

RFC 4648 Base32

?

Uses the standard alphabet A–Z2–7 with = padding. Decoding expects UTF-8 text after bytes are recovered—same idea as the Base64 page.

For URL-safe Base64, use the Base64 & URL tool; for MIME email bodies, see quoted-printable.

Common use cases

  • Encode short secrets or test vectors with a case-insensitive alphabet (common in RFCs and some crypto APIs).
  • Decode pasted Base32 from configs or logs when the payload is UTF-8 text.
  • Compare output shape with Base64 when readability or charset constraints differ.

Common mistakes to avoid

  • Expecting encryption

    Base32 is reversible encoding for transport or display—not confidentiality.

  • Decoding arbitrary binary as UTF-8

    This workspace interprets decoded bytes as UTF-8 text. Random binary may fail strict UTF-8 decoding.

FAQ

How is this different from Base64?

Base32 uses a 32-character alphabet (A–Z and 2–7), is more compact for humans to read case-insensitively, and is longer than Base64 for the same bytes.

Does data leave my browser?

No. Encoding and decoding run entirely on your device.

Common search terms

Phrases people search for that match this tool. See the full long-tail keyword index.

  • base32 encode online
  • rfc 4648 base32 decoder
  • base32 decode utf-8 browser
  • base32 rfc4648 alphabet online

More tools

Related utilities you can open in another tab—mostly client-side.