Utils365

Base32 encoder and decoder

Turn text into Base32, the case-safe alphabet used for 2FA keys, and back again.

  • 100% free
  • No sign-up
  • Runs in your browser

Paste text, open a file, or drop one here

Next: Base64 encode / decode · Text to hex · Hash generator

Report a problem with this tool

How to use Base32 encode / decode

  1. Choose the direction

    Text → Base32 encodes; Base32 → text decodes. Pasting something that looks like Base32 offers to decode it.

  2. Set the alphabet and padding

    Use the standard A–Z and 2–7 alphabet or Base32hex, and choose whether to add = padding at the end.

  3. Copy the result

    Copy or download it. Decoding ignores case, spaces and dashes, so keys copied from apps work as they are.

Why use Utils365

  • Matches the standard

    Encoding follows RFC 4648 exactly and is tested against its official examples, such as foobar → MZXW6YTBOI======.

  • Reads keys as people write them

    Lower case, groups of four with spaces and missing padding are all accepted, as 2FA setup pages show them.

  • Any text

    Text is encoded as UTF-8, so accents and emoji come back exactly when you decode.

Frequently asked questions

What is Base32?

A way to write bytes using 32 characters: A–Z and 2–7. Every 5 bytes become 8 characters. It’s about 60% larger than the original, more than Base64, but it has no lower case or symbols to mistype.

Where is Base32 used?

Most famously for 2FA secret keys in authenticator apps (TOTP), which you may type by hand. It also appears in onion addresses, some file-sharing hashes and Crockford-style IDs.

Why are there = signs at the end?

Padding fills the result out to a multiple of 8 characters. f encodes to MY======. It’s optional: decoders can work out the length without it, and 2FA keys usually leave it off.

Why aren’t 0, 1 and 8 in Base32?

The standard alphabet leaves out 0, 1 and 8 because they look like O, I or L and B. That makes it safer to read aloud or type from paper.

What is Base32hex?

A variant in RFC 4648 using 0–9 then A–V. Encoded values sort in the same order as the original bytes, which some databases and DNS records rely on. It isn’t compatible with standard Base32.

How is Base32 different from Base64?

Base64 uses 64 characters including both cases, + and /, so it’s more compact (4 characters per 3 bytes) but case-sensitive. Base32 trades size for being case-insensitive and easy to type.