Base64 is not the only way to turn bytes into text. Two others trade compactness for readability.
Base32
Base32 uses 32 characters: the capital letters A to Z and the digits 2 to 7, with equals signs as padding. It is case-insensitive and avoids confusable characters, so people can type it back correctly. In the Base32 and Base58 tool, “Hello” becomes JBSWY3DP. It is longer than Base64, since each character carries 5 bits instead of 6, but it is safe on case-insensitive systems and easy to read aloud. Authenticator app secrets are commonly written this way.
Base58
Base58 uses letters and digits but leaves out the characters that look alike (0, O, I and l) and skips the plus and slash used by Base64. “Hello” becomes 9Ajdvzr. It is best known from Bitcoin addresses, where a typo would be costly, and from short identifiers.
Using the tool
- Choose Base32 or Base58, then encode or decode.
- Paste your text.
- Copy or download the result.
When decoding, the input must be valid in the chosen alphabet and decode to valid UTF-8 text. Otherwise the tool tells you.
Which one to pick
- Base64 when size matters and case is preserved.
- Base32 when the text is typed or read aloud, or the system ignores case.
- Base58 when people copy identifiers by hand and look-alike characters cause errors.
Not encryption
All three are reversible by anyone without a key, so they offer no protection. Treat anything “hidden” in them as visible.
See also how to encode and decode Base64.
Frequently asked questions
Is the tool compatible with Bitcoin addresses?
It converts text to and from Base58. Real Bitcoin addresses also include a checksum and a version byte, which this tool does not add, so use it for learning, not for handling funds.