Text to Base32

Encode your text into Base32 format using standard RFC 4648 alphabet

Input Text

Base32 Output

0 Input Bytes

0 Output Characters

+0% Size Increase

Encoding text as Base32

Base32 rewrites data using 32 characters, the letters A to Z and the digits 2 to 7. The result is case-insensitive and avoids symbols that are troublesome in URLs and filenames, and it skips look-alikes such as 0, 1, 8 and 9. It is used in one-time-password secrets, some identifiers and protocols that must survive being read aloud or typed by hand. This tool converts any text you enter into a standards-compliant Base32 string.

Using the encoder

Type or paste text into the Input Text box. The Paste button reads the clipboard and Clear empties the box.
Click Encode to Base32.
The Base32 Output card shows the encoded string.
Use Copy Result or Download .txt (saved as base32_output.txt). Three stats sit below: Input Bytes, Output Characters and Size Increase.

What happens under the hood

Your text is converted to UTF-8 bytes first, so accents, non-Latin scripts and emoji are handled correctly and count as multiple bytes.
The bytes are split into five-bit groups, and each group is mapped to a character from the RFC 4648 alphabet.
Equals signs are appended so the output length is a multiple of eight characters.

Sample scenarios

Generating a test secret for an authenticator app integration during development.
Producing case-insensitive tokens for use in filenames or DNS labels during a proof of concept.
Comparing your own encoder implementation against a known-good result.
Demonstrating to students how different encodings expand data.

Things to keep in mind

Base32 makes data bigger: roughly eight characters for every five bytes, which is an increase of about sixty percent before padding, as the Size Increase figure will show. It is an encoding, not encryption, so it hides nothing from anyone who knows to decode it. The output always includes the equals signs, and some systems, such as many authenticator apps, expect them omitted, so trim them if needed. Only the standard alphabet is produced, not the extended-hex or Crockford versions. To reverse the process, use the Base32 to Text decoder. Encoding runs as JavaScript in the page when you click the button, and the stats update with each new encode so you can compare different inputs.

Related Tools

Related Tools

Frequently Asked Questions

Which Base32 alphabet does this tool use?

The standard RFC 4648 alphabet: uppercase letters A to Z followed by the digits 2 to 7. It does not produce the Base32hex or Crockford variants, which use different character sets.

Why does the output end with equals signs?

The tool adds padding so the output length is a multiple of eight characters, as the standard requires. Some applications accept unpadded Base32, in which case you can delete the trailing equals signs after copying.

Does it handle non-English text and emoji?

Yes. Text is first converted to UTF-8 bytes, so accented letters, other scripts and emoji encode correctly. They use more than one byte each, which is why Input Bytes can exceed the number of characters you typed.

What does the Size Increase figure mean?

It compares the encoded length, including padding, with the number of input bytes, shown as a percentage. Base32 always expands data, typically by about 60 percent or more for short inputs because of the padding.

Is Base32 a secure way to hide data?

No. It is only an encoding and can be reversed by anyone who knows to decode it. Use real encryption for secrets. Base32 is chosen for readability and compatibility with case-insensitive systems, not for confidentiality.