Loona Automation logoLoona Developer Tools
Home › Encoders & Decoders

Text to Base32 Encoder

In short: encode text with the RFC 4648 Base32 alphabet (A–Z and 2–7) — the encoding behind authenticator-app secrets, designed to be case-insensitive and free of easily-confused characters.
🔒 Private by design: everything runs in your browser on this device. Your input is never uploaded to a server.

Example

Input:

foobar

Output:

MZXW6YTBOI======

About this converter

Base32 encodes 5 bytes as 8 characters from a 32-symbol alphabet of uppercase letters and the digits 2–7, deliberately excluding 0, 1 and 8 (too easily confused with O, I and B when read aloud or typed). That human-friendliness is exactly why it shows up in TOTP shared secrets (the strings behind authenticator apps and those "manual setup keys"), in some license keys and in DNS-based systems where case-insensitivity matters. The cost is size: output is 60% larger than the input, worse than Base64 — Base32 is chosen for safety in transcription, never for compactness. Padding with = to a multiple of 8 characters is part of the standard.

Frequently Asked Questions

Where do I meet Base32 in real life?

In the manual setup key of any authenticator app (TOTP), some VPN and backup codes, and encoded identifiers designed to be typed by humans.

Why does the alphabet skip 0 and 1?

To avoid confusion with the letters O and I when people read and type codes.

Base32 vs Base64 — which should I choose?

Base64 for machine-to-machine transport (smaller); Base32 when a human might read, type or hear the string.

Related Developer Tools

Embed this tool on your website — free

Add this tool to your own website or blog — it is completely free, needs no sign-up, and always shows the latest version. Copy the code below and paste it into your page where you want the tool to appear. Keeping the small “Powered by Loona Automation” credit line under the embed helps keep this tool free — but you are free to style or remove it; the tool works either way.