Use a browser-based Base32 tool to encode text into Base32 or decode a Base32 string back to text, entirely on your device. Base32 uses a 32-character alphabet that avoids ambiguous characters, which is why it shows up in TOTP secrets and other places where a string has to be typed or read aloud.
Both encode binary data as printable text, but Base32 uses only uppercase letters and the digits 2 through 7, deliberately leaving out characters that are easy to confuse like 0, 1, 8 and 9. That makes Base32 longer than Base64 for the same data but far more robust when a human has to type it, read it over the phone, or scan it, at the cost of some size.
The most common encounter is two-factor authentication: the secret behind an authenticator app is usually shared as a Base32 string. It also appears in some file and hashing systems. Being able to decode a Base32 value locally lets you inspect it while debugging a TOTP setup, and because the tool runs client-side, a secret you decode is never transmitted.
Base32 uses a smaller, less ambiguous alphabet (A to Z and 2 to 7), which makes it easier to type and read but longer than Base64.
Because Base32 avoids confusing characters, making the secret safe to type by hand or read aloud when setting up an authenticator.
No. Encoding and decoding run entirely in your browser.