convert

Base32 Encoder

Encode text or any file to RFC 4648 Base32 (used by TOTP secrets and many APIs).

Runs on your deviceBatch readyPaste textNew

Paste or drop

Paste text below, or drop a file instead.

0 chars · 0 lines
…or drop a file
Drag and drop, or choose files

Choose an output

Encode text or any file to RFC 4648 Base32 (used by TOTP secrets and many APIs).

Fine-tune

Optional — sensible defaults are already set.

About Base32 Encoder

This tool encodes text or any file into RFC 4648 Base32, using the alphabet A to Z and 2 to 7. Base32 is case-insensitive and avoids easily confused symbols, which is why it is used for TOTP secrets in authenticator apps and in identifiers people may type by hand.

When it helps

  • Encoding a random secret key for a TOTP or HOTP two-factor setup.
  • Producing identifiers that survive case-insensitive file systems or DNS labels.
  • Testing an application's Base32 decoder with known input.

Tips

  • Padding with = fills the output to a multiple of 8 characters. Many TOTP implementations and otpauth:// URIs expect the secret without padding, so turn off "Add = padding" for those.
  • Base32 output is about 60 percent larger than the input, more than Base64's one third, in exchange for being case-insensitive.
  • This uses the standard RFC 4648 alphabet, not Crockford's Base32 or the base32hex variant.

Good to know

Quick answers about base32 encoder in your browser.

Base32 has no lowercase letters, no + or / and no 0, 1 or 8, so a secret shown on screen can be typed by hand without confusing similar-looking characters.

No. Like Base64, it is a reversible encoding with no key. Its job is to represent bytes as text, not to protect them.

Yes. There is no sign-up, no watermark and no limit on how many files you process.

No. Files are read and processed locally in your browser, so they never leave your device.

Related tools