Does Base32 Encode upload my file or text to Tool-You servers?

No. Base32 Encode runs in this browser tab. Files stay on the device. Limit note: UTF-8 to RFC 4648 Base32. Empty text fails.

Should I use Hex Encode instead of Base32 Encode?

Use Base32 Encode when you need RFC 4648 Base32; optional padding and lowercase. Use Hex Encode when you need Hex encode/decode with bytes. They share a category (Crypto) but not the same job.

Base32 Encode

RFC 4648 Base32; optional padding and lowercase.

Encodes UTF-8 to A–Z and 2–7. Padding with = is on by default. Optional lowercase. Unlike Hex Encode this is Base32, not hex. Unlike TOTP this does not read a secret or emit digits. Empty text fails.

What Base32 Encode does

The interactive controls for Base32 Encode load after this article so crawlers still read the instructions. Path /crypto/base32-encode is the canonical address. Work happens on this device; Tool-You does not take a copy of the file or pasted text for Base32 Encode.

How to use Base32 Encode

Keep this tab on Base32 Encode (/crypto/base32-encode). Pasting into the wrong Crypto tool (for example Hex Encode) changes the job.
Paste or type the input Base32 Encode expects. Path hint: crypto · base32 encode. RFC 4648 Base32; optional padding and lowercase.
Apply the Base32 Encode action only. Base64 Encode / Decode is a different transform (Encode or decode UTF-8 text as Base64 or Base64URL.). Encodes UTF-8 to A–Z and 2–7. Padding with = is on by default. Optional lowercase. Unlike Hex Encode this is Base32, not hex. Unlike TOTP this does not read a secret or emit digits. Empty text fails.
Copy the output of Base32 Encode if you need it elsewhere. Size/complexity still follows: UTF-8 to RFC 4648 Base32. Empty text fails.
If the text job is actually Hex encode/decode with bytes., leave Base32 Encode and open Hex Encode.

When not to use Base32 Encode

Skip Base32 Encode when a neighbor tool matches better — start with Hex Encode or Base64 Encode / Decode — or when the description already warns the job will fail. In the tool’s own words: Encodes UTF-8 to A–Z and 2–7. Padding with = is on by default. Optional lowercase. Unlike Hex Encode this is Base32, not hex. Unlike TOTP this does not read a secret or emit digits. Empty text fails.

Questions about Base32 Encode

What does Base32 Encode do that other Crypto pages on this site do not?: Encodes UTF-8 to A–Z and 2–7. Padding with = is on by default. Optional lowercase. Unlike Hex Encode this is Base32, not hex. Unlike TOTP this does not read a secret or emit digits. Empty text fails. Short version: RFC 4648 Base32; optional padding and lowercase.
Does Base32 Encode upload my file or text to Tool-You servers?: No. Base32 Encode runs in this browser tab. Files stay on the device. Limit note: UTF-8 to RFC 4648 Base32. Empty text fails.
Should I use Hex Encode instead of Base32 Encode?: Use Base32 Encode when you need RFC 4648 Base32; optional padding and lowercase. Use Hex Encode when you need Hex encode/decode with bytes. They share a category (Crypto) but not the same job.
What are the limits of Base32 Encode?: UTF-8 to RFC 4648 Base32. Empty text fails. Also: Encodes UTF-8 to A–Z and 2–7. Padding with = is on by default. Optional lowercase. Unlike Hex Encode this is Base32, not hex. Unlike TOTP this does not read a secret or emit digits. Empty text fails.