Base32 Encoder

How Base32 Encoder works

Encode text to Base32 or decode Base32 back to text using the standard alphabet. Everything happens inside this page: the tool reads your input, runs the calculation or conversion locally, and hands the result back to you. Nothing is transmitted, because there is no backend to transmit it to.

That design choice is deliberate. Most free tool sites upload your files to a server, process them there, and quietly keep a copy. Toolcin cannot do that — the site is a set of static files. If your connection dropped the moment the page finished loading, every tool would still work.

Why not just use Base64

Base32 uses only A–Z and 2–7, so the output survives systems that uppercase everything, cannot carry punctuation, or treat 0 and O as the same character. That is why TOTP secrets and some licence keys are Base32 rather than Base64.

The cost is size: five characters carry 25 bits instead of Base64's 30, so a Base32 string is about 20% longer for the same data.

Padding and case

Base32 pads with = to a multiple of eight characters, and RFC 4648 defines an extended hex alphabet that differs in the last six symbols. Decoding usually ignores case and padding, which is what makes it forgiving to type by hand.

What it is not

Like Base64, it is encoding, not encryption. A Base32 string is trivially reversible, so it protects nothing — it only makes data safe to transmit through a restricted channel.

Good to know

• Works offline once loaded, including on flights and in locked-down networks.
• No file size limit beyond your device's own memory.
• Free to use, with no account and no usage counter.
• Results are produced locally, so they are not logged or shared with anyone.

Questions