About the Base32 and Base58 Encoder
Base32 and Base58 Encoder converts text or raw bytes into Base32 or Base58, and back. Base32 follows RFC 4648: it uses the letters A to Z and the digits 2 to 7, is safe for case-insensitive systems, and is the format behind authenticator app secrets. You can choose whether to add = padding and whether to use the extended hex alphabet of 0 to 9 and A to V. Base58 uses the alphabet made famous by Bitcoin, which leaves out the confusing characters 0, O, I and l, and is used in cryptocurrency addresses, IPFS identifiers and short IDs. Enter text (converted as UTF-8) or a string of hex bytes, and pick Encode or Decode. If decoded bytes are not readable text, they are shown as hex. All of it runs in your browser, so your data is never sent anywhere.
Updated September 2026
How to use the Base32 and Base58 Encoder
- 1Choose Base32 or Base58, and Encode or Decode.
- 2Type or paste your text. For raw bytes, tick the hex option and enter bytes such as 48 65 6c 6c 6f.
- 3For Base32, choose padding and the alphabet if you need to match another system.
- 4Read the result, which updates as you type.
- 5Copy the result with the Copy button.
Where these encodings are used
- Base32: two-factor authentication secrets, some file and onion address formats, and case-insensitive identifiers.
- Base32 extended hex: DNS and sorting-friendly identifiers, where the order of the encoded text matches the order of the data.
- Base58: Bitcoin and other cryptocurrency addresses, IPFS content identifiers and short IDs.
- Both: compact ways to write bytes as text in configuration files, logs and URLs.
Text, bytes and hex
Encoders work on bytes, not on characters. When you type text, the tool first converts it to bytes in UTF-8, the common standard, so accented letters and emoji use two to four bytes each. To encode raw bytes, for example a key you have as hex, tick the hex option and enter the bytes, with or without spaces.
Decoding goes the other way: the text is turned into bytes, and if these bytes form valid UTF-8 text, you see the text. Otherwise you see the bytes as hex digits.
Common problems
If decoding fails, check for characters outside the alphabet. Base32 accepts A to Z and 2 to 7, and Base58 rejects 0, O, I and l, which is often a sign of a typing or copying mistake. A Base32 text whose length does not fit a whole number of bytes is also reported. Spaces and new lines are ignored.
Base58 has no padding and no checksum in this tool. Bitcoin addresses add a Base58Check checksum on top, which is not verified here. Leading zero bytes are kept as leading 1 characters, as in the standard.
Related tools
Base64 Encoder Decoder handles Base64, and Number Base Converter switches numbers between binary, octal, decimal and hex. Hash Generator creates digests that are often written in hex or Base64, and UUID Generator makes identifiers. Binary Translator and ROT13 and Caesar Cipher show other ways of writing text.
Remember that encoding is not encryption. For passwords and secrets, use Password Generator and keep them safe.
Features
- Base32 (RFC 4648) with or without padding
- Extended hex alphabet for Base32
- Base58 with the Bitcoin alphabet
- Encode and decode text as UTF-8
- Hex bytes as input or output
- Clear error messages for invalid characters
- Runs in your browser
Frequently asked questions
What is Base32?
Base32 turns binary data into text using 32 characters: the letters A to Z and the digits 2 to 7. Each character carries 5 bits, so the output is about 60 percent bigger than the input. It is case-insensitive and avoids look-alike characters such as 0 and 1, which makes it good for things typed by hand, such as one-time password secrets in authenticator apps.
What is Base58?
Base58 is a way of writing numbers and bytes with 58 characters: the digits and letters without 0, O, I and l, and no symbols. It makes short, easy-to-copy strings that do not break at word boundaries. It was created for Bitcoin addresses and is also used by IPFS and other systems.
What does the = at the end of Base32 mean?
Padding. Base32 works in blocks of 8 characters, and if the data does not fill a block, the end is padded with equal signs. Many systems accept the text without padding, and some need it, so the tool lets you choose.
What is the difference between Base32 and Base64?
Base64 is more compact because each character holds 6 bits, but it is case-sensitive and uses symbols such as + and /. Base32 is longer but uses only letters and digits of one case, so it survives places where case is lost or symbols are troublesome, such as file names and voice reading.
Why do I see hex when I decode?
Decoded data does not have to be text. If the bytes are not valid UTF-8, for example a key or a hash, the tool shows them as hex so that you can see them exactly. Tick the option to always show hex if you want to check the bytes of readable text.
Is Base32 or Base58 a kind of encryption?
No. They are ways of writing data as text, and anyone can decode them. Do not use them to hide secrets. Use them to make data easier to store, type or transmit.