Skip to content
en
All tools

Categories

Developer ToolsEncoding & DecodingJSON & DataHash & ChecksumText ToolsDate & TimeNetwork ToolsFile ToolsMarkdown & Diagrams

Base32 Encoder

Convert text into a Base32 string, the case-insensitive encoding used for authenticator secrets and file-safe identifiers.

Processed locally in your browser

Options
0 chars · 0 lines
The result will appear here.

What is Base32 Encoder?

Base32 represents data with 32 characters (A–Z and 2–7 in the standard RFC 4648 alphabet) and groups input in blocks of 5 bytes that become 8 characters. It is longer than Base64 but survives case-insensitive systems and avoids look-alike symbols such as + and /.

The encoder converts your text to UTF-8 bytes, then produces either the standard alphabet or the "Extended Hex" alphabet (0–9 and A–V, RFC 4648 §7) that preserves sort order. Padding with "=" up to a multiple of 8 characters is optional.

How does it work?

  1. Enter the text to encode; the Base32 result updates instantly.
  2. Pick the RFC 4648 alphabet (default) or Extended Hex, and decide whether to keep "=" padding.
  3. Copy the output, or press Swap to decode a Base32 string in the decoder.

Common use cases

  • Preparing a test secret in the Base32 format that TOTP and HOTP authenticator apps expect.
  • Producing case-insensitive identifiers that survive DNS labels, filenames and voice reading.
  • Checking your own Base32 implementation against the RFC 4648 test vectors such as foobar → MZXW6YTBOI======.
  • Encoding short payloads for QR codes where uppercase alphanumeric text is compact.

Examples

Try this input in the tool above:

Input
Hello, Base32!
Output
JBSWY3DPFQQEEYLTMUZTEII=

Privacy

Base32 Encoder runs entirely in your browser. The text or files you provide are processed on your device and are not uploaded, logged or stored on our servers.

Limitations

Base32 is not encryption, and it inflates data by about 60%. Never encode real authenticator secrets in an online page you do not trust.

Frequently asked questions

What does foobar look like in Base32?

MZXW6YTBOI====== with the standard alphabet and padding, or CPNMUOJ1E8====== with Extended Hex. These are the official RFC 4648 test vectors.

What is the Extended Hex alphabet for?

It uses 0–9 and A–V so that encoded strings sort in the same order as the raw bytes. It is rarer than the standard alphabet.

Is the "=" padding required?

Strictly, yes in RFC 4648, but many systems (including authenticator apps) accept Base32 without it. Untick padding to drop it.

Related tools

More tools in Encoding & Decoding →